performance-monitor
Skill31 starsChanged 4 months agoMITView on GitHub
Use when a task needs ongoing performance-signal interpretation across build, runtime, or operational metrics before deeper optimization starts.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- mysleekdesigns/crawlforge-mcptheir own version, first seen Oct 11, 2026
- code-with-mehedi/nextjs-claude-startertheir own version, first seen Aug 25, 2026
- belokonm/claude-supercode-skillstheir own version, first seen Jan 12, 2026
- lodetomasi/claude-code-skills-toolstheir own version, first seen Oct 24, 2025
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- belokonm/claude-supercode-skills★ 11same name
- mysleekdesigns/crawlforge-mcp★ 6same name
- code-with-mehedi/nextjs-claude-starter★ 0same name
- lodetomasi/claude-code-skills-tools★ 0same 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 repository175 other files it gives its agents.
- ab-test-analysisSkill
- accessibility-testerSkill
- ad-security-reviewerSkill
- agent-installerSkill
- agent-organizerSkill
- ai-engineerSkill
- ai-governance-auditorSkill
- ai-observability-engineerSkill
- ai-writing-auditorSkill
- angular-architectSkill
- anti-ui-slop-reviewerSkill
- api-designerSkill
- api-documenterSkill
- architect-reviewerSkill
- assumption-mappingSkill
- azure-databricks-platform-architectSkill
- azure-infra-engineerSkill
- backend-developerSkill
- backlog-groomingSkill
- backstage-specialistSkill
- blockchain-developerSkill
- browser-debuggerSkill
- build-engineerSkill
- business-analystSkill
- chaos-engineerSkill
- cli-developerSkill
- cloud-architectSkill
- codebase-orchestratorSkill
- code-mapperSkill
- code-reviewerSkill
- cohort-analysisSkill
- competitive-analystSkill
- compliance-auditorSkill
- content-marketerSkill
- content-quality-editorSkill
- context-managerSkill
- cpp-proSkill
- csharp-developerSkill
- customer-success-managerSkill
- data-analystSkill
- database-administratorSkill
- database-optimizerSkill
- data-engineerSkill
- data-researcherSkill
- data-scientistSkill
- debuggerSkill
- dependency-managerSkill
- deployment-engineerSkill
- design-bridgeSkill
- devops-engineerSkill
- devops-incident-responderSkill
- django-developerSkill
- docker-expertSkill
- docs-researcherSkill
- documentation-engineerSkill
- dotnet-core-expertSkill
- dotnet-framework-4.8-expertSkill
- dx-optimizerSkill
- electron-proSkill
- elixir-expertSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
5
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 33
verify observed movement exceeds expected baseline noise
- Distinctive: line 35
check for confounders (traffic mix, synthetic tests, instrumentation drift)
- Distinctive: line 36
ensure next-step recommendation is specific and executable
- Distinctive: line 37
call out missing telemetry needed to avoid misrouting effort
- Distinctive: line 46
Do not label correlation as confirmed causality unless explicitly requested by the parent agent.
“Common” is measured: kept by at least 6 in 10 of the 4 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
Instructions
Own performance signal triage as early-warning interpretation before deep optimization work begins.
Distinguish meaningful regressions from noise and route investigation to the right owner quickly.
Working mode:
- Map metric movement by timeframe, subsystem, and recent change context.
- Separate signal from noise using baseline variance and impact magnitude.
- Identify most probable ownership boundary for deeper investigation.
- Recommend next diagnostic step with highest information gain.
Focus on:
- metric definition integrity and comparability across periods/environments
- severity weighting by user impact and business-critical path relevance
- correlation with releases, config changes, and workload shifts
- dominant resource signal (CPU, memory, IO, latency, queueing) classification
- confidence scoring for likely owner subsystem
- alert fatigue reduction through prioritized triage output
- handoff readiness for specialist performance engineering follow-up
Quality checks:
- verify observed movement exceeds expected baseline noise
- confirm candidate root-area ranking includes confidence and caveats
- check for confounders (traffic mix, synthetic tests, instrumentation drift)
- ensure next-step recommendation is specific and executable
- call out missing telemetry needed to avoid misrouting effort
Return:
- concise performance summary and impact assessment
- likely owner area(s) with confidence ranking
- probable trigger candidates and evidence basis
- next investigative action and why it is highest leverage
- data gaps and monitoring improvements needed
Do not label correlation as confirmed causality unless explicitly requested by the parent agent.
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.

