mcpbeat Sign in

Node Zombie Guardian Agent Skill

Use when diagnosing stale or orphaned Node.js processes launched by VCO, auditing ownership/liveness, or safely simulating cleanup without touching external Node workloads.

758 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
2583
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/foryourhealth111-pixel/Vibe-Skills --skill node-zombie-guardian

The instruction itself

9 sections, as written by the author

Node Zombie Guardian

This skill is for managed-process hygiene inside the VCO ecosystem.

It exists to answer one question safely: which Node processes belong to VCO, which of them are stale, and which of those are eligible for cleanup without risking live external workloads.

Safety Boundary

  • Only processes with ownership = vco-managed can ever become cleanup candidates.
  • external and unknown processes remain audit-only.
  • Cleanup is report-first by default.
  • Fixture -Apply mode remains simulation-only and must never terminate real processes.

When To Use

  • Node processes accumulate after long VCO runs and you need an ownership-aware audit.
  • You want to register or observe VCO-launched Node processes through the wrapper.
  • You need a Markdown or JSON report of managed vs external Node processes.
  • You want to simulate cleanup of stale VCO-managed Node processes without touching real workloads.

Operator Surfaces

This skill is a focused wrapper around the operator scripts that live in the bundled vibe skill:

  • ../vibe/scripts/common/NodeLaunchWrapper.ps1
  • ../vibe/scripts/governance/Invoke-NodeProcessAudit.ps1
  • ../vibe/scripts/governance/Invoke-NodeZombieCleanup.ps1
  • ../vibe/scripts/verify/vibe-node-zombie-gate.ps1

Quick Start

1. Launch a managed Node process through the wrapper

Use the wrapper when VCO starts a Node workload that should be tracked in the ledger.

& "..\vibe\scripts\common\NodeLaunchWrapper.ps1" `
  -RepoRoot "C:\path\to\repo" `
  -Command "node" `
  -ArgumentList @("scripts\worker.js")

2. Audit live Node ownership and liveness

Default mode is read-only and emits a report.

& "..\vibe\scripts\governance\Invoke-NodeProcessAudit.ps1" `
  -RepoRoot "C:\path\to\repo" `
  -WriteArtifacts

Expected outcomes:

  • classify processes such as managed_live, managed_stale, external_audit_only
  • emit JSON and Markdown artifacts for review
  • keep non-managed processes out of the cleanup candidate set

3. Simulate cleanup

Cleanup remains report-only unless explicitly switched, and the safety filters still apply.

& "..\vibe\scripts\governance\Invoke-NodeZombieCleanup.ps1" `
  -RepoRoot "C:\path\to\repo" `
  -WriteArtifacts

Use this to confirm which managed stale processes would be targeted before any real cleanup path is considered.

Verification

Run the dedicated gate before trusting changes in this area:

& "..\vibe\scripts\verify\vibe-node-zombie-gate.ps1" -WriteArtifacts

The gate proves:

  • classification is deterministic on fixtures
  • only managed rows become cleanup candidates
  • external rows never become cleanup candidates
  • report-only mode never terminates processes
  • fixture -Apply mode stays simulated

Other skills for the same job

different authors, same section of the catalogue
Protocolsio Integration
by christophacham
×4

Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.

16k tokens
Tailored Resume Generator
by frostant
×4

Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances

3k tokens
Excalidraw Diagram Generator
by github
vendor ×3

Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.

36k tokens scripts
Expo Dev Client
by openai
vendor ×3

Build and distribute Expo development clients locally or via TestFlight

961 tokens
Executing Plans
by ZhanlinCui
×3

Use when you have a written implementation plan to execute in a separate session with review checkpoints

542 tokens
Anndata
by christophacham
×3

Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.

16k tokens
Benchling Integration
by christophacham
×3

Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.

14k tokens
Biopython
by christophacham
×3

Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.

24k tokens

How to use it

Copy the folder

Take foryourhealth111-pixel/node-zombie-guardian from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.