skill-discovery

1. **Project-level** (highest priority):
   - .claude/skills/**/SKILL.md

2. **Local plugins** (if .claude-plugin/ exists):
   - .claude-plugin/*/skills/**/SKILL.md

3. **Plugin directories** (workspace plugins):
   - plugins/*/skills/**/SKILL.md

4. **Home directory** (user-wide, lowest priority):
   - ~/.claude/skills/**/SKILL.md

</skill_locations>

<discovery_workflow> Use Glob to find all SKILL.md files: Glob: .claude/skills/**/SKILL.md Glob: .claude-plugin/*/skills/**/SKILL.md Glob: plugins/*/skills/**/SKILL.md

  Note: Skip ~/.claude/skills/ unless explicitly requested
  (user-wide skills may not be relevant to specific project)
</step>

<step number="2" name="Parse Frontmatter">
  For each discovered SKILL.md:

  1. Read the file
  2. Extract YAML frontmatter between --- markers
  3. Parse required fields:
     - name (string, required)
     - description (string, required)
  4. Parse optional fields:
     - keywords (array)
     - category (string)
     - dependencies (array)
</step>

<step number="3" name="Infer Categories">
  If skill doesn't have explicit category, infer from:

  1. **Path analysis**:
     - /testing/ → "testing"
     - /frontend/ → "frontend"
     - /backend/ → "backend"
     - /workflow/ → "workflow"

  2. **Name analysis**:
     - "tdd-*", "*-test" → "testing"
     - "debug-*" → "debugging"
     - "react-*", "vue-*" → "frontend"
     - "api-*", "db-*" → "backend"

  3. **Description keywords**:
     Match against keyword list (see <category_keywords>)
</step>

<step number="4" name="Build Catalog">
  Create structured catalog:
  ```json
  {
    "total_count": 5,
    "by_source": {
      "project": 2,
      "plugin": 3
    },
    "by_category": {
      "testing": ["tdd-workflow", "unit-testing"],
      "frontend": ["react-patterns"],
      "backend": ["api-design", "db-patterns"]
    },
    "skills": [
      {
        "name": "tdd-workflow",
        "description": "Test-driven development workflow",
        "path": ".claude/skills/tdd-workflow/SKILL.md",
        "source": "project",
        "categories": ["testing", "workflow"],
        "keywords": ["tdd", "red-green-refactor"],
        "priority": 1
      }
    ]
  }
  ```
</step>

<step number="5" name="Match to Task">
  If a task description is provided, rank skills by relevance:

  1. **Exact keyword match** (+10 points)
  2. **Category match** (+5 points)
  3. **Description similarity** (+1-3 points)
  4. **Project source bonus** (+2 points)

  Return skills sorted by relevance score.
</step>

</discovery_workflow>

<category_keywords> testing: - test, tdd, spec, coverage, assertion, mock, stub, fixture - jest, vitest, pytest, testing-library, cypress, playwright

debugging:
  - debug, trace, diagnose, log, breakpoint, error, exception
  - stack trace, profiling, performance

frontend:
  - react, vue, svelte, angular, component, ui, ux
  - css, style, layout, responsive, animation, a11y

backend:
  - api, server, endpoint, route, handler, middleware
  - rest, graphql, grpc, websocket