Download for MacApple silicon, macOS 14+
Skill

ns-analyze-event

@nodesource Updated 2026-09-16

Investigates an existing N|Solid event payload and correlates relevant MCP evidence. Use when the user provides or references an event such as process-blocked, new-vulnerability-found, agent-exit, uncaught exception, stack trace, span data. Routes follow-up to CPU, memory, vulnerability, or tracing workflows when needed.

Install

With your agent

Install OMGSkills skill "nodesource/nsolid-skills-plugin:skills/ns-analyze-event" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), 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-analyze-event ~/.claude/skills/ns-analyze-event

From README

Parse the Event Extract these fields first: event, type, severity, app, agent, time, and args. If args is a JSON string, parse it before doing anything else. If args already include a stack trace, span data, trace identifiers, or other direct evidence, analyze that payload before reaching for more MCP tools. Identify whether the event is best treated as performance, security, lifecycle, or error oriented. Branch by Event Type Performance events such as process-blocked, event loop lag, and high CPU: Call metrics-historic with field: ["cpuUserPercent", "heapUsed", "loopEstimatedLag"], q: "app= " or q: "id= ", and start/end around the event time. Call assets to look for nearby profiles or snapshots. If relevant assets exist, prefer asset-summary. Security events such as new-vulnerability-found: Call vulnerabilities for the affected application. Call application-packages to identify the loaded package versions.