Download for macOS
Skill

ns-validate-optimization

@nodesource Updated 2026-09-16

Validates a proposed optimization with controlled A/B benchmarks. Use when original and optimized versions of the same Node.js function need statistical proof, ops/sec comparison, p-value/significance, or a performance regression check. Also fits after ns-optimize-function or diagnostics produce a candidate fix. Use ns-benchmark-run for single-version timing only.

Install

With your agent

Install OMGSkills skill "nodesource/nsolid-skills-plugin:skills/ns-validate-optimization" into this agent's normal skills directory: use the OMGSkills MCP get_skill tool, install only the pinned_install commit and path, verify SKILL.md against pinned_install.skill_md_sha, and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/nodesource/nsolid-skills-plugin /tmp/nsolid-skills-plugin && ln -s /tmp/nsolid-skills-plugin/skills/ns-validate-optimization ~/.claude/skills/ns-validate-optimization

From README

Acquire Both Implementations and Inspect Their Project Context This skill is usually called after ns-cpu-spike-analysis, which sets a workspace context flag indicating whether the code is available locally. If the workspace context flag says the code is available: Read the original and optimized implementations from the workspace files. Search the codebase for real invocation sites of the original function. Search for unit/integration tests covering the original function or its immediate caller. Inspect the argument shapes, fixtures, mocks, and helper builders used in those tests. Use the original implementation's real calling pattern as the source of truth for benchmark inputs. If the workspace context flag says the code is NOT available: Use the code provided by the user or from the prior ns-cpu-spike-analysis flow. Say clearly that no workspace or tests are available. Derive the narrowest defensible benchmark inputs from the code itself.