MCP-skill-library-dynamic
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SKILLS_DIR | Yes | Path to the skills directory. In the local stdio configuration, this is set to `<ROOT_DIR>/.agents/skills`. | |
| SKILL_LIBRARY_DATA_DIR | Yes | Path to the data directory. In the local stdio configuration, this is set to `<ROOT_DIR>/.data`. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_skillsA | List all available skills/rules in the knowledge base. Supports optional search query for token efficiency. |
| fetch_skill_ruleA | Fetch the full markdown content and nested rule guidelines of a specific skill. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one lists available skills, the other fetches a specific skill's content. There is no overlap or ambiguity between them.
Both tools follow the same verb_noun pattern (list_skills, fetch_skill_rule), making the naming predictable and consistent.
With only 2 tools, the set is on the thin side, but it fits the narrow scope of a read-only skill library. It feels borderline rather than clearly inadequate.
For a read-only knowledge base, list and fetch cover the essential operations. The search option on list_skills adds flexibility. Minor gaps like versioning or metadata retrieval are not critical.