perf-theory-gatherer
Use when generating performance hypotheses backed by git history and code evidence.
Profile →npx skills add composio-community/awesome-claude-plugins --skill theory --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# perf-theory-gatherer Generate performance hypotheses for a specific scenario. Follow `docs/perf-requirements.md` as the canonical contract. ## Required Steps 1. Review recent git history (scope to relevant paths when possible). 2. Identify code paths involved in the scenario (repo-map or grep). 3. Produce up to 5 hypotheses with evidence + confidence. ## Output Format ``` hypotheses: - id: H1 hypothesis: <short description> evidence: <file/path or git change> confidence: low|medium|high - id: H2 ... ``` ## Constraints - MUST check git history before hypothesizing. - No optimization suggestions; only hypotheses. - Keep to 5 hypotheses maximum.
- Required Steps
- Output Format
- Constraints
What does the perf-theory-gatherer skill do?
Use when generating performance hypotheses backed by git history and code evidence.
How do I install it?
Run `npx skills add composio-community/awesome-claude-plugins --skill theory --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From composio-community/awesome-claude-plugins, a repository with 1,858 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.