Skill Workshop

Skill Workshop is OpenClaw's governed path for creating and updating workspace skills. Agents and operators never write SKILL.md directly through this path — they create a proposal (pending draft with content, target binding, scanner state, hashes, and rollback metadata) that becomes a live skill only when applied.

Skill Workshop writes workspace skills only. It never touches bundled, plugin, ClawHub, extra-root, managed, personal-agent, or system skills.

How it works

• Proposal first: generated content is stored as PROPOSAL.md, not SKILL.md.
• Apply is the only live write: create, update, and revise never change active skills.
• Workspace scoped: creates target the workspace skills/ root; updates are allowed only for writable workspace skills.
• No clobber: create fails if the target skill already exists.
• Hash bound: update proposals bind to the current target hash and go stale if the live skill changes before apply.
• Scanner gated: apply reruns the security scanner before writing.
• Recoverable: apply writes rollback metadata before touching live files.
• Consistent surfaces: chat, CLI, and Gateway all call the same service.

Lifecycle

create/update -> pendingrevise        -> pendingapply         -> appliedreject        -> rejectedquarantine    -> quarantinedtarget change -> stale

Only a pending proposal can be revised, applied, rejected, or quarantined.

Lifecycle curation

The Gateway tracks aggregate skill usage in the shared state database. Once a day, it reviews skills created and applied by Skill Workshop. Skills unused for more than 30 days become stale; after 90 days they become archived and are left out of new agent skill snapshots. Archived skill files remain unchanged on disk. Manually authored skills are never curated; only skills created by Skill Workshop proposals enter lifecycle curation.

Pinned skills bypass lifecycle transitions. A stale skill returns to active after it is used and the next sweep runs. Archived skills return only through an explicit restore:

Lifecycle transitions and restores apply to new sessions; running sessions keep their current skill snapshot.

openclaw skills curator statusopenclaw skills curator pin <skill>openclaw skills curator unpin <skill>openclaw skills curator restore <skill>

All curator commands accept --json. Status also reports deterministic overlap candidates as suggestions only; it never merges skills or calls a model.

Chat

Ask the agent for the skill you want; it calls skill_workshop and returns a proposal id.

Learn from recent work

Use /learn to turn the current conversation or named sources into one standards-guided skill proposal:

/learn/learn docs/runbook.md and https://example.com/guide; focus on recovery

With no request, /learn asks the agent to distill the reusable workflow from the current conversation. With a request, the agent treats paths, URLs, pasted notes, and conversation references as sources while honoring focus, scope, and naming requirements. It gathers the sources with its existing tools, then calls skill_workshop with action: "create".

The resulting proposal stays pending; /learn never applies it. Review and apply it through the normal approval flow or with openclaw skills workshop.

Create:

Make a skill called morning-catchup that runs my Monday inbox routine.

Update an existing workspace skill:

Update trip-planning to also check seat maps before booking.

Iterate on a pending proposal:

Show me the morning-catchup proposal.Revise it to also flag anything marked urgent.Apply the morning-catchup proposal.

Agent-initiated apply, reject, and quarantine show an approval prompt by default. Set skills.workshop.approvalPolicy to "auto" to skip it in trusted environments.

The prompt identifies the proposal id and target skill, and shows the proposal description, support-file count, and body size. Approval requests are bounded to finish before the agent tool watchdog. If no decision arrives before the prompt expires, the lifecycle action does not run: the proposal stays pending and unchanged. Decide later in the Skill Workshop UI or run openclaw skills workshop apply|reject|quarantine <proposal-id>. Agents should not retry an expired lifecycle action in a loop.

CLI

# Createopenclaw skills workshop propose-create \  --name morning-catchup \  --description "Daily inbox catch-up: triage, archive, surface, draft, plan" \  --proposal ./PROPOSAL.md # Update an existing workspace skillopenclaw skills workshop propose-update trip-planning --proposal ./PROPOSAL.md # List and inspectopenclaw skills workshop listopenclaw skills workshop inspect <proposal-id> # Revise before approvalopenclaw skills workshop revise <proposal-id> --proposal ./PROPOSAL.md # Close outopenclaw skills workshop apply <proposal-id>openclaw skills workshop reject <proposal-id> --reason "Duplicate"openclaw skills workshop quarantine <proposal-id> --reason "Needs security review"

