effort-calibrator

Solid

Choose and tune the effort setting for Claude Fable 5 workloads. Use whenever the user asks which effort level to use ("what effort should this batch job run at?", "is xhigh worth it here?"), complains that Fable 5 is slow or expensive, wants to cut latency or token cost, designs a pipeline/harness that mixes routine and hard tasks, or reviews API code that sets output_config.effort.

AI & Automation 14 stars 1 forks Updated 6 days ago MIT

Install

View on GitHub

Quality Score: 80/100

Stars 20%
39
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Effort Calibrator On Fable 5, effort is the primary dial trading intelligence against latency and cost. Defaults that were right for earlier models are usually wrong here: Fable 5 at lower effort frequently beats earlier models at `xhigh`, so over-provisioning effort wastes money and time without adding quality. ## Starting points by workload | Workload | Start at | |---|---| | Routine transforms, classification, short edits, chat, subagents | `medium` (try `low` if latency matters) | | Most analysis and writing | `high` (the general default) | | Coding and agentic/tool-heavy work | `high` (the API and Claude Code default on Fable 5) — even for workloads that ran at `xhigh` on earlier Opus models; escalate to `xhigh` only for the most capability-sensitive tasks | | Hardest capability-sensitive work: large migrations, multi-day autonomous runs, novel research | `xhigh` | | Frontier problems only, where evals show headroom above `xhigh` and token spend is unconstrained | `max` | The signal for `max` is evals showing headroom above `xhigh` on your actual task: on most workloads it adds significant cost for small gains and can tip into overthinking. ## Adjustment signals Lower effort when: - Tasks complete correctly but take longer than the work warrants - The session is interactive and waiting hurts more than marginal quality helps - Output shows over-deliberation: long context-gathering before trivial actions Raise effort when: - First-shot correctness matters more tha...

Details

Author
kpab
Repository
kpab/claude-fable-5-skills
Created
1 months ago
Last Updated
6 days ago
Language
N/A
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

fable-seat

Operating profile for a Claude Code session whose model is Fable (`claude-fable-5`) — the dials that make a Fable-led session run cheaply. Effort defaults to `high` and steps DOWN for routine work (not `xhigh` by reflex); task framing leads with the outcome instead of prior-model step-by-step scaffolding; the prompt cache stays warm by farming cheap work to a subagent rather than inline-switching the main loop's model; long runs get a task budget plus context compaction; and durable state lives on the memory surface. Apply ONLY when the session model is Fable — it is a genuine NO-OP on Opus and every non-Fable model. This is Fable-mechanics guidance, NOT a superiority claim (it does not assert Fable beats Opus). Use it when you're running Fable and want to set the operating dials, before kicking off a long agentic run on Fable, or when asked "how should I run Fable", "Fable operating profile", "Fable seat", "calibrate for Fable", "am I running Fable cost-efficiently".

0 Updated today
BryceEWatson
AI & Automation Solid

effort-estimate

When the user needs accurate effort estimates for tasks, features, or projects. Use when the user says "how long will this take," "effort estimate," "estimate this," "scope this," "size this," "time estimate," "sprint planning," or when planning work. Unlike generic estimates, this skill calibrates against YOUR actual velocity — past estimates vs actuals — so estimates get more accurate over time.

4 Updated 4 days ago
irfad7
AI & Automation Listed

fable5-optimizer

Load before answering whenever a request mentions Claude Opus 5, Claude Fable 5, GPT-5.6 Sol, Codex, or asks which model or agent should plan, implement, review, research, or verify work. Use for model routing, cross-model workflows, Codex delegation, effort selection, context preparation, and runtime/browser verification. Do not use for ordinary implementation or review with no model-choice question, or for generic prompt rewriting.

1 Updated today
nyldn