AI Agent & Automation Workflows

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 ", "can do this", "who/what should do this", "find someone/something to ...", "ask 's agent/twin", or "what has worked on". Activate on: "delegate to", "assign this to", "can X do this", "who should do this", "which team/service can do this", "find someone to", "ask X's agent", "talk to X's twin", "what has X worked on", "делегуй", "постав задачу X", "доручи X", "чи впорається X", "хто це зробить", "яка команда/сервіс це зробить", "підбери виконавця", "запитай агента X", "над чим працював X", "делегируй", "поставь задачу X", "поручи X", "справится ли X", "кто это сделает", "какая команда/сервис это сделает", "подбери исполнителя", "спроси агента X", "над чем работал X". For a plain 1:1/group message use simulator-chat; to only create/assign a task use simulator-tasks; for workspace playbooks (not agents) use simulator-skills.

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 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.

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 ...", "застилізувати смартформу", "стилі CDU", "тема для форми", "кастомний CSS", "оформити таблицю/ сайдбар/модалку", "застилизовать смартформу", "стили CDU", "тема формы", "кастомный CSS", "оформить таблицу/сайдбар/модалку".