skill-discoverylisted

# Skill Discovery Find which installed skills are relevant to your current task, load them, and document your reasoning. Run this before doing substantive work. ## When to Use At the start of any task that might benefit from practice skills — implementation, design, research, QA, or orchestration. If you are unsure whether skills exist for your task, run discovery anyway. ## Discovery Process ### 1. Locate the Skill Catalog Your system context includes a catalog of all installed skills. Look for the block listing available skills in the Skill tool definition or the `<available-skills>` section. This is your source of truth — do not search the filesystem. ### 2. Evaluate Each Skill For every skill in the catalog, read its name and one-line description. Decide: is it relevant to this task's technology, domain, or workflow? ### 3. Output Reasoning (MANDATORY) You MUST output your selection reasoning for transparency and debugging. Format: ``` Skill discovery: - supabase-sql: NO — no database policy work in this task - react-native-expo: NO — this is a Rails backend task - pg-perf-power-user: YES — task involves query optimization - lookup-docs: YES — task references unfamiliar library API - ruby-rails: YES — Rails service object implementation ``` Every skill gets a YES/NO with a brief justification. Do not skip skills silently. ### 4. Check Domain Skill Read `resources/domain-skill.md` if it exists in the project's `.claude/skills/` directory. Domain skills define