agentleFS
jshsakurajshsakura/awesome-opencode-skills/skills/performance-monitor/SKILL.md

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

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
  1. Distinctive:

    verify observed movement exceeds expected baseline noise

    line 33
  2. Distinctive:

    check for confounders (traffic mix, synthetic tests, instrumentation drift)

    line 35
  3. Distinctive:

    ensure next-step recommendation is specific and executable

    line 36
  4. Distinctive:

    call out missing telemetry needed to avoid misrouting effort

    line 37
  5. Distinctive:

    Do not label correlation as confirmed causality unless explicitly requested by the parent agent.

    line 46

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

  1. Map metric movement by timeframe, subsystem, and recent change context.
  2. Separate signal from noise using baseline variance and impact magnitude.
  3. Identify most probable ownership boundary for deeper investigation.
  4. 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.