actions

Define and manage agent actions with defineAction and client hooks.

3|Updated Jun 10, 2026

Search Tags:#architecture #tooling #patterns #actions #agent-native #frontend-hooks #defineAction

Ready to run

npx skills add https://github.com/BuilderIO/builder-agent-native-starter --skill actions-builderio

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: actions
Source: https://github.com/BuilderIO/builder-agent-native-starter/tree/main/.agents/skills/actions
Command: npx skills add https://github.com/BuilderIO/builder-agent-native-starter --skill actions-builderio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defines and manages agent actions as the single source of truth for app operations. The agent calls them as tools and frontend code uses them through client hooks, enabling consistent behavior across UI and automation.

Core Features & Use Cases

Define actions with a standardized surface using defineAction, including runtime schemas and HTTP exposure rules.
Use useActionQuery / useActionMutation to call actions from the UI and callAction for imperative flows.
Promote multi-step workflows and provider-backed operations into reusable skills for cross-app automation.

Quick Start

Create your first action by defining it with defineAction and wiring the UI to useActionQuery / useActionMutation.

Frequently Asked Questions about actions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I define agent actions that both my frontend and AI tools can call consistently?▼

Agent actions are defined using defineAction as a single source of truth for app operations. The agent calls them as tools while frontend code uses them through client hooks, ensuring consistent behavior across UI and automation.

What is the best way to expose agent actions to the frontend via HTTP?▼

Exposing agent actions to the frontend via HTTP is handled by defining actions with defineAction and configuring HTTP exposure rules. The structured data returns directly to clients while frontend hooks consume the operations.

How do I call agent actions from the UI using frontend hooks?▼

You call agent actions from the UI using useActionQuery and useActionMutation hooks for standard flows, or use callAction for imperative client-side executions, wiring the UI directly to the defined operations.

Can I use agent actions for multi-step workflows and provider-backed operations?▼

Yes, actions support promoting multi-step workflows and provider-backed operations into reusable skills. This enables cross-app automation by allowing both agents and frontend clients to execute the same standardized operations.

How does the agent discover available actions in my application?▼

Agent discovery of available actions is guided via AGENTS.md. This file directs the agent to the defined operations, ensuring it can properly identify and call the actions as tools during automation tasks.

Why maintain a single source of truth for app operations across UI and automation?▼

A single source of truth for app operations prevents behavioral drift between manual UI interactions and automated agent tasks. Defining actions once with defineAction ensures both paths execute identical logic and return consistent structured data.