skill-store
Related Servers
Alternatives to skill-store
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables 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.2,056 npm6MIT
- AlicenseAqualityCmaintenanceConverts AI Skills (following Claude Skills format) into MCP server resources, enabling LLM applications to discover, access, and utilize self-contained skill directories through the Model Context Protocol. Provides tools to list available skills, retrieve skill details and content, and read supporting files with security protections.328Apache 2.0
- AlicenseAqualityDmaintenanceIntegrates with the skills.sh ecosystem to allow AI coding agents to discover, install, and manage reusable instruction sets. It enables autonomous agents to extend their capabilities with structured skill discovery and full lifecycle management through the Model Context Protocol.619 npm1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables agents to install compatible SKILL.md skills from Git repositories or local directories into a persistent registry, then discover them through search, progressive loading, and asset reads. It exposes only user-selected hot skills as individual activation tools, keeping execution and trust decisions under explicit operator control.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to discover, install, and manage SKILL.md skills from a Git-backed registry via MCP tools for search, install, and list operations.4 npm1MIT
- AlicenseAqualityBmaintenanceEnables MCP hosts to discover, browse, and load Agent Skills from one or many SKILL.md libraries over the Model Context Protocol, with namespaced libraries, search/list/get tools, progressive disclosure, and a digest-verified pull client for syncing skills to disk.71MIT
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.