agentleFS
Sign inStart free
aayushostwalaayushostwal/nexus/skills/performance/SKILL.md

performance

Skill19 starsChanged 3 months agoMITView on GitHub

Use for memory, CPU, latency, and query-performance investigations, plus dependency-upgrade blast-radius analysis. Trigger on leak/OOM/profiling/regression reports or "what breaks if I upgrade X." Route to memory-leak or dependency-blast-radius workflow based on intent.

78 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use app-brief, design-from-app and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • StijnusSkill

    app-brief

    One-page brief (docs/BRIEF.md) for a new macOS app, written before any code. Use when the user has an app idea, wants to replace an app they pay for, or the research and clone skills are done.

    Also in 3 projects that use this

  • StijnusSkill

    design-from-app

    Rebuild the look of an app the user likes as a native SwiftUI design kit, by measuring its screenshots (sizes, spacing, type, colors, icons), building its parts, and comparing pixel by pixel until they match. Use when the user names an app whose look they want, shares screenshots of one, or says "make it look like X".

    Also in 3 projects that use this

  • FlorianBruniauxSkill

    tdd-rust

    Also in 3 projects that use this

  • RodrigoTomeESSkill

    web-quality-audit

    Comprehensive web quality audit covering performance, accessibility, SEO, and best practices. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website".

    Also in 9 projects that use this

  • launchapp-devSkill

    layout-grid

    Define responsive layout grid systems with columns, gutters, margins, and breakpoint behavior.

    Also in 3 projects that use this

  • MohamedAbdallah-14Skill

    app-icon

    Generate an app icon from a single 1024² master and fan out to iOS (AppIcon.appiconset with squircle-ready 1024 opaque), Android (adaptive foreground + background + Android 13 monochrome), PWA (192/512 + 512 maskable with 80% safe zone), and visionOS (3-layer parallax).

    Also in 3 projects that use this

  • +1 more from Stijnus

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 5 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 52 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the request does not clearly fit one track, ask one question: "Is this about memory/CPU/latency behavior of a running service, or about …

    line 37
  2. Very specific:

    Read the appropriate sub-skill file.

    line 42
  3. Very specific:

    Read heuristics/performance-heuristics.md for fast pattern-matching before starting investigation.

    line 43
  4. Very specific:

    Before presenting results, check against validation/output-validation.md.

    line 47
  5. Distinctive:

    Never profile a running production process without confirming the profiling overhead is acceptable.

    line 59
  6. Distinctive:

    Never recommend a dependency upgrade without completing the blast radius analysis first.

    line 60
  7. Distinctive:

    Never mix tracks — complete one sub-skill fully before considering another.

    line 61
  8. Distinctive:

    Never skip reading the actual code or configuration — performance issues are almost always specific to the exact version and usage pattern.

    line 62
  9. Distinctive:

    Never recommend "just increase memory/CPU limits" without first identifying the root cause — scaling a leak just delays the next OOM.

    line 63

“Common” is measured: kept by at least 6 in 10 of the 52 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

Nexus Performance

Route to the correct sub-skill and follow it end-to-end.

Compatibility

  • Sub-skills: memory-leak.md, dependency-blast-radius.md
  • Supporting files: examples/production-scenarios.md, checklists/performance-checklist.md, heuristics/performance-heuristics.md, anti-patterns/common-mistakes.md, validation/output-validation.md
  • Required tools: Read, Bash, Grep
  • Hands off to: nexus:debugging for single-service runtime failures
  • Hands off to: the roadmap-planner agent after the fix is approved

Routing

Step 1 — Classify the Request

Pick exactly one track:

TrackSignalSub-skill
Memory Leak"memory growing", "OOM kill", "heap dump", "RSS increasing", "memory usage creeping up", process being killed by the OSmemory-leak.md
Dependency Blast Radius"upgrade X to version Y", "what breaks if I upgrade", "which services use this lib", "blast radius of upgrading", "safe to upgrade?", "dependency impact analysis"dependency-blast-radius.md

If the request does not clearly fit one track, ask one question: "Is this about memory/CPU/latency behavior of a running service, or about the risk of upgrading a dependency?"

Step 2 — Read Sub-Skill and Execute

Read the appropriate sub-skill file. Follow its numbered steps in order. Do not skip steps. Read heuristics/performance-heuristics.md for fast pattern-matching before starting investigation.

Step 3 — Validate Output

Before presenting results, check against validation/output-validation.md.

Output Format

Each sub-skill defines its own output format. This router produces no standalone output.

Anti-Patterns

  • Never profile a running production process without confirming the profiling overhead is acceptable.
  • Never recommend a dependency upgrade without completing the blast radius analysis first.
  • Never mix tracks — complete one sub-skill fully before considering another.
  • Never skip reading the actual code or configuration — performance issues are almost always specific to the exact version and usage pattern.
  • Never recommend "just increase memory/CPU limits" without first identifying the root cause — scaling a leak just delays the next OOM.

Examples

"Memory usage is growing by 50MB per hour and the process gets OOM killed every 12 hours" → route to memory-leak.md

"We want to upgrade SQLAlchemy from 1.4 to 2.0 — what will break?" → route to dependency-blast-radius.md

"Our API latency is 3× higher than yesterday after the last deploy" → route to memory-leak.md if memory metrics are elevated; otherwise route to nexus:debugging

"Which of our services import requests==2.28.0 and would be affected by this CVE patch upgrade?" → route to dependency-blast-radius.md

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.

Check your setup, free