node-zombie-guardian
Use when diagnosing stale or orphaned Node.js processes launched by VCO, auditing ownership/liveness, or safely simulating cleanup without touching external Node workloads.
Profile →npx skills add foryourhealth111-pixel/Vibe-Skills --skill node-zombie-guardian --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 `u
What does the node-zombie-guardian skill do?
Use when diagnosing stale or orphaned Node.js processes launched by VCO, auditing ownership/liveness, or safely simulating cleanup without touching external Node workloads.
How do I install it?
Run `npx skills add foryourhealth111-pixel/Vibe-Skills --skill node-zombie-guardian --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From foryourhealth111-pixel/Vibe-Skills, a repository with 2,593 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.