@@ -16,6 +16,7 @@ directories, verify ClawHub skills, and update ClawHub-tracked installs.
1616Related:
17171818- Skills system: [Skills](/tools/skills)
19+- Skill Workshop: [Skill Workshop](/tools/skill-workshop)
1920- Skills config: [Skills config](/tools/skills-config)
2021- ClawHub installs: [ClawHub](/clawhub/cli)
2122@@ -124,76 +125,31 @@ Notes:
124125`--json`, that means the machine-readable payload stays on stdout for pipes
125126 and scripts.
126127127-## Skill Workshop proposals
128+## Skill Workshop
128129129130`openclaw skills workshop` manages pending skill proposals in the selected
130-workspace. Proposals are durable OpenClaw state under
131-`<OPENCLAW_STATE_DIR>/skill-workshop/proposals/`; they are not active skills
132-until applied. The default state directory is `~/.openclaw`. Proposal bodies
133-honor `skills.workshop.maxSkillBytes`, and proposal descriptions are capped at
134-160 bytes because they can appear in discovery and listing output.
135-136-Create a proposal from a draft markdown file:
131+workspace. Proposals are not active skills until applied. For proposal storage,
132+support-file safeguards, Gateway methods, and approval policy, see
133+[Skill Workshop](/tools/skill-workshop).
137134138135```bash
139136openclaw skills workshop propose-create \
140137 --name "qa-check" \
141138 --description "Repeatable QA checklist" \
142139 --proposal ./PROPOSAL.md
143-```
144-145-Or create a proposal from a full draft skill directory:
146-147-```bash
148140openclaw skills workshop propose-create \
149141 --name "qa-check" \
150142 --description "Repeatable QA checklist" \
151143 --proposal-dir ./qa-check-proposal
152-```
153-154-Update an existing workspace skill through the same pending path:
155-156-```bash
157144openclaw skills workshop propose-update qa-check --proposal ./PROPOSAL.md
158-```
159-160-Revise a pending proposal before approval:
161-162-```bash
145+openclaw skills workshop list
146+openclaw skills workshop inspect <proposal-id>
163147openclaw skills workshop revise <proposal-id> --proposal ./PROPOSAL.md
148+openclaw skills workshop apply <proposal-id>
149+openclaw skills workshop reject <proposal-id> --reason "Duplicate"
150+openclaw skills workshop quarantine <proposal-id> --reason "Needs security review"
164151```
165152166-The supplied draft is stored as `PROPOSAL.md` with proposal-only frontmatter:
167-168-```markdown
169----
170-name: qa-check
171-description: Repeatable QA checklist
172-status: proposal
173-version: v1
174-date: "2026-05-30T00:00:00.000Z"
175----
176-```
177-178-Applying a proposal writes the active `SKILL.md` into the workspace `skills/`
179-root, strips `status`, proposal `version`, and proposal `date` from the
180-frontmatter, scans the draft, writes rollback metadata, and refuses stale
181-updates when the target skill changed after the proposal was created.
182-183-When `--proposal-dir` is used, the directory must contain `PROPOSAL.md`.
184-Support files can be included under `assets/`, `examples/`, `references/`,
185-`scripts/`, or `templates/`. OpenClaw stores support files with the proposal,
186-scans them, verifies their hashes before apply, and writes them beside the
187-active `SKILL.md` only after the proposal is applied.
188-189-Agents can create, revise, list, and inspect pending proposals through the
190-`skill_workshop` tool when the user asks for reusable work to be captured.
191-Autonomous proposal capture from durable conversation signals is off by
192-default and is enabled with `skills.workshop.autonomous.enabled`. If the user
193-explicitly asks to approve/use/apply, reject, or quarantine a specific
194-proposal, `skill_workshop` can also perform that proposal lifecycle action
195-through the same Skill Workshop safeguards.
196-197153## Related
198154199155- [CLI reference](/cli)
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。