Skill Discovery

Skill Discovery

Context-aware lazy loader. Discovers and loads skills on-demand based on task signals instead of loading everything at startup.

When to Activate

Run this protocol at the START of every task. Skip only when:

• Task is trivially simple (single-line fix, typo correction)
• All needed skills are already loaded in your skills: list
• Task is purely conversational (no code/architecture work)

Step 1: Detect Task Signals

Gather signals from three sources:

1a. Platform Signals

Check request keywords → git diff extensions → CWD path:

Multiple platforms: ask user (max 1 question). If 80%+ files = one platform, use that.

Platform Detection Priority

1. Explicit hint in user request ("ios", "web", etc.) → highest priority
2. File extensions in git diff or $ARGUMENTS paths → high
3. CWD path segments (e.g., inside ios/, android/) → medium
4. Project markers (Package.swift → ios, build.gradle.kts → android, package.json → web, pom.xml → backend) → low

1b. Task Type Signals

Scan the user request for these patterns:

1c. Domain Signals (from git context)

• Files in module-specific directories → domain skills
• Infrastructure files (Dockerfile, terraform/) → infra skills

Step 2: Query Skill Index

Read .github/skills/skill-index.json. Filter candidates:

For each skill in index:
  SKIP if skill.name is in your loaded skills: [] list (already have it)
  SKIP if skill.tier == "core" and not matching signals (core skills load via skills: list)
  MATCH if:
    - skill.name starts with detected platform prefix (ios-, web-, etc.)
    - skill.platforms contains detected platform
    - skill.keywords intersect with detected task type signals
    - skill.agent-affinity includes your agent name

Step 2b: Resolve Dependencies

After matching candidates, resolve their connection graph:

For each matched skill:
  1. EXTENDS: Prepend parent(s) to load list. Max 3 hops.
     Example: ios-a11y extends a11y → load a11y first, then ios-a11y
  2. REQUIRES: Add required skills to load list.
     Example: kit-add-agent requires kit-agent-development → auto-add
  3. CONFLICTS: If two matched skills conflict, keep higher-priority one.
     Warn: "Dropped {lower} — conflicts with {higher}"

Dependency skills (extends/requires) do NOT count toward the "max 3" direct match limit.

Load order: bases first (extends parents → requires → matched skill).

Step 3: Select and Load (Token Budget)

Hard limits:

• Max 3 directly matched skills per task (dependencies don't count toward this)
• Max 15 KB total skill content (approximately 3,750 tokens)
• Prefer smaller skills that cover the need

Ranking (highest → lowest priority):

1. Platform skills matching detected platform
2. Skills where agent-affinity lists your agent name
3. Skills matching task-type signals from Step 1b
4. Skills matching domain signals from Step 1c

For each selected skill: Read its SKILL.md. Extract actionable patterns, constraints, conventions. Apply to your task.

After loading: Check each loaded skill's connections.enhances list. If any enhancers are relevant but not loaded, suggest them:

"Also available: problem-solving (enhances debugging)"

Do NOT auto-load enhancers. Only suggest them.

Step 4: Apply Discovered Knowledge

Integrate loaded skill knowledge into your current task:

• Architect: Platform constraints in plan phases, framework-specific steps
• Implementer: Code patterns, testing approach, UI components
• Debugger: Platform debugging tools, common pitfalls, logging patterns
• Tester: Test frameworks, assertion patterns, coverage tools
• Reviewer: Platform conventions, anti-patterns, security concerns
• Orchestrator: Route to correct specialist, inform task decomposition

Quick Reference: Common Discovery Paths