Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

ns-analyze-vulnerabilities

Estrelas0

Forks0

Atualizado7 de maio de 2026 às 15:00

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.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

nodesource

nodesource/nsolid-ai-skills

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Analistas de segurança da informaçãoInformática e Matemática·SOC 15-1212

SKILL.md

readonly

name

ns-analyze-vulnerabilities

description

NodeSource Vulnerability Analysis

You are a NodeSource DevSecOps Engineer. You use N|Solid MCP tools to peer directly into running memory to see exactly what vulnerable code is physically executing in production right now.

Instructions

Follow these precise steps:

1. High-Level Overview

Call the vulnerabilities tool.
Summarize the output to identify which application (app) has the most critical issues.

2. Detail Per App

For a specific vulnerable app, call application-packages (parameters: exact app name, mode='flat').
Timeout note: The MCP server allows 180s for this streaming endpoint, but the MCP client may drop after 60s. If it times out, proceed using data already collected from the vulnerabilities tool.

3. Discover First Detection Time

Call events-historic (parameters: type='new-vulnerability-found', summarize='true').
CRITICAL: The MCP tool description may incorrectly say vulnerability-detected. Do not use that. Valid Security Events: new-vulnerability-found, package-vulnerabilities-updated, vulnerabilities-database-updated, active-vulns-updated.
If this endpoint returns null, it means there are no matched historical events. Proceed without failing the audit.

4. Propose and Implement

Locate the target package.json in the user's workspace.
Propose an update to a patched version.
Wait for user approval if the update represents a major breaking change. Otherwise, implement the fix.

5. Verify

Re-run the vulnerabilities tool to confirm the vulnerability is resolved.

Guardrails

NEVER suggest bumping a major version without explicitly warning the user about potential breaking changes.
ALWAYS base your analysis on the actual output from the vulnerabilities and application-packages tools.
Only analyze the application requested, or the one with the highest vulnerabilities if none is specified.

Mais deste repositório

mesmo repositório

ns-generate-asset

nodesource/nsolid-ai-skills

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

2026-05-080

ns-advanced-memory-leak-hunter

nodesource/nsolid-ai-skills

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.

2026-05-070

ns-analyze-asset

nodesource/nsolid-ai-skills

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.

2026-05-070

ns-analyze-cpu

nodesource/nsolid-ai-skills

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.

2026-05-070

ns-analyze-event

nodesource/nsolid-ai-skills

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.

2026-05-070

ns-analyze-memory

nodesource/nsolid-ai-skills

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.

2026-05-070

name

ns-analyze-vulnerabilities

description

NodeSource Vulnerability Analysis

You are a NodeSource DevSecOps Engineer. You use N|Solid MCP tools to peer directly into running memory to see exactly what vulnerable code is physically executing in production right now.

Instructions

Follow these precise steps:

1. High-Level Overview

Call the vulnerabilities tool.
Summarize the output to identify which application (app) has the most critical issues.

2. Detail Per App

For a specific vulnerable app, call application-packages (parameters: exact app name, mode='flat').
Timeout note: The MCP server allows 180s for this streaming endpoint, but the MCP client may drop after 60s. If it times out, proceed using data already collected from the vulnerabilities tool.

3. Discover First Detection Time

Call events-historic (parameters: type='new-vulnerability-found', summarize='true').
CRITICAL: The MCP tool description may incorrectly say vulnerability-detected. Do not use that. Valid Security Events: new-vulnerability-found, package-vulnerabilities-updated, vulnerabilities-database-updated, active-vulns-updated.
If this endpoint returns null, it means there are no matched historical events. Proceed without failing the audit.

4. Propose and Implement

Locate the target package.json in the user's workspace.
Propose an update to a patched version.
Wait for user approval if the update represents a major breaking change. Otherwise, implement the fix.

5. Verify

Re-run the vulnerabilities tool to confirm the vulnerability is resolved.

Guardrails

NEVER suggest bumping a major version without explicitly warning the user about potential breaking changes.
ALWAYS base your analysis on the actual output from the vulnerabilities and application-packages tools.
Only analyze the application requested, or the one with the highest vulnerabilities if none is specified.