What To Ask Skill
Every consequential signature has five questions that would have changed everything — asked the day before instead of discovered the year after. This skill is the library's front door: name the situation ("signing a lease," "buying a used car," "joining a startup," "hiring a contractor"), get the five questions that carry the most leverage for that situation, each with why it matters and what a bad answer sounds like. When a full decoder exists for the document, this skill hands off to it; when none does, five good questions still beat walking in empty.
What This Skill Produces
- The five questions — highest-leverage first, phrased ready to say out loud
- Per question: why it matters (the failure it prevents) and what a bad answer sounds like (the tell to listen for)
- The get-it-in-writing flags — which answers must survive on paper
- The handoff — the full decoder/calculator/simulator for this situation, when the library has one
Required Inputs
Ask for these if not provided:
- The situation — what's being signed/bought/agreed, with whom, and when (tomorrow changes the advice from "research" to "triage")
- The stakes and the worry — money involved, and the thing they're privately nervous about (the fifth question is usually theirs)
- What's already known — documents in hand get routed to their decoder; verbal-only situations get the questions that force things onto paper
Framework: The Question-Selection Rules
- Leverage order, not checklist order: the five are chosen by expected-cost-prevented, not thoroughness — the question that voids the deal outranks ten that adjust it. A list of twenty is a list of zero; five is the format because it forces the ranking.
- Every question gets its bad-answer tell: "What happens if I need to exit early?" matters less than knowing that "oh, we're flexible, we'll work with you" is the bad answer — vagueness where numbers should be is the universal tell, and each question names its specific version.
- The writing question is always in the five for anything with money attached: some form of "can I get that in writing?" — because the answers to questions 1–4 are worth exactly what they're written on.
- Route to depth when it exists: lease → lease-decoder; job offer → benefits-decoder; contractor → home-contractor-quote-decoder; car lot → the-car-dealership to rehearse it first. The five questions are the door; the decoder is the room.
- Unknown situations still get real questions — derived from the universal five axes: exit costs (how do I leave?), change costs (what can they change on me?), the money's full shape (what's the all-in number?), failure modes (what happens when something goes wrong?), and verification (how do I check what you just told me?). Any situation on earth maps onto those.
Output Format
Before you [sign/buy/agree]: [situation]
The Five
1. "[The question, verbatim]"
Why: [the failure it prevents] · Bad answer sounds like: "[the tell]" · [📝 get in writing]
[…2–5, same shape…]
If You Only Ask One
[Which, and why it carries the most weight here]
Go Deeper
[The library's full treatment for this situation, linked — or "no decoder yet; the five axes above are the map"]
Quality Checks
Anti-Patterns
Example Trigger Phrases
- "What should I ask before signing this?"
- "I'm about to buy X what do I check."
- "What questions for the landlord/dealer/contractor/HR?"
- "What am I forgetting?"
1---2name: what-to-ask3description: "Get the five questions that matter before you sign, buy, or agree to anything — the front door to the decoder family, routed by situation. Use when asked what should I ask before signing this, I'm about to buy X what do I check, what questions for the landlord/dealer/contractor/HR, or what am I forgetting. Produces the five highest-leverage questions for the specific situation with why each matters and what a bad answer sounds like, plus the pointer to the full decoder when one exists."4disable-model-invocation: true # skill-optimizer5metadata:6 source: https://skillmd.com/skills/slipcast-dev/what-to-ask7---89# What To Ask Skill1011Every consequential signature has five questions that would have changed everything — asked the day before instead of discovered the year after. This skill is the library's front door: name the situation ("signing a lease," "buying a used car," "joining a startup," "hiring a contractor"), get the five questions that carry the most leverage *for that situation*, each with why it matters and what a bad answer sounds like. When a full decoder exists for the document, this skill hands off to it; when none does, five good questions still beat walking in empty.1213## What This Skill Produces1415- **The five questions** — highest-leverage first, phrased ready to say out loud16- **Per question:** why it matters (the failure it prevents) and **what a bad answer sounds like** (the tell to listen for)17- **The get-it-in-writing flags** — which answers must survive on paper18- **The handoff** — the full decoder/calculator/simulator for this situation, when the library has one1920## Required Inputs2122Ask for these if not provided:23- **The situation** — what's being signed/bought/agreed, with whom, and when (tomorrow changes the advice from "research" to "triage")24- **The stakes and the worry** — money involved, and the thing they're privately nervous about (the fifth question is usually theirs)25- **What's already known** — documents in hand get routed to their decoder; verbal-only situations get the questions that force things onto paper2627## Framework: The Question-Selection Rules28291. **Leverage order, not checklist order:** the five are chosen by expected-cost-prevented, not thoroughness — the question that voids the deal outranks ten that adjust it. A list of twenty is a list of zero; five is the format *because* it forces the ranking.302. **Every question gets its bad-answer tell:** "What happens if I need to exit early?" matters less than knowing that "oh, we're flexible, we'll work with you" *is the bad answer* — vagueness where numbers should be is the universal tell, and each question names its specific version.313. **The writing question is always in the five** for anything with money attached: some form of "can I get that in writing?" — because the answers to questions 1–4 are worth exactly what they're written on.324. **Route to depth when it exists:** lease → [lease-decoder](../lease-decoder/SKILL.md); job offer → [benefits-decoder](../benefits-decoder/SKILL.md); contractor → [home-contractor-quote-decoder](../home-contractor-quote-decoder/SKILL.md); car lot → [the-car-dealership](../the-car-dealership/SKILL.md) to rehearse it first. The five questions are the door; the decoder is the room.335. **Unknown situations still get real questions** — derived from the universal five axes: exit costs (how do I leave?), change costs (what can they change on me?), the money's full shape (what's the all-in number?), failure modes (what happens when something goes wrong?), and verification (how do I check what you just told me?). Any situation on earth maps onto those.3435## Output Format3637# Before you [sign/buy/agree]: [situation]3839## The Five40**1. "[The question, verbatim]"**41*Why:* [the failure it prevents] · *Bad answer sounds like:* "[the tell]" · [📝 get in writing]4243[…2–5, same shape…]4445## If You Only Ask One46[Which, and why it carries the most weight here]4748## Go Deeper49[The library's full treatment for this situation, linked — or "no decoder yet; the five axes above are the map"]5051## Quality Checks5253- [ ] Exactly five questions, leverage-ranked — not a padded checklist54- [ ] Every question has a bad-answer tell, specific to it55- [ ] The in-writing flag appears wherever money does56- [ ] The user's stated private worry became one of the five57- [ ] The handoff link appears when the library covers the situation5859## Anti-Patterns6061- [ ] Do not exceed five — the ranking discipline is the product; a sixth question weakens the first62- [ ] Do not ask questions the user can't act on — every answer must change something63- [ ] Do not phrase questions adversarially — the counterpart is a person; the tells do the detecting64- [ ] Do not skip the handoff to save face — five questions are the trailer, not the movie65- [ ] Do not generate generic questions for a specific situation — "what are the terms?" is what this skill exists to replace6667## Example Trigger Phrases6869- "What should I ask before signing this?"70- "I'm about to buy X what do I check."71- "What questions for the landlord/dealer/contractor/HR?"72- "What am I forgetting?"