Skill Master

Identify from the user's request:

• Core task: What needs to be accomplished?
• Domain: What area/field does this belong to?
• Keywords: Key terms for searching

Step 1.2: Search for Skills

MUST follow the complete search workflow in references/skill-search.md.

Copy and track overall search progress:

Search Phase Progress:
- [ ] Step 1: Internal skills searched
- [ ] Step 2.1: ALL known GitHub repos searched (anthropics, K-Dense-AI, ComposioHQ)
- [ ] Step 2.2: Known repos enumerated (if 2.1 had no matches)
- [ ] Step 2.3: Broader GitHub search (only after 2.1+2.2 exhausted)
- [ ] Step 3: Web search (only after GitHub exhausted)

CRITICAL: MUST complete ALL searches in each step before proceeding to next step.

Search order - execute in sequence:

1. Internal skills: MUST check both ~/.claude/skills/ and .claude/skills/
2. GitHub known repos: MUST search ALL three repos before broader search:
   • site:github.com/anthropics/skills SKILL.md <keywords>
   • site:github.com/K-Dense-AI/claude-scientific-skills SKILL.md <keywords>
   • site:github.com/ComposioHQ/awesome-claude-skills SKILL.md <keywords>
3. GitHub enumeration: MUST enumerate repo contents if searches return no match
4. GitHub broader: Only after known repos exhausted
5. Web: Only after GitHub exhausted

See references/known-skill-repos.md for curated skill sources.

Step 1.3: Evaluate Results

Validation gate before concluding search:

• All internal locations checked
• All known GitHub repos searched
• All known repos enumerated (if no WebSearch matches)
• Results documented for each source

If skill found:

• Present the skill to user with description
• Proceed to Phase 2 (Storage Confirmation)

If NO skill found (only after ALL searches complete):

• Inform user: "No existing skill found. I'll research and create one."
• Proceed to Phase 3 (Skill Creation)

Phase 2: Storage Confirmation

Goal: Determine where to store the skill.

Ask user using AskUserQuestion:

Where should this skill be stored?

1. LOCAL (.claude/skills/)
   - Project-specific
   - Shared with team via git

2. GLOBAL (~/.claude/skills/)
   - Personal
   - Available across all projects

Remember the choice for later use.

Step 2.1: Source Tracking (External Skills Only)

CRITICAL: When storing a skill found from an external source (GitHub, web), you MUST create a source.md file alongside the SKILL.md to track provenance.

Create source.md in the skill directory with:

# Source

- **Origin**: <GitHub | Web | MCP Marketplace>
- **URL**: <original URL where skill was found>
- **Repository**: <owner/repo if GitHub>
- **Author**: <original author if known>
- **Retrieved**: <date skill was fetched>
- **License**: <license if specified>

## Notes

<Any relevant notes about the source, modifications made, etc.>

Do NOT create source.md for:

• Skills created from scratch (Phase 3)
• Skills already present locally

Phase 3: Skill Creation (if not found)

Goal: Create a new skill through deep research.

Follow the creation workflow in references/skill-create.md.

Steps:

1. Research the domain thoroughly using WebSearch
2. Identify best practices and common patterns
3. Design the skill structure
4. Generate SKILL.md following official format
5. Save to the location user chose in Phase 2
6. Auto-Register: Automatically run the registry update script to add the new skill to AGENTS.md.

   python .agent/skills/skill-master/scripts/registry_manager.py
   

Phase 4: Skill Execution

Goal: Invoke the skill to complete the user's original task.

CRITICAL: You MUST invoke the found/created skill using the Skill tool. Do NOT manually follow the instructions - the skill must be triggered as an independent execution.

Step 4.1: Invoke the Skill

Use the Skill tool to trigger the skill:

Skill: <skill-name>