/skill-distill: Skill & Tool Audit

You are a systems curator. Your job is to audit what's installed, classify each item honestly, present a clear report, and execute only user-approved actions.

Symmetric pair with repo-analyst:

repo-analyst:   external repo  → analyze → should we adopt?
skill-distill:  internal system → audit   → should we keep?

Modes

Parse the invocation to determine the mode before starting Phase 1.

Phase 1: Inventory

Full System Mode

Enumerate every entry in ~/.claude/skills/:

• Use Glob tool with pattern ~/.claude/skills/*/SKILL.md to list all skills

For each entry, collect the following fields:

Name — directory name.

Purpose — Use Read tool to read each skill's SKILL.md frontmatter description field.

Origin — Use Bash ls -la ~/.claude/skills/ | grep "^l" to identify symlinks vs. self-built directories.

Complexity — Use Read tool to read each SKILL.md (line count from output). Use Glob with pattern ~/.claude/skills/<skill>/prompts/* to check for prompts/ subdirectory.

Dependencies — Use Grep tool to search across all SKILL.md files:

• Pattern ~/bin/ to find binary dependencies
• Pattern API|api_key|ANTHROPIC|GEMINI|OPENAI to find API dependencies

Build and present the full inventory table before proceeding:

## Inventory: ~/.claude/skills/

| # | Skill | Origin | Lines | Has prompts/ | Dependencies | Overlap |
|---|-------|--------|-------|-------------|-------------|---------|
| 1 | qa | self-built | 248 | no | ~/bin/browse | unique |
| 2 | repo-analyst | self-built | 48 | yes (3) | none | pair: skill-distill |
...

Note: This audit covers ~/.claude/skills/ only. Skills from other sources (e.g., superpowers:* skills) are outside the managed scope. Mention their existence in the report if relevant to overlap detection.

Single Tool Mode

Read the tool's directory structure and enumerate all sub-features:

• Use Glob tool with pattern <target-path>/**/*.md to find all markdown files
• Use Glob tool with pattern <target-path>/**/SKILL.md to count sub-skills

For bundled skill packs (multiple SKILL.md files or a skills/ subdirectory inside):

• Use Read tool to read the frontmatter of each discovered SKILL.md

List each sub-skill separately. Read its description from the file header. Note if the parent pack has telemetry, config systems, or heavy runtime dependencies.

Phase 2: Classify

Assign exactly one tag per item using this priority order. Never skip steps — start at priority 1 and work down.

Overlap Detection

Compare descriptions across the full inventory. When two or more skills cover the same domain or offer similar actions, flag them as a group:

### Overlap Groups
- Group A: skill-x, skill-y — both do Z. Recommend keeping skill-x because [reason].

Per-item Classification Output

For each item, write:

• The tag
• One-sentence reason
• If [REDUNDANT]: name the replacement skill
• If [DISTILL]: describe what the new standalone skill would contain
• If [INTERNALIZE]: describe what to record in memory

Phase 3: Report + Action Menu

Present the Report

## Audit Report: <target>

**Summary:** N scanned — K keep, R redundant, D distill, I internalize, X inert

| # | Skill | Tag | Reason | Suggested Action |
|---|-------|-----|--------|------------------|
| 1 | ... | [REDUNDANT] | replaced by X | Remove |
| 2 | ... | [DISTILL] | unique QA workflow | Extract as /new-name |
| 3 | ... | [KEEP] | working well | No action |
| 4 | ... | [INERT] | unused, no clear value | Remove |
...

### Overlap Groups
(list if any detected)

### Dependency Map
- ~/bin/browse: used by qa, design-review
- Gemini API: used by meetingscribe

Action Menu

After the report, ask:

Which items to execute? Enter numbers (e.g., 1,2,5) or "all":
(KEEP items are excluded — they require no action)

Wait for the user's response before executing anything.

Execute Selected Items

Execute one item at a time. Confirm before each removal. Do not batch.

[REDUNDANT] — Remove with backup:

1. Use Read tool to read the full skill content (~/.claude/skills/<skill>/SKILL.md)
2. Append the complete content to the decision note (full text, not summary)
3. State: "Removing <skill> — replaced by <replacement>. Confirm? (y/n)"
4. On confirm:

   # If symlink: unlink only, never delete target
   if [ -L ~/.claude/skills/<skill> ]; then
     unlink ~/.claude/skills/<skill>
   else
     mv ~/.claude/skills/<skill> ~/.Trash/
   fi
   

[INTERNALIZE] — Record to memory, then remove:

1. Use Read tool to read the full skill content (~/.claude/skills/<skill>/SKILL.md)
2. Write the process/knowledge to a memory file:
   • Cross-project pattern (applicable everywhere) → write to ~/.claude/instincts/
   • Project-specific process (only relevant to one project) → write to the current project's memory directory Write a concise, actionable memory entry. Not a copy of the skill — extract the key steps.
3. Append the complete original content to the decision note (backup)
4. State: "Removed <skill> — process saved to memory at <memory-path>. Confirm removal? (y/n)"
5. On confirm:

   mv ~/.claude/skills/<skill> ~/.Trash/
   

[DISTILL] — Extract, then remove:

1. Use Read tool to read the full skill content. Use Glob to list all files in the skill directory.
2. Create a new standalone skill in ~/.claude/skills/<new-name>/SKILL.md:
   • Consult pipeline-skill-pattern if the new skill needs stages/phases
   • Strip tool-specific dependencies (telemetry, runtime config systems, etc.)
   • Keep only the core workflow and reusable knowledge
   • Write proper YAML frontmatter with name and description
3. Use Read tool to verify the new skill file exists and has content.
4. Append the complete original content to the decision note (backup)
5. State: "Created /new-name. Removing original <skill>. Confirm? (y/n)"
6. On confirm:

   mv ~/.claude/skills/<skill> ~/.Trash/
   

[INERT] — Remove with backup:

1. Use Read tool to read the full skill content. If no SKILL.md, use Glob to list directory contents.
2. Append the complete content to the decision note (backup)
3. State: "Removing <skill> — unused, no clear value. Confirm? (y/n)"
4. On confirm:

   if [ -L ~/.claude/skills/<skill> ]; then
     unlink ~/.claude/skills/<skill>
   else
     mv ~/.claude/skills/<skill> ~/.Trash/
   fi
   

Decision Note

After all executions are complete (or at end of session if no removals), write a decision note for future reference.

Where to write: Ask the user where they keep decision logs (e.g., an Obsidian vault, a docs/ directory, or any preferred location). If the user has a notes directory configured in their CLAUDE.md, use that.

Filename pattern:

skill-distill <target> audit YYYY-MM-DD.md

Note structure:

---
type: permanent
tags: [skill-audit, decision-log]
related: [skill-distill]
date: YYYY-MM-DD
---

# s