/create-claw

name: create-claw
description: Turn this agent into a shareable Claw for a person to review.
user-invocable: true
disable-model-invocation: true

Create a Claw

The Control UI invokes this manual skill in the agent's existing main conversation. It prepares a private draft before sending the message and attaches that request's `draftId` as working context. Use the `draftId` attached to this turn and edit only `.openclaw/claw-drafts/<draftId>.json`; never search for a latest draft or use a shared pointer. The attached context is request-specific, so overlapping Claw creations stay isolated. Keep internal paths and IDs out of your reply. Work in this same conversation; the Control UI opens package review when the draft is ready and owns package assembly and publication.

1. **Capture the reusable agent.** Read the current draft JSON. Use this conversation and the agent's durable instructions to identify its coherent reusable role, input, job, output, and authority. Preserve useful behavior and settings; leave out personal context. If the responsibilities do not form one coherent Claw, ask which responsibility to share before writing. Complete when the four scope fields describe an agent a new person can use. 2. **Inventory only relevant material.** Select portable workspace instructions and files that implement that role. Locate this `SKILL.md` and use its `scripts/cli.mjs` for inventory so the CLI matches the running OpenClaw installation; invoke it with an absolute path when outside the skill directory. Run `node scripts/cli.mjs skills list --agent <this agent's id> --json` and `node scripts/cli.mjs plugins list --enabled --json`. Compare the results with tools actually available in this session and capabilities used in the role. Inspect a candidate with `node scripts/cli.mjs plugins inspect <id> --json` for its source and exact version. Declare a skill or plugin only when you can ground it in a current ClawHub package reference and exact version; plugin availability alone is not a requirement. Put package references in `packages`, MCP requirements in `mcpServers`, and useful schedules in `cronJobs`. Their declarations are dependencies, not files copied into the archive. Complete when every included file and declaration has a reason tied to the reusable role. 3. **Author the proposal.** Follow [the draft format](references/draft-format.md). Rewrite instructions for a new owner. Include input, job, output, and authority in the draft `scope`, and describe the portable behavior in `CLAW.md`. Place only newly authored portable text in `files`, mapping included workspace files by `source` in the manifest. Exclude raw conversations, memories, `USER.md`, credentials, secret values, private URLs, local paths, and personal facts. Never copy the source workspace tree. Complete when the JSON at this turn's draft path is valid and contains no private source material. 4. **Hand off for review.** Briefly tell the person what the Claw does, which optional files/dependencies you included, and any capability you could not port. Do not print internal draft paths or IDs, generate a review link, upload, or publish. The Control UI opens a review of the exact built archive; the person can remove optional items and explicitly publish there. Complete when the review opens.