skill-maintenance-mcp
Related Servers
Alternatives to skill-maintenance-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to search, retrieve, and validate portable SKILL.md files through skill resources and read-only tools.26 PyPI1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to discover, search, retrieve, and read supporting files from a centrally published, versioned skill registry through four read-only MCP tools.1,505 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables users to validate MCP servers, skills, extensions, and packages for schema, security, functional, and semantic quality directly from their MCP client.MIT
- AlicenseNot gradedqualityBmaintenanceEnables managing a canonical library of agent skills and MCP servers, syncing them across multiple development harnesses, and adding, importing, or configuring them through MCP tools.7 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides read-only repository health scanning tools for drift detection, module reachability, prompt bloat, evidence calibration, and registration completeness, enabling agents to diagnose repositories via MCP.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to browse a local skill library, retrieve individual skill instructions and files, route task queries via Jev, and report completion activity.28 npmMIT
TDQS
Scored across 5 tools
Each tool targets a distinct maintenance action: backup, corruption scan, decision logging, decision reading, and aggregate validation. However, skill_validate explicitly includes corruption scanning and a decision-log summary, so an agent may wonder when to call it versus skill_scan_corruption or skill_read_decisions.
All names use a consistent skill_ prefix and snake_case, which is predictable. Minor deviations exist: skill_backup and skill_validate are verb-only, while others use verb_noun, and log_decision/read_decisions differ in number.
Five tools is well-scoped for skill maintenance. Each tool covers a specific, non-redundant part of the backup-scan-validate-log workflow.
The core maintenance loop is present, but backup lacks a corresponding restore or list-backups operation, and decision-log reading only returns a summary. These are notable gaps for a server explicitly concerned with safe skill revision.