ns-analyze-asset

Analyzes captured N|Solid CPU profiles, heap samples, and heap snapshots by asset ID.

6|7|Updated Jun 4, 2026
One-click install
npx skills add https://github.com/nodesource/nsolid-plugin --skill ns-analyze-asset-nodesource
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ns-analyze-asset
Source: https://github.com/nodesource/nsolid-plugin/tree/main/skills/ns-analyze-asset
Command: npx skills add https://github.com/nodesource/nsolid-plugin --skill ns-analyze-asset-nodesource

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Interpreting raw CPU profiles and heap snapshots is slow and error-prone, and loading them directly into an AI context wastes tokens. This Skill turns an existing N|Solid diagnostic asset into a structured, token-efficient analysis that pinpoints CPU bottlenecks and memory leak patterns. ## Core Features & Use Cases - Asset summarization by ID: Resolves an asset ID (or app name plus asset type) and retrieves a token-optimized summary via the asset-summary MCP tool, with a polling loop for asynchronously summarized heap snapshots. - Type-specific analysis: Identifies hot functions and self/total time costs in CPU profiles, top allocating constructors in heap samples, and retained-size objects, dominator chains, and common leak patterns in heap snapshots. - Runtime correlation: Cross-checks findings with historic metrics and events to distinguish a real leak from a one-off spike, and can fetch runtime code for the hottest user-owned frame. - Use Case: After capturing a heap snapshot of a production Node.js service, ask for an analysis and receive a structured report listing the largest retained objects, what holds references to them, and whether historic heap metrics confirm a growing leak. ## Quick Start Ask the assistant to analyze N|Solid asset with a given asset ID and explain the main bottleneck or leak findings.

Frequently Asked Questions about ns-analyze-asset

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze an N|Solid CPU profile or heap snapshot?▼

Provide the asset ID, or an app name with the asset type, and the Skill retrieves a token-optimized summary via the asset-summary tool. It then reports hot functions for CPU profiles or retained objects and leak patterns for heap data.

What asset types can be summarized in N|Solid?▼

CPU profiles, heap sampling assets (type heap-sample), and heap snapshots can be summarized through asset-summary. Heap profile assets from track-heap-objects are not supported by asset-summary and can only be downloaded locally.

Why does heap snapshot analysis say the asset is still processing?▼

Heap snapshot summarization is asynchronous, so the first asset-summary call may return a pending status. The Skill polls assets-in-progress and retries with waits up to 12 times, and never analyzes a snapshot still marked as processing.

Can I analyze a local .cpuprofile or .heapsnapshot file directly?▼

Raw asset files are never read into context because they are large and token-wasteful. The Skill resolves the full asset ID from .nsolid/assets/index.json and uses asset-summary; if the index is missing, only the filename prefix is known and analysis stops.

How does the analysis confirm a memory leak versus a one-off spike?▼

It queries metrics-historic for heapUsed, heapTotal, and rss around the snapshot time and checks events-historic for near-OOM or process-blocked events. Sustained growth across these signals indicates a leak rather than a transient spike.