skill-vault
Related Servers
Alternatives to skill-vault
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceA self-hosted registry and MCP server for reusable AI-agent skills that enables agents to discover, retrieve, and install skills with guardrails.58MIT
- AlicenseAqualityDmaintenanceA self-hostable, open-source, semantically-searchable Agent Skills registry delivered over MCP, with a three-tier progressive disclosure architecture.713 npm8Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables centralized, versioned management and distribution of AI agent skills through a horizontally scalable MCP server, allowing agents to dynamically discover, search, and retrieve skills over HTTP/SSE.MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that lets AI agents search, view, install, and validate skills from the skillhub registry through tool calls.MIT
- AlicenseNot gradedqualityDmaintenanceA local-first skill runtime for AI coding agents that defines skills as verifiable, composable units with sandboxed execution, and exposes them as MCP tools over HTTP.2 npm108Apache 2.0
- AlicenseNot gradedqualityBmaintenanceAn MCP server that lets AI agents browse and fetch skills from remote registries — GitHub repositories or direct HTTP URLs — without installing them locally first.MIT
TDQS
Scored across 7 tools
Each tool targets a distinct operation: search, fetch, publish, update, delete, and two separate list scopes. The only potential overlap is between search_skills and get_skill, but search returns relevant results while get returns full content by id. No tool ambiguously duplicates another.
All tools follow a consistent verb_noun pattern with snake_case: delete_skill, search_skills, get_skill, publish_skill, update_skill, list_my_skills, list_global_skills. The pluralization correctly reflects whether the tool returns multiple items or operates on one.
With exactly 7 tools, the set covers the core operations for a skill vault without being bloated or sparse. Each tool earns its place in the lifecycle (create, read, update, delete, search, list). This is a well-scoped collection for the server's purpose.
The toolset provides complete CRUD coverage: publish (create), get and list (read), update (update), and delete (delete). Additionally, search and the differentiation between personal and global lists round out the expected workflows for a vault. No missing operations that would force agents to work around gaps.