corezoid-ai-plugin

Universal Corezoid assistant. Use when the user asks anything about Corezoid processes, wants to work with process JSON files, mentions process nodes, MCP tools, process validation, or any Corezoid-specific task. Also use when the user mentions "Corezoid", "BPM process", "conv.json", "push process", "run task", or asks for general platform knowledge. This skill provides deep knowledge of the platform model and guides you to use the Corezoid MCP tools correctly.

Corezoid process creation specialist. Use when the user wants to create a new Corezoid process from scratch, build a new automation flow, design a new BPM process, or implement a new API connector. Activate when the user says "create a process", "build a new flow", "new process", "design from scratch", "implement a connector", "create an automation", or "add a new process".

Corezoid process editing specialist. Use when the user wants to modify, update, or fix an existing Corezoid process, add or remove nodes, change node behavior, add an API call, fix an error, or update process logic. Activate when the user says "edit a process", "modify", "update", "fix", "add a node", "change behavior", "add a call", "remove a node", or "update the logic".

Manages Corezoid environment variables (env_var) — create, list, modify, delete, and use variables in process JSON. Activate when the user mentions "variable", "env var", "environment variable", "secret", "create variable", "list variables", "delete variable", "modify variable", "env_var", "{{env_var", or asks how to store a URL, token, API key, or any constant that should not be hardcoded in a process. Also activate when a process references {{env_var[@name]}} and the variable does not exist yet.

Corezoid environment setup specialist. Use when the user wants to connect to Corezoid, set up credentials, authenticate, pull a project, configure the environment, or start working with a Corezoid project for the first time. Activate when the user says "init", "setup", "connect to corezoid", "login", "pull workspace", "configure environment", or "get started".

Auto-arrange the nodes of a Corezoid process into a clean, readable layout — a vertical top-to-bottom business flow with error handling railed off to the right and no overlapping nodes. Use it AUTOMATICALLY on every process YOU built or assembled, as the last step before push-process — never hand-place coordinates by eye (eyeballed grids overlap the moment nodes are taller than the step). Also reach for it whenever the user says a process is unreadable, tangled, ugly, a mess, or that nodes sit on top of each other, or asks to "arrange", "lay out", "tidy up", "make readable", "fix positions", "clean the diagram", "remove the overlaps" — or their equivalents in any language the user speaks. Do NOT silently re-arrange a process the user already positioned — see the "When you MAY re-layout" rules in the body. It only changes x/y coordinates and collapses IF/Delay/error nodes — never edges, logic, conv_id, aliases or node types.

Manages Corezoid aliases — create, list, modify, delete, link/unlink, and use aliases in process JSON. Activate when the user mentions "alias", "short_name", "short name", "create alias", "list aliases", "delete alias", "modify alias", "rename alias", "unlink alias", "link alias", "get callback hash", "conv[@", or asks how to reference a process by name instead of numeric ID. Also activate when reviewing a process that uses numeric conv_id values and the user wants to replace them with aliases.

Corezoid Git Call node specialist — run custom code (Python, Go, Java, PHP, JavaScript, Clojure, Lisp, Prolog, or a custom Dockerfile) as a step inside a process. Use when the user needs logic that plain nodes cannot do: parsing files, using external libraries, cryptography, building email/attachments, or any custom runtime. Activate on "git call", "gitcall", "run my code", "parse a file", "use a library", "custom code node", "python/go/php in a process", or "why does push-process hang on git_call". Load this skill only when the task is actually about git_call — it is not needed for ordinary flows.

Corezoid session retrospective specialist. Analyzes the finished (or ending) session of Corezoid work and turns what was learned into concrete, ready-to-apply updates — workspace CLAUDE.md entries, feedback reports to the Corezoid team, permission allowlist entries, personal memory. Routes each finding to the right scope and applies nothing without explicit user confirmation. The goal: every session makes the next one smarter. Use when the user says "retro", "retrospective", "what did we learn", "capture learnings", "update CLAUDE.md from this session", "session retrospective", "ретро", "что мы узнали", "зафиксируй выводы", or signals the session is wrapping up and wants to keep the takeaways. Do not trigger on a mere summary request that transfers nothing into files or configs.

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.

Collects and submits bug reports, improvement requests, and quality signals about the Corezoid plugin to the Corezoid team. Activate in two cases: 1. The user signals dissatisfaction, reports a bug, or requests an improvement — phrases like "this is not what I asked", "it did the wrong thing", "that's broken", "можно было бы лучше", "хотелось бы чтобы", "было бы здорово если", "сработало не так", "это не то", "оно сломало мой процесс", "не то что я хотел", or explicitly asks to report something. 2. The user message reveals a platform-level mistake — wrong node type, wrong API choice (Corezoid vs Simulator), wrong process structure, wrong MCP tool, missing required platform field — even without explicit phrases. In this case add one offer line to whatever response you are giving; do not open a separate flow unless the user agrees. Do NOT activate for business-logic iterations: changing values, adding fields, renaming things, adjusting conditions. These are normal user-driven changes, not platform issues.

