perf-theory-gatherer — Claude Code skill: performance hypotheses
A skill that turns git history and code evidence into up to five hypotheses about a performance problem.
npx skills add composio-community/awesome-claude-plugins --skill perf-theory-gatherer -a claude-code
npx skills add composio-community/awesome-claude-plugins --skill theory -a claude-codeWhat perf-theory-gatherer does
You describe a scenario, and the skill walks it in order: recent git history scoped to the relevant paths, then the code paths involved, found through a repo map or grep. What comes back is a list of hypotheses, each with evidence and a confidence level of low, medium or high. Five is the ceiling.
The output shape is fixed. Every hypothesis gets an id, a short description, a file path or git change as evidence, and a confidence rating. Checking git history is mandatory before any hypothesis is written. The skill does not suggest optimizations — it only names possible causes.
It follows docs/perf-requirements.md as the canonical contract, so that file needs to exist in your repo. Without it the skill has no agreed requirements for the performance work, which is worth checking before you run it.
What it helps with
- turn commit history into candidate causes of a slowdown
- locate the code paths a given scenario touches
- separate hypotheses from ready-made optimization advice
- tie every hypothesis to a file or git change
- cap the investigation at five prioritized hypotheses
Example prompts for the agent
- review git history for the slow order list scenario and give me hypotheses with evidence
- why is the report export slow — find the code paths and list up to five causes
- check recent commits in the search module and produce hypotheses with confidence levels
How to install perf-theory-gatherer
1Skills CLI (Vercel)
npx skills add composio-community/awesome-claude-plugins --skill perf-theory-gatherer -a claude-codenpx skills add composio-community/awesome-claude-plugins --skill theory -a claude-code2Manually: put the files in place
~/.claude/skills/theory/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/theory/
1Skills CLI (Vercel)
npx skills add composio-community/awesome-claude-plugins --skill theory -a codex2Manually: put the files in place
.agents/skills/theory/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add composio-community/awesome-claude-plugins --skill theory -a cursor2Manually: put the files in place
.cursor/skills/theory/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install composio-community/awesome-claude-plugins theory2Manually: put the files in place
.github/skills/theory/SKILL.md1Skills CLI (Vercel)
npx skills add composio-community/awesome-claude-plugins --skill theory -a gemini-cli2Platform CLI
gemini skills install https://github.com/composio-community/awesome-claude-plugins --path perf/skills/theoryManually: put the files in place
.devin/skills/theory/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add composio-community/awesome-claude-plugins --skill theory -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about perf-theory-gatherer
How do I install perf-theory-gatherer in Claude?
Run npx skills add composio-community/awesome-claude-plugins --skill perf-theory-gatherer -a claude-code. The skill then lives at ~/.claude/skills/theory/SKILL.md.
What does perf-theory-gatherer do?
It reads git history and code for a scenario you name and returns up to five hypotheses about performance causes, each with evidence and a confidence rating.
Does it need docs/perf-requirements.md?
Yes, the skill treats it as the canonical contract. Without that file in the project it has no agreed requirements for the performance investigation.