agentskills-mcp
Related Servers
Alternatives to agentskills-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables 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 gradedqualityCmaintenanceEnables any agent to search skill packs with bounded results, fetch one full validated skill on demand, and act without copying directories into prompts.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search and retrieve over 89K skills on-demand at runtime, eliminating the need to manually install skills upfront.136MIT
- FlicenseNot gradedqualityCmaintenanceEnables searching and browsing a library of Agent Skills and prompts, then loading full SKILL.md instructions and supporting files for a chosen skill.-
- AlicenseNot gradedqualityCmaintenanceEnables MCP-capable LLMs to browse, search, load, and receive recommendations from the pstack Agent Skills collection, including engineering principles and task playbooks, on demand.MIT
- AlicenseAqualityBmaintenanceEnables agents to discover, read, and use reusable skills stored in public GitHub repositories.417 npmMIT
TDQS
Scored across 10 tools
Most tools are clearly separated by resource (skill body, references, scripts, assets) and by action (list vs get vs search). The only soft overlap is between list_skills, search_skills, and get_skill_metadata, which all return catalog-level metadata, but the descriptions give explicit guidance on when to use each.
Every tool follows a strict verb_noun snake_case pattern (list_/get_/search_ + resource). The per-directory resource names (skill_references, skill_scripts, skill_assets) are parallel and predictable, so an agent can infer unlisted tools.
Ten tools is well within the ideal range and each earns its place: three discovery tools, one body reader, and a symmetric list/get pair for each of the three sub-directories. No redundant or filler tools.
The read/lifecycle surface for consuming a skill is fully covered: discover, inspect metadata, read body, and traverse references, scripts, and assets. Gaps are minor and likely intentional — there is no way to create, update, or delete skills, and no tool to execute a script rather than just read it.