skill-usage-log-reviewer

Skill Usage Log Reviewer

This skill audits your installed Claude skill collection — identifying which skills you actively use, which are dormant, and which overlap with each other. It outputs a structured audit report with a one-click deactivation checklist, helping you keep your skill portfolio lean and your sessions fast.

Input:

• List of installed skill names (paste, file listing, or description)
• Optional: brief usage notes per skill ("used daily", "tried once", "never used")

Output:

• skill-audit-report.md — table with Keep / Review / Deactivate verdicts, reasoning, and a deactivation checklist

---

Language Detection

Detect the user's language from their message:

• If Russian (or contains Cyrillic): respond in Russian
• If English (or other Latin-script language): respond in English
• If ambiguous: respond in the language of the trigger phrase used

---

Instructions

Step 1: Collect the Skill List

1. Check if Claude can see the installed skills from the conversation context (e.g., available_skills list or plugin manifest). If yes — use it directly; do not ask the user.
2. If not available from context: ask the user to provide their skill list.
   • Accepted formats: pasted names, ls output from skill folder, plugin manifest text, or free-form description
3. Validate input is non-empty.
   • If empty: stop and respond — "No skills listed. Please paste your installed skill names, or describe which skills you have active in Claude."
4. Check if input looks like a conversation transcript or unrelated text (no skill names detectable):
   • If detected: stop and respond — "This doesn't look like a skill list. Please provide the names of your installed Claude skills."

---

Step 2: Collect Usage Context

1. Check if the user already provided usage notes alongside the skill list (e.g., "skill-x — used daily", "skill-y — never tried").
   • If usage notes are present for all skills: skip to Step 3.
2. If usage notes are absent or partial: gather usage context with targeted questions.
   • Group skills into batches of 5–8 and ask: "For each skill below, tell me roughly how often you use it: daily / weekly / monthly / never."
   • Do not ask per-skill individually — batch questions to reduce friction.
3. If the user declines to answer usage questions: default all skills to "Unknown" and note this in the report; still run the duplicate detection step.