Knowledge

Knowledge

@knowledge files are reusable reference documents stored in Sokket. They give your AI-assistant the background material it needs, such as schemas, standards, workflows, and architectural notes. /instructions load these files using @fileName, allowing you to keep reference content centralised and up-to-date.

This page explains what @knowledge is, how to create it, how references work, and how your AI-assistant uses the content when running an /instruction.

Example

A simple @knowledge file used to support test generation workflows:

Title:testing-guidelines.md
Description:** Shared rules for writing consistent unit tests.

Write tests that:
- cover typical behaviour
- check boundary conditions
- verify error handling
- document assumptions in the code

This demonstrates:

• A clear name and description
• Reusable testing rules
• Content that can be referenced from /instructions using @testing-guidelines

What @knowledge is used for

Common types of @knowledge include: API documentation (schemas, endpoints, response formats, error codes), architecture and design (system diagrams, database schemas, component relationships), development standards (style guides, coding standards, review checklists), domain and business logic (business rules, validation logic, permissions), and workflows and procedures (deployment workflows, onboarding guides, operational steps).

Using @knowledge keeps reference material in one place, so /instructions always rely on the latest version.

How to create @knowledge

@knowledge files contain only content. They do not use parameters or dynamic fields.

1. In a library, select + Knowledge
2. Enter a file name, for example testing-guidelines.md
3. Add your content in the editor
4. Open the Properties panel and add a Description (required)
5. Select Save
6. Select Publish to make the file available in connected tools

Referencing @knowledge in /instructions

Reference a file using its name:

@fileName

Examples:
• Follow the rules in @testing-guidelines
• Generate this route based on @api-schema
• Use @frontend-style-guide for naming

Reference names must match the @knowledge file name exactly, including casing. The referenced file must be published.

Technical details

In Sokket

• You create and publish @knowledge files
• Sokket exposes them with MCP resources/list and resources/read
• Descriptions and metadata are shown to tools and assistants
• Drafts remain in the Sokket web app until published

In the AI-assistant

When an /instruction runs:

1. The assistant fetches the instruction and metadata
2. It resolves all @fileName references
3. It loads each referenced file via resources/read
4. The knowledge content is injected into the resolved prompt
5. The final prompt is sent to the model

This approach reduces token waste and keeps reference material consistent.

Troubleshooting

Visit FAQs.

Related pages

Learn more about /instructions, context engineering, or connect tools.