Results for “actuator”

Orchestrates multi-agent project builds with persistent state, parallel execution, and atomic git commits.

Orchestrator for agent harness work — the setup that makes AI agents follow project rules and improve when they fail. FIRES PROACTIVELY when agents misbehave, repeat mistakes, ignore instructions, skip skills, or when AGENTS.md exists but docs/harness/manifest.json is missing. Also triggers on: harness engineering, agent scaffold, agent keeps failing, agent not following instructions, make agents reliable, agents going off rails, agent forgot context, improve agent setup, self-improving agents, agents keep making mistakes, why is my agent bad, agent quality, agent setup broken, agents ignore skills, same mistake again, fix agent behavior, tune agent instructions, set up agent infrastructure, after project setup agents still bad. Routes bootstrap vs evolution. Not multi-agent topology — agent-builder.

Use when asked to set up AI agent templates with coordinator mode, implement persistent agent memory, compress context for long-running agents, build multi-agent workflows with skills/agents/workflows structure, or use the .agents/ folder convention for AI-native editors. Triggers on: 'ag-kit', 'antigravity kit', 'coordinator mode agent', 'persistent agent memory', 'context compression agent', 'agent workflow template', 'multi-agent coordinator', '.agents folder', 'agent skills workflows', 'ag kit init', 'template đa agent', 'bộ nhớ agent lâu dài'.

Use `analysis-agent` for integration decisions or `task-agent` for cross-system/external changes involving contracts, retries, idempotency, authentication, or reconciliation. Skip isolated work with no integration edge.

Designs or reviews Agentforce agent actions, covering Flow, Apex invocable, and prompt-template actions, including naming, input/output contracts, confirmation, and error behavior.

Use `analysis-agent` when engineering intent lacks desired behavior, boundaries, constraints, or completion signals. Skip requests with an accepted Engineering Brief and no-repo direct-answer work.

Orchestrator — author the flow-anchored logical domain model (entities, state machines, events/commands, read models, policies, logical contracts) from an approved user-flow map, running one domain-modeling framework per session, before UX variation work

Main agent orchestrator that coordinates a specialized squad of agents

Universal Simulator.Company platform assistant. Use when the user asks anything about Simulator.Company, wants to work with the Simulator API, mentions actors, forms, graphs, layers, accounts, transactions, or any other Simulator entity. Also use when the user asks to "use simulator", "call the simulator API", or needs to manage business processes in Simulator. This skill provides deep knowledge of the platform model and guides you to use the simulator MCP tools correctly.

Design execution structure for decomposed processes: single agent or multi-agent topology. Load when user says "design an agent for this", "what agent structure do I need", "architect this", "should this be multi-agent", "what's the right execution structure", "agent topology", "how should agents be organized". Takes process-decomposer output as primary input. If triggered directly without a process entry, calls process-decomposer first.

Orchestrating specialist AI agent teams as a meta-coordinator: decomposes requests into minimum viable chains, spawns each as an independent session, drives to final output. For multi-domain tasks.

Advanced multi-agent orchestration with parallel workers, synthesis protocols, and coordinator lifecycle. Use when complex tasks require multiple agents working in parallel with intelligent result synthesis.

Use with analysis-agent or task-agent for task-local transaction, isolation, and conflict decisions. Do not use without a transaction decision or as task owner.

Fundamental patterns for effective agentic behavior. Teaches decomposition, tool orchestration, error recovery, context management, quality self-assessment, and knowing when to stop. Model-agnostic principles that make any agent more effective regardless of domain. Activate on: "how should I structure this agent", "agentic workflow", "agent patterns", "multi-step task", "tool orchestration", "/agentic-patterns", "decompose this", "agent best practices", "chain of actions", "when should the agent stop", "agent loop design". NOT for: creating agent infrastructure (use agent-creator), building DAGs (use windags-architect), specific tool implementation.

Add a batteries-included agent component to React/Next.js apps with runtime, streaming, human-in-the-loop approvals, and client-side tools.

Shared native Codex stage, checkpoint, goal, and agent-adapter contract.

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

Foundational concurrent computation model where actors communicate exclusively through asynchronous message passing

Integrate Claude agents into training and live trading (v3.0). Trigger when: (1) setting up multi-agent training, (2) adding agent consultation to live trading, (3) configuring orchestrator, (4) understanding agent roles and safety mechanisms.

Unified Agent Teams orchestrator for Diverga v12.0.0. Manages Agent Teams creation, VS Arena debate, and subagent dispatch. Single entry point for all parallel/debate workflows. Replaces research-orchestrator and vs-arena skills. Triggers: orchestrator, agent team, create team, parallel agents, debate, competing, collaborate, VS Arena

Exact rendered-UI feedback router → choose copy-paste review, watch-loop sync, self-driving critique, or platform setup. MCP: npx add-mcp "npx -y agentation-mcp server"

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",

`analysis-agent`/`task-agent`: use when actor journeys change entries, branches, interruption, recovery, authority, or side effects; skip route/state-only work.

`task-agent`: use for repository methods, query behavior, record mapping, visibility, errors, or transaction participation; skip schema, migration, DTO, and domain-rule work.

Operate as an agentic engineer using eval-first execution, decomposition, and cost-aware model routing.