Skill Jack MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SKILLS_DIR | No | Path to the directory containing Agent Skills |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| skillA | Load a skill's full instructions. Returns the complete SKILL.md content with step-by-step guidance, examples, and file references to follow. SkillsWhen a user's task matches a skill description below: 1) activate it, 2) follow its instructions completely. |
| skill-resourceA | Read files referenced by skill instructions (scripts, snippets, templates). Use when skill instructions mention specific files to read or copy. Pass a directory path (e.g., 'templates') to read all files in that directory at once. |
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 clearly distinct purposes: 'skill' loads the full instructions for a skill, while 'skill-resource' reads the files referenced by those instructions. There is no overlap in functionality, and an agent can easily tell them apart based on their descriptions.
The tool names follow a consistent pattern with a hyphen separating words (e.g., 'skill-resource'), and both start with 'skill' to indicate the domain. However, the first tool is simply 'skill' while the second is 'skill-resource', which is a minor deviation from a strict verb_noun pattern, but overall the naming is readable and predictable.
With only 2 tools, the server feels thin for a 'Skill Jack MCP' that implies managing or executing skills. This minimal set may not cover essential operations like listing available skills, creating new skills, or updating existing ones, which are likely needed for a complete skill management system.
Inferring the domain as skill management, there are significant gaps: no tools to list, create, update, delete, or search skills, and no way to execute or run skills directly. The provided tools only handle loading instructions and reading referenced files, leaving core lifecycle operations uncovered and likely causing agent failures in broader tasks.