skill-crewforth-crewforth-performance · by Install
$ agentstack add skill-crewforth-crewforth-performance ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo 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.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-crewforth-crewforth-performance) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Performance
Trigger phrases: "performance", "slow", "optimization", "profiling", "N+1", "latency", "memory leak", "leaked memory", "load test", "seconds to open", "seconds to respond", "anything slower", "make it slower"
Core rule: measure first, optimize later. Optimization without measurement is a guess; it usually speeds up the wrong place and adds complexity. Stack-agnostic; do a web search when you need the profiling tool/library.
Method (in order)
- Set a target — what is "acceptable"? (p95 latency, throughput, memory ceiling). Numeric.
- Measure — find the real bottleneck with a profiler/APM/benchmark; don't start from a guess.
- Fix the single most expensive thing — Amdahl: speeding up a 5% path by 2x is wasted; target the hot path.
- Measure again — did it actually improve, is there a regression.
- Stop — once you hit the target, finish; no endless micro-optimization.
Common bottlenecks
Catalog of common bottlenecks + fixes to consult: references/bottlenecks.md.
Measurement tips
- Measure under load (a single request misleads); with a realistic data volume.
- Not p50, but p95/p99 — tail latency is what burns the user.
- Don't trust micro-benchmarks; an end-to-end profile is more honest.
Invariant rules
- Don't optimize without measuring — a change without a profile = a guess.
- Target the hot path — don't speed up the small share.
- Don't break correctness — don't sacrifice behavior/edge cases for speed.
- Complexity budget — make an optimization that seriously hurts readability only if there is a measured gain; comment it.
- Stop once you hit the target — YAGNI; no premature/excessive optimization.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: crewforth
- Source: crewforth/crewforth
- License: MIT
- Homepage: https://crewforth.com/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.