From skill-master
This skill should be used when the user asks "which skill should I use", "skill recommendations", "onboard me", "what skills do I have", "improve skills", "skill analytics", "adaptive skills", or "skill ecosystem". Make sure to use this skill whenever the user needs to find the right skill for a task, wants onboarding into a new project, needs skill combination recommendations, wants to analyze skill usage patterns, evolve or improve existing skills based on usage data, or manage the skill ecosystem, even if they just ask what tools or capabilities are available.
How this skill is triggered — by the user, by Claude, or both
Slash command
/skill-master:skill-masterThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Intelligent orchestrator for the entire Claude Code skill ecosystem. Provides proactive onboarding, skill recommendation, usage analytics, and adaptive growth -- skills that learn and improve from how they are used.
Intelligent orchestrator for the entire Claude Code skill ecosystem. Provides proactive onboarding, skill recommendation, usage analytics, and adaptive growth -- skills that learn and improve from how they are used.
Three integrated layers work together:
SessionStart Hook (proactive) -- Fires on every conversation. Scans the project for signals (go.mod, Dockerfile, .claude-plugin, etc.) and injects recommended skills into context.
This Skill (knowledge) -- The meta-knowledge base. Contains information about what every skill does, when to combine them, and how to evolve them.
MCP Server (tools) -- Persistent tools for searching, recommending, installing, and evolving skills programmatically.
The onboarding process follows this sequence:
The hook detects these project signals:
| Signal | Detection | Recommended Skills |
|---|---|---|
| Go project | go.mod, go.sum | go-development, framegotui-sdk |
| framegotui | pkg/core/app.go, import | framegotui-sdk (critical) |
| Node.js | package.json | frontend-design |
| Docker | Dockerfile, compose | docker-deployment |
| Claude plugin | .claude-plugin/ | marketplace-creator, plugin-dev:* |
| Tailscale | tailscale.json, /var/lib/tailscale | tailscale-expert |
| Xen Orchestra | xo-cli.conf | xen-orchestra-expert |
| gRPC | proto/, buf.yaml | grpc-patterns |
| MCP | .mcp.json, pkg/mcp | plugin-dev:mcp-integration |
| Web UI | pkg/web, web/ | frontend-design |
| CLAUDE.md | CLAUDE.md exists | claude-md-management |
To add a new signal detection pattern:
hooks/session-start.sh (or the equivalent hook configuration)Example signal entry structure:
Signal name: "terraform"
Detection: main.tf, *.tf, .terraform/
Skills: infrastructure-as-code (critical)
Compound: terraform + tailscale -> network-infra-combo
Some tasks need multiple skills working together:
New biodoia project (Go + framegotui):
framegotui-sdk -- architecture patternssuperpowers:test-driven-development -- TDD disciplinesuperpowers:brainstorming -- design firstmarketplace-creator -- if building a pluginInfrastructure task (Tailscale + XO):
tailscale-expert -- VPN meshxen-orchestra-expert -- VM managementsuperpowers:writing-plans -- plan before executingSkill development (meta):
skill-creator:skill-creator -- create and test skillsplugin-dev:skill-development -- plugin skill patternssuperpowers:writing-skills -- TDD for skillsmarketplace-creator -- register in marketplaceSkills evolve based on usage data. The system tracks patterns and proposes improvements automatically.
~/.claude/skill-master-usage.jsonlThe adaptive growth workflow operates as a continuous loop:
Description tuning -- If a skill should trigger but does not, widen the description triggers. If it triggers when it should not, narrow them.
Signal mapping -- If users in Go projects consistently invoke tailscale-expert, add go+tailscale as a compound signal in the hook configuration.
Skill gaps -- If users repeatedly ask about a topic with no matching skill, flag it as a candidate for a new skill. Log the topic and frequency in the usage JSONL file.
Content evolution -- If a skill's references are outdated (API changes, new features), flag for refresh. Compare reference file timestamps against upstream release dates when possible.
Combination discovery -- If skills A and B are always used together in the same session, suggest creating a combined workflow or meta-skill that bundles both.
Use the /skill-evolve command or the MCP tool analyze_usage:
# Via command
/skill-evolve
# Via MCP tool (if MCP server running)
# Tool: skill_master.analyze_usage
# Via the analysis script directly
python3 scripts/analyze-usage.py
The MCP server exposes these tools when running. Configuration is defined in .mcp.json at the plugin root:
{
"mcpServers": {
"skill-master": {
"command": "python3",
"args": ["${CLAUDE_PLUGIN_ROOT}/mcp-server/server.py"]
}
}
}
| Tool | Description | Example Use |
|---|---|---|
search_skills | Search all available skills by keyword or domain | Find skills related to "infrastructure" or "testing" |
recommend_stack | Given a project path, recommend a skill stack | Analyze /mnt/godata/projects/myapp and suggest relevant skills |
analyze_usage | Analyze usage.jsonl and propose improvements | Review last 30 days of skill invocations for optimization |
skill_health | Check skill quality scores across the marketplace | Audit all skills for description quality, reference freshness |
propose_evolution | Generate a specific improvement proposal for a skill | Suggest description changes for a skill with low trigger accuracy |
Start the server by ensuring the .mcp.json file is present in the plugin root. Claude Code automatically discovers and starts MCP servers defined in plugin .mcp.json files. The server implementation is at mcp-server/server.py.
Skill Master serves as the coordination layer across the entire skill ecosystem:
references/skill-catalog.mdreferences/adaptive-growth.mdscripts/analyze-usage.pyreferences/skill-catalog.mdreferences/adaptive-growth.mdmcp-server/server.pyscripts/analyze-usage.pyhooks/ directory at the plugin rootnpx claudepluginhub biodoia/biodoia-skills-marketplace --plugin skill-masterEnforces skill invocation before any response: checks for relevant skills even with 1% applicability, used at conversation start.
Create, update, and manage Claude Code skills including SKILL.md files, slash commands, directory structures, frontmatter, substitutions, and invocation controls.
Loads skills efficiently using a 3-layer progressive disclosure system: lightweight index always loaded, summaries on demand, full skills only during execution to minimize token usage.