triage

/triage — Skills Portfolio Triage Management

Based on the ablation experiment results of skills-ecosystem-eval, manage the lifecycle of learned skills.

Step 0: Check Tools

Confirm ~/.claude/scripts/skills-triage.sh exists and is executable (ls -la ~/.claude/scripts/skills-triage.sh). If it does not exist, prompt to copy it first from the agent-skills repo:cp ~/Documents/agent-skills/triage/skills-triage.sh ~/.claude/scripts/ && chmod +x ~/.claude/scripts/skills-triage.sh。

Step 1: View Status

~/.claude/scripts/skills-triage.sh status

Display the number retired, the list, and the audit log. If /skill-health command is available, it is recommended to run it first to get a global view of the portfolio (duplicate coverage rate, gap analysis), then decide the retirement priority order.

Step 2: Retire Skill

When the user provides a skill name and reason:

~/.claude/scripts/skills-triage.sh retire <name> "<reason>" <tier> <delta>

• tier: T1 (degraded), T2 (Q3 delta=0), T3 (other)
• delta: the delta value of the ablation experiment

Before retiring, confirm:

1. Read the skill content and summarize it for the user
2. Confirm the user agrees to retire

Pre-retirement impact analysis: Before the user confirms, first check whether this skill is referenced elsewhere — grep ~/.claude/skills/learned/、~/.claude/rules/、~/.claude/CLAUDE.md and project CLAUDE.md, and organize the results:

Reference source	Reference location	Impact
(no references)	—	Safe to retire
other-skill.md	Line 12	After retirement, other-skill may change behavior

If references exist, show the impact list to the user and let the user decide whether to continue retiring.

Step 3: Restore Skill

~/.claude/scripts/skills-triage.sh restore <name>

After restoration, verify the skill file returns to ~/.claude/skills/learned/。

Step 4: Batch Processing

When the user provides ablation data (such as full-analysis.json):

1. Read the data, filter skills with delta < 0, and sort by absolute delta value

2. List the skills to be retired (i.e., the table below,the table itself is the tracking baseline and denominator), and perform the Step 2 impact analysis for each (grep search for references):

   Skill	Delta	Tier	Dependency relationship
   skill-a.md	-0.23	T1	None
   skill-b.md	-0.10	T2	Referenced by skill-c

   Skills with dependency relationships must be confirmed with the user before retirement and cannot be retired automatically in batches; those without dependency relationships can be retired in batches after being confirmed one by one

3. Retire after confirming one by one, and after each retirement mark that row's status on the table (if the session has a Task tool, it can additionally be used to TaskCreate/TaskUpdate mirror; the default model does not have these tools, see rules/task-tracking-availability.md）

Step 5: Post-Retirement Integrity Verification

After batch retirement is complete, verify each skill marked as done:

• no longer in ~/.claude/skills/learned/ (ls ~/.claude/skills/learned/<skill-name>.md should come up empty)
• the skill name has appeared in ~/.claude/skills/retired/RETIRED_LOG.md in

If any item does not hold, the retirement is considered incomplete and manual intervention is required; that task must not be marked as complete.

Key Paths

Path	Purpose
~/.claude/skills/learned/	Active skills
~/.claude/skills/retired/	Retired archive
~/.claude/skills/retired/RETIRED_LOG.md	Audit log
~/.claude/scripts/skills-triage.sh	Batch script