Knowledge

@knowledge files are static reference material that provide context to your MCP-compatible tools. They are the raw data and documents you want to keep up-to-date in one central place. @knowledge files are the “nouns” of your AI workflows.

Common types of @knowledge files include:

API documentation

• API schemas, endpoint references, error codes

Architecture and design

• System architecture diagrams, database schemas, component relationships

Development standards

• Coding standards, style guides, code review checklists

Domain and business logic

• Business rules, validation logic, user permissions

Workflows and procedures

• Deployment workflows, onboarding processes, step-by-step procedures

How @knowledge helps in context engineering

@knowledge files centralise reference material that would otherwise be scattered across files, wikis, and conversations. When /instructions reference @knowledge, your team’s tools always use the latest version.

• One place for everything - Update schemas, guides, or specs once, changes propagate everywhere
• Consistency - All /instructions reference the same up-to-date material
• Maintainability - Update reference material without rewriting prompts

How to build @knowledge

@knowledge files are simple. They only contain content and have no dynamic properties.

1. From a library, add + Knowledge
2. Give it a file name (e.g., my-schema.md)
3. In the editor, paste or write your content
4. Fill out the Properties panel: Description is required
5. Select Publish to make it available in connected tools. Published @knowledge files are sent to the MCP endpoint and visible in connected tools. Drafts are visible only in the Sokket web app.

Understanding the properties panel (MCP standards)

As you type in the editor, this panel updates automatically. Published @knowledge files are sent to the MCP endpoint and visible in connected tools. Drafts are visible only in the Sokket web app.

Details

• Name: The @knowledge file name
• Description: (MCP Requirement) Required. The human-readable description your team will see. The @knowledge file cannot be published without it.

Using @knowledge in /instructions

@knowledge files can be referenced in /instructions using the @knowledgeFile syntax. Type @knowledgeFile in your /instruction content to reference @knowledge files.

e.g.

• Refactor this code using @frontend-style-guide
• Generate a new API route based on @api-schema
• Draft an error message for $errorCode using @standard-api-error-codes

When you type @knowledgeFile in a /instruction editor, it automatically creates a reference link that pulls that @knowledge file into the /instruction when it runs. Reference names must match the @knowledge file name exactly, including spelling and casing.

Troubleshooting

The Publish button is disabled when mandatory fields are missing. All @knowledge files must have a Description. Check the Properties panel and fill in the missing Description field.

A new @knowledge file is not appearing in a connected tool. The @knowledge file is likely still a Draft. Only Published items are sent to the MCP Endpoint. Drafts are visible only in the Sokket web app.

A /instruction reference to @knowledge fails. The referenced @knowledge file is not published, or the reference name doesn’t match the filename exactly (check spelling and casing). Publish the @knowledge file or fix the reference name in the /instruction.

Next Steps

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