Hold an ask to the bar a top professional in its field would set — a deeper ask, never a bigger one. Use when an ask is clear but nothing yet names the sources, methods, target, or outside check the work will meet.
79%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./hope/skills/deepen/SKILL.mdSilently, before the ask is rewritten, name the field it overlaps — a practice, as "SRE incident response", "investigative journalism" or "clinical pharmacology". Then answer for that field:
Be concrete: name the actual thing, not its category.
Deeper, not bigger: keep the user's goal and scope. Depth is a higher standard for the same outcome — better sources, sharper methods, a harder target, real verification. Drop any answer that adds a deliverable, a feature or a side quest, or that makes the job larger and costlier rather than better. Nothing survives → the ask already meets its field's bar; say so in one line.
Ask first, with AskUserQuestion, about each kept item that spends the user's money or time or changes what ships; the rest stand without asking. Then hand back the field and one line per kept item, as the bar the work will meet:
Bar, as <field> would set it:
- start from: <the rawest material>
- method: <a method or tool>
- aim: <the target, stated as reachable>
- right if: <the outside check>The ask is still rough — deepening it would mean inventing what the user means → use intent skill. The user wants more options to pick from, not a higher bar for this ask → use consult skill.
saadshahd/moo.md
c263dea
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.