nodesource

Performs an advanced N|Solid memory leak hunt comparing baseline vs peak heap evidence to isolate retained constructors, closures, and retainer paths. Use when the user reports recurring/staircase memory growth, elusive leaks, retained objects, closures holding references, or a standard heap sample/snapshot analysis was inconclusive. Prefer supplied baseline/peak assets; capture new samples only when needed.

Analyzes an existing N|Solid diagnostic asset by asset ID or local asset path using asset-summary. Use when the user asks to inspect, review, summarize, or interpret an already-captured CPU profile, heap profile, heap sample, or heap snapshot, including assets just produced by ns-generate-asset. Do not use to capture new profiles/snapshots.

Diagnoses high CPU or slow execution in a Node.js app using supplied evidence or N|Solid CPU metrics/profiles. Use when the user reports CPU spike, high CPU percent, slow endpoint/function, event loop blocking, flamegraph/profile analysis, hot loop, or asks why an app is slow. Prefer existing asset IDs, summaries, trace data, or local profiles before capturing a new profile.

Captures a new N|Solid diagnostic asset for a connected Node.js app. Use when the user explicitly asks to collect, capture, or generate a CPU profile, flamegraph, heap sample, heap snapshot, or heap tracking asset and wants it saved or handed off for analysis. For existing assets, use ns-analyze-asset instead.

Diagnoses memory growth, heap spikes, RSS increases, OOMs, and suspected leaks in Node.js apps using supplied heap evidence or N|Solid heap sampling/snapshots. Use when the user reports memory leak, heap growing, high RSS, out-of-memory, heap snapshot/profile analysis, or wants memory root-cause triage.

Analyzes N|Solid/OpenTelemetry tracing evidence for request latency, HTTP errors, and service dependencies. Use when the user asks about slow endpoints, API timeouts, distributed traces/spans, N+1 queries, await chains, microservice latency, cascading failures, or trace IDs. Query N|Solid only when no trace data was provided. Do not assume full waterfall details unless supplied.

Audits a local Node.js project dependency tree with NCM vulnerability and quality data. Use when the user asks for an npm audit-style security review, package CVEs, direct/transitive vulnerability report, dependency risk assessment, or remediation plan before upgrading. For vulnerabilities actually loaded in running N|Solid processes, use ns-analyze-vulnerabilities instead.

Benchmarks one Node.js function and reports throughput/statistics. Use when the user asks to benchmark or time a single function, measure ops/sec, compare input sizes, or answer "how fast is this code?" Use ns-validate-optimization instead when original and optimized versions need an A/B proof.

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.