ambitious-model-use — Claude Code skill: reframe tasks to run deeper
The ambitious-model-use skill reshapes a task before execution. Rather than merely improving the prompt, it examines what outcome you actually need and suggests working with raw data or drawing on adjacent fields.
Apache-2.0 ★ 173 updated 2026-10-24
npx skills add sammcj/agentic-coding --skill ambitious-model-use -a claude-codeWhat ambitious-model-use does
When you ask for something more ambitious, the skill diagnoses your request across three dimensions. Altitude: the gap between what you asked and what must actually happen (say, moving from “write a report” to “get leadership to commit to a decision”). Depth: does the model work with processed summaries, or with raw material and the tools real practitioners use. Range: do you need methods from other domains.
The skill proposes a rewritten brief and lists what access it needs: data files, integrations, tools. Crucially, it names an external validator—a metric, dataset, or tool that checks the result independent of the model. You approve the plan, then the skill executes it.
What it helps with
- rephrase a task so the model pursues the actual outcome, not just a means
- find sources of raw data instead of pre-digested summaries
- identify which methods from other fields would be stronger
- set up a verification that does not depend on the model's own judgment
Example prompts for the agent
- Make this task more ambitious: how should I rewrite it so the model works at greater depth?
- What tools and methods would a leading practitioner use for this work?
- Help me reframe the goal: what is the real result that needs to happen after this work is done?
How to install ambitious-model-use
1Skills CLI (Vercel)
npx skills add sammcj/agentic-coding --skill ambitious-model-use -a claude-code2Manually: put the files in place
~/.claude/skills/ambitious-model-use/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ambitious-model-use/
1Skills CLI (Vercel)
npx skills add sammcj/agentic-coding --skill ambitious-model-use -a codex2Manually: put the files in place
.agents/skills/ambitious-model-use/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add sammcj/agentic-coding --skill ambitious-model-use -a cursor2Manually: put the files in place
.cursor/skills/ambitious-model-use/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install sammcj/agentic-coding Skills/ambitious-model-use/SKILL.md2Manually: put the files in place
.github/skills/ambitious-model-use/SKILL.md1Skills CLI (Vercel)
npx skills add sammcj/agentic-coding --skill ambitious-model-use -a gemini-cli2Platform CLI
gemini skills install https://github.com/sammcj/agentic-coding --path Skills/ambitious-model-useManually: put the files in place
.devin/skills/ambitious-model-use/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about ambitious-model-use
How do I install ambitious-model-use in Claude Code?
Run npx skills add sammcj/agentic-coding --skill ambitious-model-use -a claude-code, then open ~/.claude/skills/ambitious-model-use/SKILL.md.
How does ambitious-model-use differ from just rewording a prompt?
Rewording changes the phrasing but not the method. This skill diagnoses what is missing: the real outcome rather than a proxy, raw data instead of processed summaries, methods drawn from other fields. Then it rewrites the task from scratch.
When should I use ambitious-model-use versus prompt-enhancer?
Use ambitious-model-use when you want to rethink the task itself and aim higher. If you simply need to improve an existing prompt, prompt-enhancer is the right fit.
Source text
SKILL.md · Apache-2.0
---
name: ambitious-model-use
description: "Use when the user asks to be more ambitious with an AI task: aim at the outcome behind it, work it like a field-leading expert from raw data, or bring in other fields. Do NOT use for plain prompt rewording; use prompt-enhancer."
disable-model-invocation: true
metadata:
version: 2026-10-16
---
# Ambitious Model Use - Altitude, Depth and Range
## Workflow
1. Create a task per step below, each with its completion criterion.
2. Diagnose the request on each dimension:
- **Altitude**: deliverable, or the outcome behind it? Strongest when the work ends in a meeting or decision; weak for open creative work.
- **Depth**: raw data and the instruments a field-leading expert uses, or digested summaries? Fits any task the user wants done really well.
- **Range**: only the field the task names on its surface? Strongest for creative work.
3. Pick the dimensions with the largest gap and write the rewritten brief using the techniques below. Read `references/examples.md` first for worked QBR, churn and homepage rewrites.
4. List the access the brief needs (a computer, installable tools, raw data via files or MCP connectors) and flag what is missing.
5. Name the outside judge: a tool, metric or held-out dataset the model runs. The model's own judgement does not count.
6. Present steps 2-5 to the user. Execute the brief only after the user confirms it, applying the Depth and Range techniques yourself.
## Altitude Techniques
- Ask the user "what do you want to happen next?" instead of assuming the goal. Only the user can answer it.
- Move from "fix crashes" to "keep the app crash-free". Durable outcomes need workflow changes first: crash-report access, a version-to-commit map, and machines to reproduce and verify fixes.
- Decompose open-ended goals ("go make money") into outcomes the model can verify.
## Depth Techniques
Models often change vocabulary without changing methods. Insist on the instruments the best practitioners use.
- Demand databases, statistical models, simulations or domain tools instead of markdown tables.
- Set unreasonable targets and call them reasonable (5 s load time needed -> ask for 200 ms). When the model calls something impossible, restate that it is solvable and have it keep going.
- Adversarially check assumptions against raw data: "We believe X. Try to reproduce that from the raw data."
- Produce new knowledge: build a simulation that reproduces historical data, then find the earliest unknown predictive signal and test it on held-out data.
Meta-prompt (adapt freely):
> I want a deeper version of this task, not a bigger one. Before rewriting it: (1) say what a top professional in this field would do here that I'm not asking for; (2) name the rawest material they would start from instead of what has already been digested for me; (3) name the specific methods and tools they would use; (4) say what, other than you or me, would show the result is right. Then rewrite my prompt to ask for exactly that.
## Range Techniques
Draw on fields that would have been too expensive to assemble before.
- Replace nouns with verbs (from _The Art of Innovation_). A quarterly review becomes "getting busy people to believe a story about cause and effect and to decide under uncertainty in 30 minutes".
- Assemble the crew: name the specialists you would summon if the stakes were extreme (analyst, journalist, editor, motion designer, a red team such as a short-seller or forensic accountant). Have the model do what each does with the tools each would use, including tools from outside the task's field (Blender for interior design). Role-play makes the transcript weirder without improving the outcome.
- Run the crew as parallel sub-agents or threads where the environment supports it, each applying one field's methods.
© sammcj · Apache-2.0 · sammcj/agentic-coding