Skip to main content
skill CX Codex

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.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
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-code
Open on GitHub

What 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-code
npx skills add composio-community/awesome-claude-plugins --skill theory -a claude-code

2Manually: put the files in place

~/.claude/skills/theory/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/theory/

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.

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set8

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor