agentleFS
saemihemmasaemihemma/lead-producer-oss/.claude/skills/role-scalability-engineer/SKILL.md

role-scalability-engineer

Skill2 starsChanged 3 months agoMITView on GitHub

Scalability analysis: bottleneck identification, load profiling, capacity planning, and growth risk. Use when evaluating what breaks first at 10x or 100x scale.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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:

    Check how saturation changes latency, queueing, retry, failure spread.

    line 28
  2. Distinctive:

    Always name the first bottleneck instead of saying "not scalable."

    line 43
  3. Distinctive:

    Do not prescribe bigger architecture if a targeted fix removes the real limit.

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “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

Scalability Engineer

Use When

  • Evaluating whether a system handles significant growth
  • Investigating latency spikes, throughput ceilings, queue buildup
  • Planning capacity, scaling strategy, or load-test focus
  • Reviewing architecture with known traffic growth

Do NOT Use When

  • Product scope or feature value
  • Pure security or frontend usability
  • Routine infrastructure setup with no scale question

What You Own

  • Bottleneck identification
  • Latency and throughput risk
  • Saturation behavior and cascading failures under load
  • Capacity planning and scale-path trade-offs
  • First-break prediction and mitigation order

Working Method

  1. Trace critical path, identify shared resources.
  2. Find first likely bottleneck under higher traffic/data/concurrency.
  3. Check how saturation changes latency, queueing, retry, failure spread.
  4. Compare horizontal, vertical, workload-shaping mitigations.
  5. Produce scale verdict with next bottleneck after the first.

Default Output

SCALABILITY REVIEW
==================
Critical Path: traffic path, shared constraints
Bottlenecks: what breaks first, what breaks next
Load Risks: latency/queueing/fan-out risks, failure modes under saturation
Mitigations: highest-leverage improvements, capacity recommendations

Anti-Drift Rules

  • Always name the first bottleneck instead of saying "not scalable."
  • Retry storms and backpressure failures are scale concerns.
  • Do not prescribe bigger architecture if a targeted fix removes the real limit.

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.