nsolid-ai-skills

Generate a new N|Solid diagnostic asset for a connected Node.js application. Supports CPU profiles, heap samples, and heap snapshots.

Advanced multi-phase memory leak hunting for elusive Node.js leaks using N|Solid MCP. Use when the user reports a recurring memory leak, staircase heap pattern, retained objects, or when a standard memory analysis was inconclusive. Performs baseline-vs-peak delta analysis across multiple heap samples to isolate the exact leaking constructor or closure.

Analyze an already-existing N|Solid asset from either an asset ID or a local downloaded file path. Prefer MCP asset-summary for token-efficient analysis, but fall back to the local file when MCP is unavailable. Supports CPU profiles, heap profiles, heap samples, and heap snapshots.

Diagnose high CPU usage in Node.js applications using user-provided evidence or live V8 CPU profiles from N|Solid MCP. Use when the user mentions: high CPU, CPU spike, CPU usage, slow endpoint, slow function, flamegraph, profiling, optimize function, slow loop, or "why is my app slow". Prefer existing assets, summaries, or trace data before capturing a new profile.

Investigate an existing N|Solid event with event-type-aware MCP tool usage. Tailors the workflow for performance, security, lifecycle, and error events, and correlates related assets before suggesting deeper follow-up analysis.

Diagnose memory leaks and high heap usage in Node.js applications using real-time heap sampling or user-provided heap evidence from N|Solid MCP. Use when the user mentions: memory leak, memory growth, heap growing, OOM, out of memory, high RSS, or heap analysis. Prefer existing assets, summaries, or local files before capturing new heap data.

Analyze distributed tracing for HTTP latency, microservice topology, and error origins using OpenTelemetry spans from N|Solid MCP. Use when the user mentions: API timeout, microservice latency, slow endpoint, slow database query, N+1 query, event loop lag, cascading failure, distributed trace, OpenTelemetry, span, tracing, request waterfall, slow dashboard, async bottleneck, await chain, service dependency, or "why is the API slow". Prefer user-provided traces or span exports before querying for fresh data.

Analyze live runtime vulnerabilities across all connected Node.js processes using N|Solid MCP tools. Use when the user mentions: CVE, vulnerability, npm audit, security risk, zero-day, supply chain attack, malicious package, dependency risk, outdated package, "is this package safe", or "do we have any vulnerabilities". This skill scans running production memory for actively-exploitable CVEs — data that a static npm audit cannot provide.

Run a security audit across all npm dependencies in a Node.js project. Use when the user mentions: audit, security scan, vulnerabilities, CVE, check dependencies, npm audit, security report, dependency risks, or asks to review all packages. Produces a prioritized remediation plan grounded in NCM data covering both direct and transitive dependencies.

Benchmark a single Node.js function to measure its performance in ops/sec using the ns-benchmark MCP server. Supports both user-provided code and live V8 source extraction from a running N|Solid process. The final benchmark report is markdown-first and can be persisted to `.nsolid/assets/` in generic-agent flows. Use when the user wants to profile or measure a function's throughput without comparing two versions.

Validate a code optimization using scientifically controlled A/B benchmarks via the ns-benchmark MCP server. Use when the user has an original and optimized version of a function and wants to prove the performance improvement with statistical rigor (ops/sec, p-value, improvement percentage). Also invoked automatically after CPU or memory optimization skills propose a fix. The final benchmark report is markdown-first and can be persisted to `.nsolid/assets/` in generic-agent flows.

Generate a Software Bill of Materials (SBOM) for a registered Node.js application using N|Solid MCP. Use when the user mentions: SBOM, software bill of materials, compliance, SOC2, license audit, transitive dependency, or needs a compliance report.

Advise on upgrading the Node.js runtime version for a project. Use when the user mentions: upgrade Node, update Node.js, Node version, LTS, end of life, EOL, nvmrc, engines field, migrate Node, Node 18/20/22/24, or asks which Node.js version to use. Detects the project-pinned version and provides authoritative LTS/EOL data, a target recommendation, and step-by-step upgrade instructions.

Find a replacement for an npm package. Use when the user mentions: replace, drop, remove package, find alternative, swap out, deprecated package, abandon package, migrate away, or asks "what can I use instead of". Provides NCM-grounded comparison of the target and proposed alternatives, with migration steps and API diff guidance.

Advise on upgrading a specific npm package in a Node.js project. Use when the user mentions: upgrade, update package, bump version, npm update, migrate package, breaking change, semver, outdated package, or asks about a specific package version. Provides risk assessment, step-by-step upgrade instructions, and rollback guidance grounded in NCM data.