agentleFS
Sign inStart free
NinjaSln-labsNinjaSln-labs/agent-skills/perf-check/SKILL.md

perf-check

Skill1 starsChanged 41 days agoNo licenceView on GitHub

Machine performance check: read-only sampling diagnosis of the dev machine's speed — memory pressure (MemAvailable gauge, swap thrash rate), CPU (load vs cores, utilization sampling), WSL2 resource tuning (cgroup ceilings, .wslconfig with autoMemoryReclaim advice), disk IO await per device, top CPU/memory processes, and macOS memory pressure (compressor gauge). Judgements follow the USE method; every threshold carries a basis tag (consensus vs heuristic). Read-only, tuning suggestions are commands for the user — never executed. Use when the machine feels slow, builds stall, memory pressure or swap activity is suspected, a process eats CPU/memory, disk latency is suspect, or WSL2 vmmem/VM sizing needs review. NOT for: runnability checks (env-check), application load testing, or AI session health.

3 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

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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