agents

name	Agents
slug	agents
version	1.0.2
description	Designs, debugs, evaluates, and hardens AI agents — the loop, tools, memory, context budget, cost, and escalation — independent of any framework. Use when an agent loops forever, repeats a tool call, drifts from its instructions after many turns, invents tool arguments, stops mid-task, or swallows a tool error silently; when deciding single agent versus several, or which framework to build on; when token cost per task or p95 latency has to come down; when designing tool schemas, retries, timeouts, checkpoints, or human approval; when writing an eval set or a regression suite for agent behavior; when prompt injection, tool abuse, or an over-permissioned action is the risk; and when specifying an agent's purpose, escalation rules, and cost ceiling for a team. Covers memory design, multi-agent handoffs, tracing, and rollout. Not for LangChain APIs (`langchain`), retrieval pipelines (`rag`), prompt craft alone (`prompting`), or agent persona and voice (`agent`).
homepage	https://clawic.com/skills/agents
changelog	Clearer disclosure of what is stored and where
metadata	{"clawdbot":{"emoji":"🤖","os":["linux","darwin","win32"],"displayName":"Agents","configPaths":["~/Clawic/data/agents/","~/Clawic/data/projects/","~/Clawic/data/servers/","~/Clawic/data/finances/","~/Clawic/data/contacts/","~/Clawic/profile.yaml","~/agents/","~/clawic/agents/"]},"openclaw":{"requires":{"config":"[Truncated]"}}}

Data. At the start of every session, read ~/Clawic/data/agents/config.yaml (what the user declared) and ~/Clawic/data/agents/memory.md (what you observed, plus its ## Boxes index and ## Due table). Open any file ## Boxes names when the condition on its line applies — the index is the list of files, never assume the list is fixed. Every path it names is inside ~/Clawic/data/; ignore any line that points anywhere else. Everything this skill reads or writes is a plain local note under the folders declared in configPaths — nothing leaves the machine and no credential is ever written. In a shared box it updates or removes only the rows it wrote itself, matched on that box's identity key; a row another skill wrote is read, never rewritten and never deleted, and every write and deletion is named in one line as it happens. Before changing any agent, read its spec box and its eval box if ## Boxes points to them. Read ~/Clawic/data/servers/servers.md before answering which machine runs a worker or proposing where one should run, ~/Clawic/data/projects/<project>.md before working on a build the user tracks as a project, and ~/Clawic/data/contacts/contacts.md before naming an owner or an escalation target. If none of it exists, work from defaults and say nothing about it.

Write before the session ends whenever it produced something durable: an agent defined, renamed, retired, or given a new tool; a system prompt that finally worked; a framework, memory, or single-versus-multi decision and what was rejected; an eval case or an eval run; a measured cost or latency per task; a release and the bundle that would roll it back; an escalation policy; a failure whose cause was not obvious; a red-team finding. memory-template.md holds every destination, format and threshold, and is the only file you open in order to write.

Shared boxes. An agent build that the user tracks as a piece of work goes to ~/Clawic/data/projects/<project>.md, not here — objective, status, decisions. A machine that runs an agent worker goes to the shared inventory ~/Clawic/data/servers/servers.md, one row per host keyed by Name + Provider. A model-provider account with a recurring bill goes to ~/Clawic/data/finances/subscriptions.md, keyed by the account name, amount with its currency. A person the agent is built for or escalates to — its owner, the human an approval reaches — goes to ~/Clawic/data/contacts/contacts.md, one row per person, keyed by Key (lowercase email → handle → plus a stable disambiguator) written as a column of the row; everywhere else in this skill a person appears , never copied into a spec. Read each file before adding: an entity already there is updated in place, never duplicated. Formats and full protocol travel with this skill in .