No user-submitted related servers found.
Scored across 12 tools
Most tools address distinct actions: binding, listing, suggesting, rescanning, archiving, reading, and estimating. A few diagnostic/inspection tools (doctor, list_skills, get_binding, why) have some overlapping concerns, but their descriptions make each purpose clear enough.
Most tools follow an imperative verb_noun pattern like bind_skills, list_skills, rescan_skills, and estimate_tokens. A few names deviate (doctor, why, native_skills_bypass), but the pattern is still predictable overall.
Twelve tools is a well-scoped set for a skill-management server. Each tool covers a distinct part of the workflow: cataloging, binding, suggesting, diagnosing, archiving, reading, and host integration, without obvious bloat.
The tool surface covers core lifecycle needs: listing, reading, binding, suggesting, rescanning, archiving, and host contract writing. Restoring archived skills or configuring skill roots is not directly exposed, but those feel like external/recoverable edge cases rather than critical gaps.
