corezoid

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.

Simulator.Company actor (record) specialist. Use when the user wants to create, update, read, search, or filter the *instances* of a form template (a.k.a. Account Template records) — i.e. data-bearing actors — and needs the `data` value protocol right. Activate when the user says "create an actor", "add a record", "create a record from this template", "fill in a form", "update actor data", "find actors where field = …", "filter actors by balance", "создай актор", "заполни шаблон", or "добавь запись". ALSO use this skill when the user asks what **processes / functions / Corezoid processes** an actor has or can call, or about an actor's **shared API keys / available functions** — call `getCorezoidProcesses`: "what processes/functions can this actor call", "actor's connected processes", "actor's API keys", "available functions of the actor", "які процеси/функції доступні актору", "процеси актора", "функції актора", "ключі доступу актора", "какие процессы/функции у актора", "процессы актора", "доступные функции а

Simulator.Company graph structure specialist. Use when the user wants to build, edit, analyze, inspect, or ask questions about business process graphs, flowcharts, algorithms, actors (nodes), links (edges), or layers (visual views) in Simulator.Company. Trigger on any of these intents: — Creating: "create graph", "build flowchart", "new diagram", "add actor", "add block to graph", "create algorithm", "draw flowchart", "digital twin", "create process on graph", "build process diagram", "FlowchartBlock", "startStop", "predefinedProcess". — Editing: "edit graph", "update actor", "rename node", "change color", "move actor", "add step to flowchart", "modify diagram", "restructure process", "add edge", "remove link", "reorder steps", "update layer". — Syncing: "push graph", "pull graph", "sync graph", "push changes", "apply edits to layer". — Querying / analysis: "what actors are on this layer", "show me the graph", "who is connected to", "find actor", "list nodes", "describe the process", "analyze

Simulator.Company Smart Form (CDU) STYLING specialist — authoring complex Less/CSS for Smart Forms: theme tokens, page/form/section layout, component re-skinning, reusable style patterns, responsive and design-system approaches. Use when the user wants to STYLE or RESTYLE an existing Smart Form / CDU app — change its look, build a theme, style a table / sidebar / modal / form, add a design system, fix spacing/colors/fonts, or apply a complex visual design. This skill owns the `style` / `styles/` layer; it reuses the Smart Form tools (pullSmartForm / pushSmartForm / deploySmartForm) but does NOT create form templates — for the data-schema form template use `simulator-forms`, and for page layout / viewModel / backend logic use `simulator-smart-forms` / `simulator-smart-forms-logic`. Activate on: "style a smart form", "CDU styles", "theme the form", "restyle", "custom CSS/Less for the app", "style the table/sidebar/modal/button", "design system for the smart form", "make it look like …", "застилізувати смартформ

Simulator.Company form designer specialist. Use when the user wants to create or modify form templates (a.k.a. Account Templates / «Шаблон рахунків»), define custom field structures, set up account definitions, explore system forms, work with Smart Forms (CDU / Scripts), manage form status, or understand how forms define actor structure. Activate when the user says "create a form", "design a template", "add fields to form", "Account Template", "Шаблон рахунків", "define actor schema", or "what system forms are available".

Simulator.Company digital-twin & actor-agent specialist — talk to an agent AS an agent and delegate work to it. An agent is ANY actor whose `description` holds an "# Agent" competency profile (what it does, what it knows, whether it fits a task). The common case is a person: every workspace user has a 1:1 twin actor (`systemObjType="user"`) carrying that profile. But any actor can be an agent — a service/bot twin, a team or department, an organization, a process. This skill discovers the agent (`findAgent`), loads its profile (`getAgent`), adopts it as the persona, then either does the task, finds a better-suited agent, or hands the decision to the user (for a person: a task or a p2p message; for a non-person: propose another executor or run/trigger it as an actor). It is the actor-analog of `simulator-skills` (the `Skills`-form registry), but the registry is the workspace's agent actors. Use when the user wants to "delegate", "assign this to <someone/something>", "can <X> do this", "who/what should do this",

Simulator.Company chat & messaging specialist — sending messages to a user, and creating or reusing p2p (1:1) and group chats. In Simulator a chat is an actor of the Events system form (data.chatType = "p2p" | "group"), its participants are the actor's access-rule members, and its messages are `comment` reactions. Use when the user wants to "message", "write to", "DM", "send a message to" someone, "open a chat with", "start a conversation", or "reply in the chat". Activate on "write a message to user N", "send N a message", "open a chat with", "message someone", "напиши повідомлення користувачу", "надішли повідомлення", "відкрий чат з", "почни розмову з", "напиши юзеру", "напиши сообщение пользователю", "отправь сообщение", "открой чат с", "напиши в чат". For comments/approvals on an arbitrary actor (not a chat) use `simulator-reactions`; for files use `simulator-attachments`; for sharing/access in general use `simulator-access`.

Simulator.Company skill registry specialist — the data-driven analogue of these built-in skills. Use when the user wants to RUN a saved playbook ("run skill", "use the … skill", "/skill <slug>", "is there a skill for …", "what skills do I have"), or to AUTHOR one ("create a skill", "save this as a skill / playbook", "teach simulator to …", "make a reusable procedure"). A skill is an actor of the `Skills` system form whose `description` holds a step-by-step procedure (which MCP tools to call, with concrete entity ids) for a workspace-specific task such as "create a smart contract" or "onboard a client". Activate on: "run skill", "use playbook", "is there a skill for", "what skills do I have", "save as skill", "create a skill", "teach simulator", "запусти скіл", "використай скіл", "є скіл для", "які скіли є", "збережи як скіл", "створи скіл", "навчи simulator", "запусти навык", "используй навык", "сохрани как навык", "создай навык".

Simulator.Company task & assignment specialist — creating a task and assigning who does it, who approves it, and whose signature it needs. In Simulator a task is an actor of the Events system form (no chatType), and the roles are access privileges, not data fields: the executor gets `execute`, approvers get `sign`, and a legal document's signers get `ds`. Completion and sign-off are then posted as `done` / `sign` / `reject` reactions. Use when the user wants to "create a task", "assign a task to", "set an executor/assignee", "add approvers", "require a signature", "who signs this", "make a to-do". Also covers **order / directive documents** that tell a specific person to do something — an "order/наказ addressed to X" is a task whose addressee is the executor. Activate on "create a task", "assign to", "task for", "needs approval", "who approves", "requires signature", "sign-off", "order", "decree", "directive", "create an order for", "створи задачу", "постав задачу", "признач виконавця", "додай погоджувача", "