Create a Template

Use this skill when the person asks to create a Template from this agent, including ordinary chat requests such as “create a new template from this agent.” No sidebar action or special command is required. Stay in this conversation and use this agent's current workspace and durable instructions as source material. Prepare only a private proposal; the existing Control UI owns exact-archive review, package assembly, and explicit human publication. A request to create a Template is not permission to publish it.

Locate this SKILL.md and invoke its scripts/cli.mjs with an absolute path so commands use the running OpenClaw installation. If this turn has a request-specific workContext.detail.draftId from the optional Control UI entry, reuse it. Otherwise run node <absolute-skill-directory>/scripts/cli.mjs templates draft <absolute-current-agent-workspace> --json once and capture the returned draftId and path. Read and edit only that request's .openclaw/template-drafts/<draftId>.json. Never search for a latest draft, use a shared pointer, select a different agent, or start another conversation. Independent requests each get a new draft. If initialization has an uncertain result, inspect its recorded output before creating another draft. Keep internal paths and IDs out of your reply.

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 Template, 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 the role requires it. Use an exact ClawHub ref and version when grounded in a current release, or a path entry for a newly authored portable skill or plugin folder included in this proposal. A bundled skill needs a root SKILL.md and every required supporting file; include those files under that declared folder. Do not copy an installed skill or plugin tree, dependencies, or private source material. Plugin availability alone is not a requirement.