Corezoid API connector specialist. Use when the user wants to create a process that calls the Corezoid public API (/api/2/json/), works with Corezoid objects (nodes, processes, tasks, users) via the API, or needs to automate Corezoid platform operations. Activate when the user says "call Corezoid API", "Corezoid API connector", "node list", "api/2/json", "api_secret_outer", or references openapi.corezoid.com operations.

Corezoid state diagram creation specialist. Use when the user wants to create a new Corezoid state diagram, build a state machine, design a status / lifecycle store, or set up a "state" object with conv_type "state". Activate when the user says "create a state diagram", "build a state machine", "new state diagram", "design states", "track status", "user lifecycle", "состояния", "стейт диаграмма", "создать state diagram", or mentions storing state-by-ref between processes.

Corezoid state diagram editing specialist. Use when the user wants to modify, update, or fix an existing Corezoid state diagram — add or remove a state, change a transition, add a side effect on transition, fix the wiring of an api_callback state node, or rework transitions. Activate when the user says "edit a state diagram", "add a state", "remove a state", "change transitions", "fix state diagram", "update state machine", "поправить state diagram", "изменить состояния", or refers to modifying a .conv.json with conv_type "state".

Corezoid access-control specialist. Use when the user wants to share a process, folder, stage or project with another user / group / API key, create or delete a user group, create or rotate an API key, invite an external user, or audit who currently has access to a Corezoid object. Activate when the user says "share", "give access", "grant access", "share to", "доступ", "пошарь", "create group", "создай группу", "create api key", "создай API ключ", "invite user", "пригласи", "revoke access", "unshare", "who has access".

Optimizes a Corezoid process JSON — reduces tact consumption by merging nodes, cleans data flow, fills missing node titles, and adds resilience patterns. Activate when the user says "optimize", "improve", "reduce tacts", "merge nodes", "clean up process", "what can be improved", "show optimizations", or any phrase implying they want to make a process faster, cheaper, or more readable. Two modes: plan-only (analysis + report, no changes) and auto (plan + execute immediately).

Corezoid project review and audit specialist. Use when the user wants to review or audit an entire Corezoid project or folder — multiple processes at once. Activate when the user says "review project", "audit project", "review all processes", "audit all processes", "review folder", "review all processes in", "project-wide review", "cross-process analysis", "find issues across processes", "review the whole project", or "audit folder".

Corezoid process review and audit specialist. Use when the user wants to analyze, review, audit, or improve an existing Corezoid process. Activate when the user says "review a process", "analyze", "check", "audit", "find issues", "explain this process", "what's wrong with", "optimize", or "check for hardcoded values".

Corezoid marketplace pre-publication validator. Standalone skill — no external skill dependencies required. Use this skill whenever the user wants to publish, release, or submit a project or folder to the Corezoid marketplace, or asks to check if a project is ready to publish. Activate on phrases: "publish to marketplace", "готово до публікації", "можна публікувати", "перевір перед публікацією", "validate for marketplace", "pre-publish check", "marketplace validation", "publication readiness", "check before publish", "submit to marketplace", "перевірка публікації". Also activate when the user asks "what's blocking publication" or "why can't I publish this".

Project commit helper for corezoid-ai-plugin. Use instead of the generic commit skill whenever the user says "/commit", "commit", "закоммить", "сделай коммит", or asks to commit changes in this repository.

Creates and manages Corezoid dashboards — adds charts (column, pie, funnel, table), binds metrics to process nodes, configures real-time mode, and sets up drill-down linking between dashboards. Activate whenever a user asks to create a dashboard, add a chart, visualize process metrics, set up reporting for a Corezoid process, configure real-time monitoring, or asks what dashboards or charts exist. Also activate when the user wants to show task counts, completion rates, error rates, or any other process statistics visually in Corezoid.

Documents a Corezoid process — produces a human-readable Markdown file AND enriches the process JSON with descriptions on every node and parameter. Output is designed for team wikis, internal portals, and future product integration. Activate whenever a user asks to document a process, write docs for a connector, add descriptions to a process, create documentation for a logic, describe what a process does, or any similar phrasing. Also activate when the user shares a process JSON and asks to explain it or make it self-documenting. Always produce BOTH outputs (Markdown file + enriched JSON) — never just one.