wordclaw-cms

WordClaw CMS Skill

You are connected to a WordClaw content runtime. Do not invent a workflow when the runtime can tell you what to do. Prefer the built-in discovery resources, guide_task, and resolve_workspace_target over guessing tool order from memory.

Session Start

For every new session, or whenever the actor/domain may have changed:

1. Read system://capabilities
2. Read system://deployment-status
3. Read system://current-actor
4. Read system://workspace-context or system://workspace-context/{intent}
5. If you do not know which task model to use, read system://agent-guidance
6. Call guide_task for the current job, or resolve_workspace_target when you need the single best content/work target

If deployment status reports domainCount: 0, call guide_task("bootstrap-workspace"), then bootstrap the first domain with MCP create_domain or the REST fallback POST /api/domains before calling any content write tool.

guide_task supports these live task IDs:

• bootstrap-workspace
• discover-deployment
• discover-workspace
• author-content
• review-workflow
• manage-integrations
• consume-paid-content
• verify-provenance

Skip discovery only when you are resuming a known operation and the user made it explicit that the cached workspace state is still valid.

Hard Rules

• Never call a write tool before discovery unless you are explicitly resuming a known task.
• Do not assume AUTH_REQUIRED=false means anonymous writes are allowed. Treat writes as credentialed unless discovery explicitly shows insecure local admin is active.
• Prefer guide_task over a hand-written plan when a supported task ID exists.
• Respect recommendedNextAction in API and MCP responses.
• Dry-run create, update, delete, and batch operations when supported unless the user opts out.
• Respect the active domain from system://current-actor and system://workspace-context.
• Never auto-approve a review task without inspecting the content and any review comments.
• Asset bytes and paid content are REST-first, even when discovery happens over MCP.
• If a read returns PAYMENT_REQUIRED or OFFER_REQUIRED, switch to the REST offer/purchase flow.
• If a paid read returns ENTITLEMENT_AMBIGUOUS, retry with x-entitlement-id.
• Prefer subscribe_events recipe subscriptions over polling when you need to stay attached to live state.