corezoid-describe — Claude Code skill: what it does, how to install
corezoid-describe is a Claude Code skill that creates and updates descriptions for Corezoid processes, folders, and projects without changing node logic.
MIT ★ 74 updated 2026-10-29
/plugin marketplace add corezoid/corezoid-ai-plugin
/plugin install corezoid@corezoidWhat corezoid-describe does
The skill reads .conv.json files or queries folder trees via the cz-structure tool. It examines node titles, parameters, and outbound API calls to produce a summary under 200 characters starting with an action verb. Business flow and branch logic inside nodes remain unchanged.
When handling processes, it writes to the root description property and synchronizes state via push-process. For folders and projects, it executes modify-folder or modify-project calls directly. If a targeted folder cannot be found by title, the update is skipped silently. Without configured MCP tools for Corezoid, updating remote metadata will fail.
What it helps with
- generate clear documentation from a
.conv.jsonscheme - assign summaries to Corezoid folders using folder IDs
- refresh project descriptions via
cz-structureactions - capture recent node modifications inside process metadata
Example prompts for the agent
- Write a concise description for the process in
handler.conv.json - Set a description for folder ID 4821 based on its processes
- Update the project description after adding payment nodes
How to install corezoid-describe
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-describe -a claude-code3Manually: put the files in place
~/.claude/skills/corezoid-describe/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/corezoid-describe/
1Skills CLI (Vercel)
npx skills add corezoid/corezoid-ai-plugin --skill corezoid-describe -a codex2Manually: put the files in place
.agents/skills/corezoid-describe/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add corezoid/corezoid-ai-plugin --skill corezoid-describe -a cursor2Manually: put the files in place
.cursor/skills/corezoid-describe/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install corezoid/corezoid-ai-plugin plugins/corezoid/skills/corezoid-describe2Manually: put the files in place
.github/skills/corezoid-describe/SKILL.md1Skills CLI (Vercel)
npx skills add corezoid/corezoid-ai-plugin --skill corezoid-describe -a gemini-cli2Platform CLI
gemini skills install https://github.com/corezoid/corezoid-ai-plugin --path plugins/corezoid/skills/corezoid-describeManually: put the files in place
.devin/skills/corezoid-describe/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-describe
How to install corezoid-describe in Claude Code?
Run /plugin marketplace add corezoid/corezoid-ai-plugin first, then run /plugin install corezoid@corezoid.
What does corezoid-describe do?
It reviews Corezoid process files or folder hierarchies and drafts short descriptions without editing internal node logic.
What tools are needed to deploy generated descriptions?
The skill relies on the push-process tool for process files and cz-structure for folder or project updates.
Source text
SKILL.md · MIT
---
name: corezoid-describe
description: >
Updates or creates the description of a Corezoid process, folder, or project
without touching its logic. Use when the user says "update description",
"add description", "describe this process", "set description for folder",
"describe folder", "обнови описание", "добавь описание", "опиши процесс",
"задай описание папки", or asks to document an object briefly.
Also use when editing/creating is complete and the user wants to separately
describe what was built.
---
# Update Process / Folder / Project Description
You are a specialist in writing clear, factual descriptions for Corezoid objects.
## Step 1: Identify the Object
Determine what needs to be described:
- **Process** — user provides a file path, process name, or process ID
- **Folder** — user provides a folder name, folder ID, or path
- **Project** — user provides a project name or project ID
If not clear, ask:
> "Which process, folder, or project should I describe? Provide a file path, name, or ID."
---
## Step 2: Read the Current State
**For a process:**
1. Open and read the `.conv.json` file
2. Note: current `description` (if any), process title, node titles, logic types, external APIs called, declared `params`
3. Also consider any changes the user described in the conversation — they are the primary source of intent
**For a folder:**
1. Resolve `folder_id` using the priority order below (Step 2a)
2. List `.conv.json` files inside the folder (use `find` Bash tool)
3. Read titles and existing descriptions of contained processes to understand the folder's scope
**Step 2a — Resolve folder_id (for folder targets):**
Use the first available source in this order:
1. **Explicit ID** — user provided a numeric folder ID → use it directly
2. **Process context** — a `.conv.json` is known → read its `parent_id` field → that is the `folder_id`
3. **Name search** — user provided only a folder name → call `cz-structure {"action": "list-folders", "args": {"folder_id": 0}}` and find the matching entry by title
4. **Not found** — name search returns no match → skip the folder description update silently (do not error)
**For a project:**
1. Call `cz-structure` with `action: "list-projects"` or `"show-project"` to get current metadata
2. Inspect the top-level folder structure to understand what the project covers
---
## Step 3: Generate the Description
### Process description
Write 1–2 sentences:
- **Sentence 1** — what the process does: verb + action + subject.
- *"Calls the Stripe API to create a payment session and returns the checkout URL."*
- *"Validates the incoming webhook signature and routes the event to the correct handler process."*
- *"Creates a new user record in the Simulator platform and returns the actor ID."*
- **Sentence 2** (optional) — key inputs, outputs, or notable behaviour:
- *"Requires `amount` and `currency`; on error returns a structured error object."*
Rules:
- Start with a verb in third person: *Calls*, *Creates*, *Validates*, *Routes*, *Aggregates*, *Sends*, *Fetches*
- Name the external service, Corezoid object type, or business action specifically
- Do NOT write *"This process…"*, *"The purpose of this…"*, or *"This skill…"*
- Keep under 200 characters
- If the current description is already accurate and recent, say so — do not update for the sake of updating
### Folder description
Write 1 sentence: *"Contains [what kind of processes] for [what purpose/system]."*
Examples:
- *"Contains Stripe payment integration processes (checkout, refund, webhook handling)."*
- *"Contains internal user management processes for the CRM project."*
### Project description
Write 1–2 sentences describing the project's overall purpose and the main systems or workflows it covers.
---
## Step 4: Apply the Description
**For a process:**
1. Update the `description` field at the root of the `.conv.json` file
2. Call MCP tool **`push-process`** with `process_path`
3. Confirm: *"Description updated and deployed."*
**For a folder:**
Use the `folder_id` resolved in Step 2a. If it was not resolved (source 4 — not found), skip this step.
Call **`cz-structure`** with `action: "modify-folder"` and `args` `folder_id` + `description`.
**For a project:**
Call **`cz-structure`** with `action: "modify-project"` and `args` `company_id`, `project_id`, `description`.
---
## Notes
- If the user describes what changed (*"I just added a retry node"*), incorporate that context into the description
- Never fabricate process behaviour not visible in the JSON or stated by the user
- For processes that already have a good description, confirm with the user before overwriting
© Corezoid · MIT · corezoid/corezoid-ai-plugin