Agents, Skills, and Scheduled Tasks
Build the AI team through guided, reviewable changes instead of editing OpenClaw configuration by hand.
The two Base agents
- RapidClaw is the product orchestrator and general operating agent. It coordinates work through the configured agents, skills, connectors, tools, models, and policies.
- Arcy is the Command Center guide, builder, diagnostician, and governed operator assistant. It helps administrators change the operating environment safely.
Agent Roster distinguishes RapidClaw-managed agents from custom agents created for your organization. Product extensions may add managed specialist agents, but they use the same shared runtime and governance path.
Create or edit an agent with Arcy
- Open Arcy and start the guided agent builder, or select an existing agent to edit.
- Describe the outcome, responsibilities, boundaries, and expected audience in ordinary language.
- Choose from models actually deployed in the environment. Arcy can recommend an appropriate available model for the workload.
- Select only the connectors, tools, skills, and data sources the agent needs.
- Review the generated instructions, scope, permission requirements, and approval boundary.
- Save the agent as a draft or approve activation when the configuration is ready.
Capability does not equal permission
Adding a tool or skill does not grant unrestricted authority. Permission Rules, action policies, connector scope, and required approvals continue to govern what the agent may read, write, send, enable, or delete.
Build reusable skills
Skills package repeatable instructions and capabilities that can be used by the appropriate agents. Use Skills Catalog to review existing skills and Arcy's guided skill builder to create a new one. Define the input, expected output, intended agents, data boundary, tools, and safety requirements. A skill should be narrow enough to test and review independently.
- Use explicit business outcomes instead of vague goals.
- Keep read-only research separate from actions that write, post, send, or delete.
- Attach only the tools required for the skill.
- Test with representative but non-sensitive examples before broader use.
- Update the skill rather than copying slightly different versions into many agents.
Create scheduled tasks
A scheduled task tells an agent when to perform defined recurring work. Arcy can draft the prompt, cadence, agent, model, data scope, tools, and delivery target using live configuration selectors.
- Choose the agent and state the recurring business outcome.
- Define the schedule, time zone, and expected delivery destination.
- Select the required connectors and tools and review their permission boundaries.
- Confirm whether the task only prepares information or could request a protected action.
- Save the schedule disabled, test its output, and activate it only after review.
A schedule is not blanket authorization
Scheduled prompts do not bypass approvals. Writes, external communications, enablement, destructive actions, and other protected behavior still require the applicable permission and approval at execution time.
Review changes over time
- Use Agent Instructions and Permission Rules to understand the current operating boundary.
- Use Activity Log and Agent Journal to review what ran and how agents behaved.
- Use Usage & Costs to compare model consumption by agent, including Arcy.
- Pause or disable a schedule when its output, scope, or timing no longer matches the business need.
- Use Emergency Stop when governed execution must be frozen across agents, schedules, and Teams while diagnosis continues through Arcy.