What problem does it solve? When an N|Solid event fires (process-blocked, new-vulnerability-found, agent-exit, uncaught exception), engineers must manually piece together metrics, assets, and traces to understand what happened. This Skill automates that triage by parsing the event payload and pulling the right MCP evidence for the event type. ## Core Features & Use Cases - Event Parsing and Classification: Extracts event, type, severity, app, agent, time, and args fields, then classifies the event as performance, security, lifecycle, or error oriented. - Type-Specific Evidence Gathering: Routes to the correct MCP tools such as metrics-historic, assets, vulnerabilities, application-packages, events-historic, or runtime-code depending on the event category. - Guided Follow-Up and Reporting: Recommends the right deeper workflow (CPU spike, memory spike, vulnerability, or tracing analysis) and optionally writes a markdown report to .nsolid/assets/. - Use Case: You receive a process-blocked event for a production Node.js app. The Skill parses the payload, queries historical CPU, heap, and event loop lag metrics around the event time, checks for nearby profiles, and delivers a root cause hypothesis with next steps. ## Quick Start Analyze this N|Solid process-blocked event payload and tell me what caused it and what to investigate next.
