跳到正文
cccskills
免费在 GitHub 公开

fable-haiku

Run fable-mode execution discipline on Claude Haiku. Routes the task to the @fable-worker-haiku agent, whose definition carries the staged loop with tightened verification (no bare "unverified" allowed) and an escalate-don't-improvise rule. Trigger when the user explicitly asks for thorough/systematic handling run cheaply or fast ("fable on haiku", "deep work mode but cheap", "stage this on haiku"). For bulk mechanical work. Do NOT use for tasks needing synthesis — benchmark note: at n=1 the skill's effect on Haiku swung both directions (+25 / −17); route quality-critical work to fable-sonnet instead.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(1)

  • SKILL.md2.2 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Fable Mode — Haiku (v3, agent-routed)

v3 change: the worker is a real agent definition (agents/fable-worker-haiku.md) invoked by name. Its system prompt carries the loop, the tightened verification rule, and the operational rules; this skill only routes.

If a task has one obvious correct approach and fits in a single pass, skip this loop and do it directly.

How to run it

  1. Confirm fable-worker-haiku appears in the available agent types. If not, fall back to inline: spawn a general-purpose Haiku agent and pass it the rules verbatim from agents/fable-worker-haiku.md.
  2. Spawn @fable-worker-haiku via the Task tool (subagent_type: "fable-worker-haiku"). Brief it with: the task, the exact output path(s), and the pass condition — name the check explicitly; Haiku gets no benefit of the doubt on verification.
  3. Haiku is cheap: for independent sub-parts, fan out one worker per part and merge. Set a ceiling on concurrent workers.
  4. Follow with @fable-verifier (a second Haiku is cheap; fresh eyes can't inherit the worker's blind spots) for anything that will be delivered without human review.
  5. If a worker escalates ("needs synthesis"), re-route that part to fable-worker-sonnet rather than retrying Haiku with a louder prompt.
  6. Mandatory delivery gate: before presenting the result to the user, invoke the double-check skill on the finished deliverable. If step 4's verifier already cold-checked the final document, double-check runs only the seam check — its own rules handle that. Do not skip the gate.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Automatic final verification pass on completed deliverables. Runs at the end of every fable-mode run — those skills invoke it before delivery. Also triggers when the user says "double check this". Uses a panel of fresh checker agents when spawning is authorized (otherwise a cold self-check) to verify the finished output — not to redo the task. Any FAIL gets fixed and re-checked before delivery.

中文简介正在准备中。当前显示原文说明。

mrtooher/fable-mode8782026年10月13日 更新

Always-on operational guardrails, model-independent. Apply on EVERY task and EVERY model whether or not fable-mode's staged loop is running. Three rules: verify-before-flag, warning batching, and find-and-replace safety. Trigger whenever a response would flag a problem, raise a warning, or edit files with search-and-replace.

中文简介正在准备中。当前显示原文说明。

mrtooher/fable-mode8782026年10月13日 更新

Run fable-mode execution discipline on Claude Fable 5.1 — the top of the escalation ladder and the strongest staged run available. Routes the task to the @fable-orchestrator agent with its model overridden to Fable (`model: "fable"`), which stages the work, delegates artifact production to @fable-worker-sonnet / @fable-worker-haiku, and cold-checks deliverables with @fable-verifier. Trigger when the user explicitly asks for thorough/systematic/"deep work" handling on the strongest model ("fable on fable", "stage this on fable", "deep work mode, fable", "run this on 5.1"), or when a fable-opus run reports the task exceeds Opus's ceiling. Benchmarked 2026-09-02: zero correctness delta on Fable 5.1 at ~1.1× tokens, ~2× wall — a provenance runner, not an accuracy runner. Do NOT use for ordinary single-pass tasks — prefer fable-opus, fable-sonnet, or fable-haiku when the task doesn't need peak reasoning. Fable is plan-included; bulk work still routes down-tier.

中文简介正在准备中。当前显示原文说明。

mrtooher/fable-mode8782026年10月13日 更新

Enforces staged execution discipline on large tasks: a written stage plan, parallel delegation where the runtime supports it, a failable verification check at each stage, and a skeptical self-review before delivery. Trigger when the user explicitly asks OR when the task objectively spans multiple files, sources, or sessions. Do NOT trigger on ordinary multi-step requests that a direct attempt handles fine (autonomous triggering only; explicit invocation always runs).

中文简介正在准备中。当前显示原文说明。

mrtooher/fable-mode8782026年10月13日 更新

Run fable-mode execution discipline on Claude Opus — the top of the escalation ladder. Trigger when the user explicitly asks for thorough/systematic/"deep work" handling on Opus ("fable on opus", "stage this on opus", "deep work mode, opus"). When a task exceeds Opus's ceiling, report that to the user rather than escalating further.

中文简介正在准备中。当前显示原文说明。

mrtooher/fable-mode8782026年10月13日 更新

Run fable-mode execution discipline on Claude Sonnet. When invoked by slash command or by name, spawns a Sonnet subagent that follows the staged loop — stage plan, parallel delegation, a failable verification check at each stage, and a skeptical self-review before delivery; a wording-only request runs the loop inline on the current model. Trigger when the user explicitly asks for thorough/systematic/"deep work" handling on Sonnet.

中文简介正在准备中。当前显示原文说明。

mrtooher/fable-mode8782026年10月13日 更新

查看 mrtooher 的全部技能

报告此技能的问题