perf-analysis
Skill2 starsChanged 7 days agoApache-2.0View on GitHub
Analyze session performance — duration, phase breakdown, token usage, bottlenecks, efficiency trends, and concrete improvement suggestions. Use for "/perf-analysis", "performance analysis", "Performance-Analyse", "warum ist das so langsam", "wie lange dauert ein Testlauf", "Token-Verbrauch analysieren", "Performance verbessern", "Kosten optimieren". Not for test quality metrics (/qa-report) or skill usage (/skill-review).
3 other projects use a version of this.
Adopted by
Most recently taken up by
- dotnet/mauitheir own version, first seen Oct 8, 2026
- Saddss/cursor-skillstheir own version, first seen Aug 29, 2026
- NVIDIA/TensorRT-LLMtheir own version, first seen Aug 17, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- dotnet/maui★ 23ksame name
- NVIDIA/TensorRT-LLM★ 15ksame name
- Saddss/cursor-skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- accessibility-testingSkill
- agentswitchSkill
- api-testingSkill
- bug-reportSkill
- bug-reproductionSkill
- demoSkill
- deploy-to-stageSkill
- exploratory-testingSkill
- failure-analysisSkill
- model-setupSkill
- onboard-productSkill
- onboard-projectSkill
- qa-helpSkill
- qa-metricsSkill
- qa-reportSkill
- re-boardSkill
- reconSkill
- release-readinessSkill
- report-to-jiraSkill
- retest-bugSkill
- retro-learnSkill
- risk-based-testingSkill
- scaffold-suiteSkill
- security-testingSkill
- skill-reviewSkill
- test-automationSkill
- test-case-managementSkill
- test-reliabilitySkill
- test-ticketSkill
- visual-testingSkill
- webdriverio-testingSkill
- whats-newSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Read the report. The summary table shows where you stand against targets.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/perf-analysis — how long does it take, what does it cost, and what should change
The blueprint writes timing and usage data for every run — and never reads it back. This turns that data into the numbers that answer "why is this slow?" and "what should we fix?" — with concrete, actionable suggestions.
Steps
- Run the analysis:
python3 .claude/skills/perf-analysis/perf-analysis.py --since 30 --suggest
# --project SHOP one project only
# --ticket SHOP-123 one specific run
# --json machine-readable output- Read the report. The summary table shows where you stand against targets; the phase breakdown shows where time goes; the suggestions section names bottlenecks with specific fixes.
- Interpret against the project's gates (
PROJECT.md→ "Pipelines / quality gates") — if the project declares tighter targets, those win. - Turn red/yellow items into actions. Each suggestion maps to a concrete
skill or workflow change (see
references/improvement-patterns.mdfor the full pattern library). - Report the findings. For a team: use
report-to-jiraor the project's reporting format. For a quick look: just print the report.
What this skill never does
- Never estimates — if a metric can't be computed from the data, it says "not computable" rather than guessing.
- Never mutates — this is read-only. It doesn't change configs, tests, or project files. Improvement suggestions are proposals, not automatic fixes.
- Never duplicates
/qa-reportnumbers — pass rate, flake rate, and findings belong to qa-report. This skill focuses on time and cost. - Never reads transcripts — token usage and model affinity come from
session-perf.log(Stop-hook-extracted metadata), never content.
Data sources
| Source | What it provides |
execution_summary.json | verdict, duration_s, phases, session, test_cases |
run.json | duration_s, result counts |
evidence/.audit/session-perf.log | token usage per session + measured model affinity (model=, model_switches=) |
evidence/.audit/compression.log | measured compression bytes per seal (run, mode, original/compressed) |
evals/results/history.log | pass-rate trend |
Fields not yet in older summaries are simply absent — the analysis reports what's available and notes what's missing.
Command surface
/perf-analysis [--since DAYS] [--project KEY] [--ticket KEY]
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

