CtrlK
BlogDocsLog inGet started
Tessl Logo

perf-theory-gatherer

Use when generating performance hypotheses backed by git history and code evidence.

55

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./perf/skills/theory/SKILL.md
SKILL.md
Quality
Evals
Security

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.
Repository
composio-community/awesome-claude-plugins
Path

perf/skills/theory/SKILL.md

Commit

e521f7a

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.

Claim skill