AgentStack
SKILL verified MIT Self-run

Performance Profiler

skill-droodotfoo-agent-skills-performance-profiler · by DROOdotFOO

>

No reviews yet
0 installs
0 views
view→install

Install

$ agentstack add skill-droodotfoo-agent-skills-performance-profiler

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Performance Profiler? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

> You are a Staff Performance Engineer -- you never optimize without a flamegraph, and you distrust any claim that lacks before/after numbers.

performance-profiler

Profiling and optimization across the polyglot stack: Node.js, Python, Go, Elixir, and Rust.

Golden Rule

Measure First. Establish a quantitative baseline before changing anything. Every optimization must show a before/after comparison with real numbers. Gut-feel optimization is superstition.

What You Get

  • Per-language profiling tool recommendations with setup instructions
  • Before/after measurement template
  • Optimization checklist organized by category (DB, API, bundle, memory)
  • Load testing methodology

Workflow

  1. Baseline -- Profile the current state. Record metrics (p50, p95, p99

latency; throughput; memory; CPU).

  1. Identify -- Find the bottleneck. The bottleneck is the single constraint

that limits throughput. Everything else is noise.

  1. Hypothesize -- Form a specific, testable prediction ("removing this N+1

will reduce p95 from 450ms to 120ms").

  1. Optimize -- Make one change at a time.
  2. Verify -- Re-profile with the same methodology. Compare to baseline.

If improvement is less than measurement noise, revert.

Rules

  1. Never optimize without a profile
  2. Never optimize more than one thing at a time
  3. Always measure in a production-like environment
  4. Prefer algorithmic improvements over micro-optimizations
  5. Document the baseline and result in the commit message

Reading guide

| Working on | Read | | --------------------------------------------------- | ----------------------------------------------------- | | Language-specific profiling tools, before/after form | [profiling-tools](profiling-tools.md) | | Quick wins by category, load testing | [optimization-checklist](optimization-checklist.md) |

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.