sd-effort-calibrate

Recommends and evaluates Claude effort levels for tasks, subagents, and scheduled jobs.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/platypeeps/sd-ai-command-pack --skill sd-effort-calibrate-platypeeps
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sd-effort-calibrate
Source: https://github.com/platypeeps/sd-ai-command-pack/tree/main/contrib/sd-effort-calibrate
Command: npx skills add https://github.com/platypeeps/sd-ai-command-pack --skill sd-effort-calibrate-platypeeps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing a Claude effort level (low through max) is often guesswork carried over from older models, leading to slow or costly runs with no measured quality gain. This Skill resolves the level currently in effect, proposes a starting level from task shape, and optionally runs a controlled A/B eval to pick the lowest level that matches the best quality. ## Core Features & Use Cases - Effective Level Resolution: Walks the precedence chain from environment variable and CLI flag through frontmatter and settings.json to report the level in effect and its source. - Starting Level Recommendation: Maps task shape and model (Opus 5.5, Fable 5.1, Sonnet 5) to a starting effort level and names exactly where to set it per scope. - Optional A/B Eval: Runs a frozen prompt at two or three adjacent levels via claude -p, scores against a rubric fixed before the runs, and picks the lowest level tying the best median score. - Use Case: A scheduled claude -p summary job runs slowly after a model upgrade. Use this Skill to resolve its current level, run a six-run eval across low and medium, and record that low ties on quality at half the cost. ## Quick Start Ask the AI to recommend an effort level for your scheduled claude -p job and, if you approve the run count and cost, run a small A/B eval to confirm the cheapest level that holds quality.

Frequently Asked Questions about sd-effort-calibrate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose a Claude effort level for a task?▼

Start from task shape: low for mechanical or read-only work, medium for routine agentic work, high for hard reasoning and multi-file coding, and xhigh or max only with measured gain. Then run a small A/B eval at adjacent levels to confirm quality holds.

How to set effort level for a claude -p scheduled job?▼

Pass --effort <level> directly to the claude -p command, typically through the job's argument hook such as JOB_CLAUDE_ARGS="--effort low". Whether claude -p reads modelSettings from settings.json is untested, so pass the flag explicitly.

What overrides effort frontmatter in a Claude subagent or skill?▼

The CLAUDE_CODE_EFFORT_LEVEL environment variable beats frontmatter, followed by the --effort launch flag or /effort session command. Frontmatter effort applies only within that subagent or skill's scope.

Does effort level carry over between Claude models?▼

No, level names do not compare across models. Opus 5.5 at medium matches or exceeds Opus 5 at high on Anthropic's coding evals, so re-run an effort sweep on your own evals after each model change.

Why is my Claude job slow or expensive after a model change?▼

A carried-over effort setting may be higher than the new model needs. Resolve the effective level and its source, then run a frozen-prompt eval at two or three adjacent levels and pick the lowest one whose median rubric score ties the best.

What are the limits of the A/B effort eval?▼

The eval is capped at nine runs total, uses one frozen prompt and fixture, and requires explicit approval since claude -p spends money. Jobs with side effects need a dry-run fixture, and the rubric must be fixed before any run.