Every subcommand takes --agent <id> (target workspace; defaults to cwd-inferred, then the default agent) and --json (structured output). propose-create, propose-update, and revise also take --goal <text> and --evidence <text> to record proposal context alongside --proposal.

Proposal content

While pending, the proposal is stored as PROPOSAL.md with proposal-only frontmatter:

---name: "morning-catchup"description: "Daily inbox catch-up: triage, archive, surface, draft, plan"status: proposalversion: "v1"date: "2026-05-30T00:00:00.000Z"---

On apply, Skill Workshop writes the active SKILL.md and removes the proposal-only fields: status, proposal version, and proposal date.

Support files

Use --proposal-dir when the proposed skill needs files beside PROPOSAL.md:

openclaw skills workshop propose-create \  --name weekly-update \  --description "Friday wrap-up: stats, highlights, next week's top three" \  --proposal-dir ./weekly-update-proposal

The directory must contain PROPOSAL.md. Support files must live under assets/, examples/, references/, scripts/, or templates/. Skill Workshop scans, hashes, and stores them with the proposal, then writes them beside the live SKILL.md only on apply.

Rejected support-file paths: absolute paths, hidden path segments, path traversal, overlapping paths, executable files, non-UTF-8 text, null bytes, and paths outside the standard support folders.

Agent tool

The model uses skill_workshop with one required action: create | update | revise | list | inspect | apply | reject | quarantine. Other parameters apply depending on the action:

Agents must use skill_workshop for generated skill work. They must not create or change proposal files through write, edit, exec, shell commands, or direct filesystem operations.

Suggested skills

OpenClaw detects durable instructions such as “next time,” “remember to,” and reactive corrections when an interactive turn ends, including failed turns. On the next turn, the agent offers to save the most recent detected workflow through skill_workshop; the user decides whether to create a proposal. This built-in suggestion does not create or change a skill by itself. Enable skills.workshop.autonomous.enabled to create pending proposals directly instead.

Approval and autonomy

{  skills: {    workshop: {      autonomous: {        enabled: false,      },      allowSymlinkTargetWrites: false,      approvalPolicy: "pending",      maxPending: 50,      maxSkillBytes: 40000,    },  },}

Autonomous capture recognizes prospective rules (for example, “from now on”) and reactive corrections (for example, “that’s not what I asked”). It groups new instructions by topic into up to three proposals per turn, routes vocabulary matches to existing writable workspace skills, and revises its own pending proposal when another correction targets the same skill.

Proposal descriptions are always capped at 160 bytes, independent of maxSkillBytes.

Gateway methods

requestRevision is Gateway-only (no CLI or agent-tool equivalent): it forwards free-text revision instructions to the owning agent's chat session instead of replacing PROPOSAL.md directly, for UIs that ask the agent to revise rather than submit literal new content.

Storage

&lt;OPENCLAW_STATE_DIR&gt;/skill-workshop/  proposals.json  proposals/<proposal-id>/    proposal.json    PROPOSAL.md    rollback.json    assets/    examples/    references/    scripts/    templates/

Default state directory: ~/.openclaw.

• proposal.json: canonical proposal record.
• proposals.json: fast listing index, rebuildable from proposal folders.
• PROPOSAL.md: pending skill proposal.
• rollback.json: recovery metadata written before apply changes live files.

Limits

Troubleshooting

Tool-policy diagnostic

When autonomous capture is enabled, openclaw doctor runs the core/doctor/skill-workshop-tool-policy check for the default agent. If policy hides skill_workshop, the warning names the first excluding config layer and the exact allow or alsoAllow change to make. Older runbooks may still use openclaw plugins inspect skill-workshop; that command now explains that Skill Workshop is built in and prints the same policy hint when applicable.

Related

• Skills for load order, precedence, and visibility
• Creating skills for hand-written SKILL.md basics
• Skills config for the full skills.workshop schema
• Skills CLI for openclaw skills commands