Skill Jack MCP
Related Servers
Alternatives to Skill Jack MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to dynamically discover and execute tools through a structured skills system. Serves as a documentation hub where skills are defined in directories, allowing progressive loading and interpretation of capabilities.MIT
- AlicenseNot gradedqualityFmaintenanceLoads Agent Skills from markdown files, exposing them as MCP tools or system prompts for AI agents.46 PyPI31MIT
- AlicenseNot gradedqualityAmaintenanceEnables coding agents to search a directory of Agent Skills and load a specific skill only when a request needs it, avoiding loading every skill description into every session.MIT
- AlicenseNot gradedqualityCmaintenanceTurns Claude-style skills (SKILL.md files with resources) into callable MCP tools for any agent. Discovers skills from a directory, exposes their instructions and resources, and can execute bundled helper scripts.224 PyPI407MIT
- AlicenseAqualityCmaintenanceEnables LLM agents to discover and search a catalog of skills, then fetch skill instructions and supporting references, scripts, and assets on demand.10MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to discover, search, and load agent skills from many sources, including other agents' skill directories, Claude Code plugin marketplaces, and remote git repositories, with no copying or syncing required.1,058 npm6MIT
TDQS
Scored across 13 tools
The core tools (load-skill, skill-resource) are clearly distinct, and the add/remove config pairs (directory, org, origin) target unambiguous resources. The only mild confusion is between the UI-opener tools (skill-config, skill-display) and the granular operations they overlap with, but descriptions help distinguish them.
Nearly all tools follow a predictable kebab-case skill-{subsystem}-{action}-{target} pattern (skill-config-add-directory, skill-display-reset-override). The outliers load-skill and skill-resource use a different verb/noun-only structure, but the set remains readable and mostly consistent.
13 tools sits comfortably in the well-scoped 3-15 range for a skill-management server. The surface leans heavily toward configuration (8 of 13), which is slightly unbalanced but each tool still earns its place.
Config resources (directories, orgs, origins, static mode) all have add/remove or set coverage, and display settings have update/reset. The main gap is the absence of a programmatic list-skills tool, since enumeration is only exposed through the skill-display UI, but core load/resource workflows are covered.