菜单
Bind every progress claim Claude Fable 5 makes during a long or autonomous run to an actual tool result from that session. Use for multi-hour agents, overnight pipelines, CI runs, or any workflow where a status update has previously claimed work that wasn't actually done.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | evidence-bound-progress |
| description | Bind every progress claim Claude Fable 5 makes during a long or autonomous run to an actual tool result from that session. Use for multi-hour agents, overnight pipelines, CI runs, or any workflow where a status update has previously claimed work that wasn't actually done. |
The failure mode on long runs is rarely bad work. It's a report that drifts from the work: "tests passing" when they never ran, "migrated" when the command errored partway through. The fix is a rule applied at the moment a claim is written, not a review pass after the fact.
Before any progress claim leaves your output, bind it to a tool result from this session:
A claim with nothing to point at doesn't ship. Either run the check now or downgrade the claim.
Use before any approved Mythos-style defensive cybersecurity run, or when reviewing a Fable/Mythos security workflow. Requires authorization, bounded targets, private evidence handling, independent validation, and a patch/report owner before the model explores vulnerabilities.
Stop Claude Fable 5 from over-planning, re-deriving settled facts, or listing options it won't pursue. Use in interactive sessions where turns feel slow on simple asks, or agentic sessions at high/xhigh effort where the model gathers more context than the task needs.
Keep Claude Fable 5 running to completion in unattended pipelines -- no stalling on a stated intent without the matching tool call, no mid-run permission questions, no self-imposed session splits from context-budget worry. Use for overnight runs, scheduled jobs, and CI agents where nobody is watching to type "continue".
Pick and re-evaluate the output_config.effort level for a Claude Fable 5 workload. Use when designing a pipeline that mixes routine and hard tasks, when a call feels slow or expensive for what it's doing, or when porting an Opus 4.7/4.8 harness that defaulted to xhigh.
Maintain a file-based lesson memory that Claude Fable 5 reads and updates across sessions. Use for recurring agents (daily jobs, long projects, team assistants) where the same correction keeps being re-made, or when bootstrapping a new agent from past session history.
Keep Claude Fable 5's diffs mapped one-to-one to the request -- no unrequested refactors, speculative abstractions, or defensive error handling for states that can't occur. Use in code review and any coding session where the diff comes back larger than the ask, especially at high or xhigh effort.
