Use when diagnosing stale or orphaned Node.js processes launched by VCO, auditing ownership/liveness, or safely simulating cleanup without touching external Node workloads.
npx skills add https://github.com/foryourhealth111-pixel/Vibe-Skills --skill 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.
ownership = vco-managed can ever become cleanup candidates.external and unknown processes remain audit-only.-Apply mode remains simulation-only and must never terminate real processes.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.ps1Use 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")
Default mode is read-only and emits a report.
& "..\vibe\scripts\governance\Invoke-NodeProcessAudit.ps1" `
-RepoRoot "C:\path\to\repo" `
-WriteArtifacts
Expected outcomes:
managed_live, managed_stale, external_audit_onlyCleanup 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.
Run the dedicated gate before trusting changes in this area:
& "..\vibe\scripts\verify\vibe-node-zombie-gate.ps1" -WriteArtifacts
The gate proves:
-Apply mode stays simulatedIntegration 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.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
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.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
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.
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.
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.
Take foryourhealth111-pixel/node-zombie-guardian from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.