| name | finding-skill-opportunities |
| description | Use when asked to find skill opportunities in a codebase, audit a repo for automatable workflows, decide what skills to write, or mine git history and existing automation for recurring multi-step procedures worth turning into Claude Code skills. |
Finding Skill Opportunities
Overview
A skill opportunity is a recurring, multi-step procedure that involves judgment and keeps getting repeated by hand. Git history and a codebase's existing automation are the evidence: the procedures a team performs over and over leave fingerprints — repeated commit types, files that always change together, release/migration keywords, half-written Makefile targets and runbook docs.
This skill scans those fingerprints deterministically (via the bundled scripts) so you don't eyeball thousands of commits, then applies judgment to turn the raw signals into a ranked list of skill candidates with evidence.
Core principle: Let the scripts find the repetition; you decide which repetitions are worth a skill.
When to Use
- "What skills should we write for this repo?"
- Auditing a codebase for automatable or skill-worthy workflows
- Onboarding to an unfamiliar repo and wanting to know its recurring rituals
- Before writing skills, to ground them in real evidence instead of guesses
Not for: writing the skill itself (use superpowers:writing-skills once you've picked a candidate) or one-off tasks with no repetition.
Workflow
Run the two scripts, then synthesize. Both are read-only and deterministic.
-
Mine git history for repetition signals:
bash "${CLAUDE_SKILL_DIR}/scripts/git-signals.sh" --repo <path> --top 20
