skill-store
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SKILLS_NAMESPACE | No | Gateway namespace for skill resources and actions. Set to an empty string for direct stdio clients. | skills |
| SKILLS_STATE_DIR | Yes | Persistent state directory for the skill store. Must exist and be writable. Only one process should run per state directory. | |
| SKILLS_PROMPT_SEPARATOR | No | Separator used in prompt names. Set to '__' if a client rejects slash-separated names. | / |
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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_storeC | Register a directory, Git, or S3 store without a restart. |
| update_storeC | Update specified fields. Omitted fields retain their existing values. |
| remove_storeB | Remove a registration without deleting backend data. |
| set_writableB | Select one writable-capable store. Git stores are read-only. |
| refresh_storeA | Refresh a store and atomically publish the rebuilt catalog. |
| migrate_skillA | Copy and verify a skill before removing a writable source. |
| migrate_storeB | Migrate each skill, stopping at the first error with progress counts. |
| list_storesA | List store configuration with credentials masked. |
| use_skillB | Load a skill and its supporting resources. Use a matching skill before starting a task. Load it with use_skill and its qualified name. No skills are available. |
| list_skillsB | List qualified names and descriptions with pagination. |
| write_skillC | Write a complete skill into the writable store; binary files use base64. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| instructions |
TDQS
Scored across 11 tools
Most tools target a distinct resource and action: store lifecycle verbs are clearly separated from skill operations. The main risk is migrate_skill vs migrate_store, but their descriptions clarify single-skill vs batch migration.
The dominant pattern is verb_noun (add_store, list_skills, write_skill) and is easy to predict. set_writable breaks the pattern by omitting the store object, and migrate_skill/migrate_store are easy to typo but still follow the convention.
Eleven tools is within the well-scoped range and each tool covers a distinct management action for stores or skills. The count feels appropriate for a skill-store management server without bloat.
Store lifecycle is well covered with add/update/remove/refresh/list and writable selection, and skills support use/write/list/migrate. The obvious gap is no generic delete/remove skill operation, so a stale skill in a writable store cannot be directly removed.