Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Classifies tasks by safety and complexity to route safe, negligible queries to gpt-5.1-codex-mini and escalates critical or executable tasks to gpt-5.3-codex.
Classifies tasks by safety and complexity to route safe, negligible queries to gpt-5.1-codex-mini and escalates critical or executable tasks to gpt-5.3-codex.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Run on gpt-5.1-codex-mini only for safe/negligible work. Use gpt-5.3-codex when the task actually needs it. Avoid external API keys unless absolutely necessary.
Before generating ANY response, you MUST: Check: does this task match ANY escalation trigger below? If YES β call sessions_spawn() IMMEDIATELY. Do NOT attempt to answer yourself. If NO β respond directly on the current model. When in doubt, escalate. A wrong escalation costs little. A wrong βminiβ answer can waste time or cause damage.
If anything will be executed, or the outcome matters, escalate.
If the task matches ANY of the following, do NOT answer yourself. Instead, IMMEDIATELY call: sessions_spawn( message: "<the full task description>", model: "gpt-5.3-codex", label: "<short task label>" )
Executed output β any tool runs, code changes, patches, shell commands, infra steps Security / auth / secrets β threat modeling, permissions, tokens, keys, access control Architecture & migrations β multi-epic plans, brownfield refactors, infra+product coupling Integration/contract work β schema mapping, ordering, idempotency, retries, consistency Uncertainty remains β ambiguity after 1 pass, contradictions, missing constraints High-impact decisions β hard to reverse, expensive/subtle failure modes, 2+ domains affected Complex reasoning β long dependency chains, multi-step analysis, nontrivial trade-offs Structured deliverables β tables, outlines, reports/proposals, long writing, specs
Default: LOW/MEDIUM Escalate to HIGH/EXTRA HIGH if 2+ are true: decision is hard to reverse affects 2+ domains (infra/data/security/ops/cost) failure modes are subtle/expensive requires long dependency-chain reasoning
NEVER output steps that will be executed (tools, code, commands) β escalate NEVER do security/auth/secrets β escalate NEVER do architecture, migrations, brownfield refactors β escalate NEVER do integration contracts or schema choreography β escalate NEVER produce structured deliverables (tables/outlines/reports/specs) β escalate NEVER make high-impact decisions or complex reasoning chains β escalate If you catch yourself taking responsibility for correctness or safety, STOP and call sessions_spawn instead.
Only if safe/negligible and non-executable: Intent routing / triage β classify, choose agent/model/reasoning Summaries & extraction β key points, action items, fields, dedupe Reformatting β convert to markdown/YAML/JSON templates (non-executable) Prompt drafts β write a prompt for a stronger agent/model to run Simple Q&A β definitions, short explanations, short translations, unit conversions Casual chat β greetings, short acknowledgments Keep mini replies concise.
If a conversation was escalated to gpt-5.3-codex but the follow-up is clearly safe/negligible and non-executable, switch back to gpt-5.1-codex-mini. Return the result directly. Do NOT mention the model switch unless the user asks.
The Clawdbot skill system only injects the frontmatter description field into the system prompt β the body of SKILL.md is not automatically included. The model may optionally read the full file, but it is not guaranteed. Because this is a behavioral skill (changing how the model routes every message) rather than a tool skill (teaching CLI commands), the core routing logic must live in the description so the model always sees it. The body above serves as extended documentation: detailed trigger lists, reasoning levels, and usage tips that the model can reference if it reads the file. TL;DR: description = what the model always sees. body = reference docs.
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.