corezoid-lifecycle — Claude Code skill: what it does, how to install
The corezoid-lifecycle skill for Claude Code pauses, resumes, or relocates Corezoid processes and folders only on explicit user instruction.
MIT ★ 74 updated 2026-10-29
/plugin marketplace add corezoid/corezoid-ai-plugin
/plugin install corezoid@corezoidWhat corezoid-lifecycle does
The skill covers four operations on live Corezoid objects: pausing a process, resuming it, moving a process to another folder, and moving a folder itself. Every call follows a fixed two-step pattern: the tool first runs with apply=false, returning a dry-run with the current state, the target state, and a confirmation token built from the object ID. Only after the user confirms that specific action does the tool get called again with apply=true and the exact token from the fresh dry-run.
Moving a process or folder across a project or stage boundary triggers extra warnings about aliases, environment variables, and access rights; the agent proceeds only after the user accepts those and adds allow_cross_stage=true. Folder moves reject projects, stages, self-moves, and moving a folder into its own descendant. Pausing a process blocks new task creation with a conveyor_is_not_active error from Corezoid, but leaves already-running or parked tasks alone, and leaves the graph and deployment untouched.
Before the first lifecycle or move call in a session, the skill reads ${CLAUDE_PLUGIN_ROOT}/docs/process/process-lifecycle-and-move.md. An unused-looking process or an in-progress review doesn't count as permission to pause or move anything — the user has to ask for that exact action.
What it helps with
- pause a Corezoid process before maintenance work
- resume a paused process and let traffic flow again
- relocate a process into another folder or project without losing its ID or graph
- move a folder of processes without touching projects or stages
- get an explicit confirmation token before changing live server state
Example prompts for the agent
- Pause process 12345
- Move the folder "Reports" into "Archive"
- Resume process 12345
How to install corezoid-lifecycle
1Plugin marketplace
/plugin marketplace add corezoid/corezoid-ai-plugin/plugin install corezoid@corezoidThis installs the whole corezoid plugin with all its skills
2Skills CLI (Vercel)
npx skills add corezoid/corezoid-ai-plugin --skill corezoid-lifecycle -a claude-code3Manually: put the files in place
~/.claude/skills/corezoid-lifecycle/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/corezoid-lifecycle/
1Skills CLI (Vercel)
npx skills add corezoid/corezoid-ai-plugin --skill corezoid-lifecycle -a codex2Manually: put the files in place
.agents/skills/corezoid-lifecycle/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add corezoid/corezoid-ai-plugin --skill corezoid-lifecycle -a cursor2Manually: put the files in place
.cursor/skills/corezoid-lifecycle/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install corezoid/corezoid-ai-plugin plugins/corezoid/skills/corezoid-lifecycle2Manually: put the files in place
.github/skills/corezoid-lifecycle/SKILL.md1Skills CLI (Vercel)
npx skills add corezoid/corezoid-ai-plugin --skill corezoid-lifecycle -a gemini-cli2Platform CLI
gemini skills install https://github.com/corezoid/corezoid-ai-plugin --path plugins/corezoid/skills/corezoid-lifecycleManually: put the files in place
.devin/skills/corezoid-lifecycle/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about corezoid-lifecycle
How do I install corezoid-lifecycle in Claude Code?
Run /plugin marketplace add corezoid/corezoid-ai-plugin, then /plugin install corezoid@corezoid.
What does corezoid-lifecycle do?
It pauses and resumes Corezoid processes, and moves processes or folders, always through a dry-run followed by a confirmation token before any real change.
Why does the skill run a dry-run before moving anything?
Because these operations touch live server state, the tool first runs with apply=false to show the current and target state, and only applies the change after the user confirms with the exact token from that dry-run.
Source text
SKILL.md · MIT
---
name: corezoid-lifecycle
description: >
Safely pauses, resumes, or moves existing Corezoid processes and folders.
Use only when the user explicitly asks to pause/unpause/resume/activate a
process or to move/relocate/reorganize a specific process or folder. Trigger
on "pause process", "resume process", "move process", "move folder",
"поставь процесс на паузу", "сними с паузы", "возобнови процесс",
"перемести процесс", "перемести папку", "перенеси процесс", or
"перенеси папку". Do not activate merely because a review, edit, cleanup,
or refactor is in progress; those are not authorization to mutate lifecycle
or location.
---
# Corezoid Lifecycle and Move Operations
Use this skill for deliberate operational changes to existing Corezoid
objects. These tools act on live server state and require explicit user intent.
Read `${CLAUDE_PLUGIN_ROOT}/docs/process/process-lifecycle-and-move.md` before
the first lifecycle/move operation in a session.
## Non-negotiable authorization rule
Never pause, resume, or move an object automatically.
The following are not authorization:
- a process appears unused;
- a review or refactor is in progress;
- edits/tests have completed;
- a folder layout looks untidy;
- pausing or moving would be a convenient safety precaution.
The user must directly ask for the specific action. If the exact object or
destination is ambiguous, resolve candidates read-only and ask the user to
choose. Do not infer a target.
## Required two-step workflow
For all four tools:
1. Resolve and repeat back the exact object ID/title. For moves, also resolve
the exact destination ID/path.
2. Call the tool with `apply=false` (or omit `apply`).
3. Present the dry-run, including current state/location, target, operational
effects, and the exact confirmation token.
4. Ask for explicit confirmation. Do not invent confirmation from earlier
general approval. The token is reconstructable and is not itself evidence
that the user approved the operation.
5. Only after confirmation, call `apply=true` with the exact token returned by
the fresh dry-run.
6. Report the tool's verified result. If it says verification failed or state
may already have changed, stop and run a new dry-run; never retry blindly.
## Pause a process
Use:
```text
pause-process(process_id=<id>)
pause-process(process_id=<id>, apply=true,
confirm="process#<id>:<live_status>->paused")
```
Explain before confirmation:
- Corezoid will reject new task creation with `conveyor_is_not_active`.
- The graph and deployment are unchanged.
- Already-running or parked tasks are not modified by this tool and must be
inspected separately.
- Pause is temporary admission control, not evidence that a process is safe
to delete.
Pause can support a user-chosen maintenance/observation window. Never choose
that window on the user's behalf.
## Resume a process
Use:
```text
resume-process(process_id=<id>)
resume-process(process_id=<id>, apply=true,
confirm="process#<id>:<live_status>->active")
```
Before confirmation, verify with the user that maintenance is complete and
that the process may receive traffic. New tasks can arrive immediately from
API callers, schedules, callbacks, and other processes. Never auto-resume just
because this session originally paused the process.
## Move a process
Use:
```text
cz-structure {"action": "move-process", "args": {"process_id": <id>, "destination_folder_id": <folder>}}
cz-structure {"action": "move-process", "args": {"process_id": <id>, "destination_folder_id": <folder>,
"apply": true, "confirm": "<exact context-bound token from the fresh dry-run>"}}
```
The operation reparents the existing process. It preserves the same ID and
graph; it does not copy, import, or deploy.
If the dry-run reports a project/stage/root context change, explain the alias,
environment-variable, access, and deployment risks. Proceed only after the
user accepts those risks, adding `allow_cross_stage=true` to the confirmed
call.
## Move a folder
Use:
```text
cz-structure {"action": "move-folder", "args": {"folder_id": <id>, "destination_folder_id": <folder>}}
cz-structure {"action": "move-folder", "args": {"folder_id": <id>, "destination_folder_id": <folder>,
"apply": true, "confirm": "<exact context-bound token from the fresh dry-run>"}}
```
Only normal folders can be moved. The action rejects projects/stages, self-move,
and moving a folder into a descendant. For cross-stage/root moves, the risks
apply to every descendant and `allow_cross_stage=true` is required after the
user accepts them.
## After a move
The MCP tool does not relocate local mirror files/directories. Re-pull the
destination and verify it before removing any stale local copy. Local cleanup
also requires explicit user intent; never delete the old local path merely
because the server move succeeded.
© Corezoid · MIT · corezoid/corezoid-ai-plugin