shubhamtaywade82/node-agent-skills/node-benchmark-engineering
Claude Code and agent skill by shubhamtaywade82/node-agent-skills
Trust tier 3
- community
Source check pending
Checking that the SKILL.md file is still in the repository.
Use when a change affects throughput, latency, CPU, memory, serialization, database, or hot-path performance.
Install
npx vskill@latest install shubhamtaywade82/node-agent-skills/node-benchmark-engineeringSKILL.md
The same SKILL.md was published earlier as shubhamtaywade82/node-agent-skills/node-benchmark-engineering.
Benchmark Engineering
Purpose
measuring backend performance with statistically useful, reproducible benchmarks.
Activate when
- a change affects throughput, latency, CPU, memory, serialization, database, or hot-path performance.
- The change touches identity, HTTP testing, performance evidence, or failure-path verification.
Repository inspection
- Detect Node.js/TypeScript versions, test framework, HTTP framework, auth stack, and CI commands.
- Inspect existing test helpers, server lifecycle, fixtures, and mocks.
- Identify the security or performance contract being validated.
- Detect exact library versions before applying adapter-specific mechanics.
Decision rules
benchmark workload represents production pressure; warmup and variance are handled; baseline comparisons are explicit; benchmark results are evidence, not goals
- Runtime behavior, not TypeScript declarations, is the contract under test.
- Keep test environments deterministic and disposable.
- Preserve security controls while creating test seams.
- Prefer evidence-backed thresholds over arbitrary numbers.
Implementation procedure
- Define representative workload.
- Control environment.
- Warm up.
- Run enough iterations.
- Report distribution.
- Compare baseline/target.
- Inspect CPU/memory.
- Reject regressions based on agreed threshold.
Failure modes
Avoid:
- single timing sample; synthetic workload unlike production; optimizing benchmark-only code; ignoring variance.
- Hidden global state, non-deterministic timing, or leaked resources.
- Tests that weaken production behavior just to make setup easier.
Verification
- Write a failing test for the intended behavior or defect.
- Exercise positive, negative, timeout, cleanup, and concurrency cases where relevant.
- Run focused and full test commands using repository tooling.
- Inspect resource cleanup and CI reproducibility.
- Record benchmark/failure evidence and remaining limitations.
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/node-benchmark-engineering/SKILL.md
Popularity
- 7-day trend score
- 5
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/shubhamtaywade82/node-agent-skills/node-benchmark-engineering)