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-engineering

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

  1. Detect Node.js/TypeScript versions, test framework, HTTP framework, auth stack, and CI commands.
  2. Inspect existing test helpers, server lifecycle, fixtures, and mocks.
  3. Identify the security or performance contract being validated.
  4. 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

  1. Define representative workload.
  2. Control environment.
  3. Warm up.
  4. Run enough iterations.
  5. Report distribution.
  6. Compare baseline/target.
  7. Inspect CPU/memory.
  8. 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

  1. Write a failing test for the intended behavior or defect.
  2. Exercise positive, negative, timeout, cleanup, and concurrency cases where relevant.
  3. Run focused and full test commands using repository tooling.
  4. Inspect resource cleanup and CI reproducibility.
  5. 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

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
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/shubhamtaywade82/node-agent-skills/node-benchmark-engineering/badge)](https://verified-skill.com/skills/shubhamtaywade82/node-agent-skills/node-benchmark-engineering)

Something wrong with this skill or its page? Tell us.