Turn a rough ask into a precise, reusable prompt.
“How do I write a prompt that gets the same good answer twice?”
Builds the prompt on SCRIPT, six lines in the order the model reads best: Supply the material, Cast the role, Request one thing, Ideal answer, Permissions, Talk to me first. One seat, one SCRIPT.
What this skill does
Takes a rough description of what you want an AI to do and returns a precise, structured prompt you can paste into any model. It follows SCRIPT, six lines in the order the model reads best, so the material comes first, the ask is one thing, the model sees an answer that is already right, and it knows what to do when it does not know. One seat, one SCRIPT.
Inputs
Any AI chat tool to paste the result into. No connectors. Bring the task and whatever the model has to read; the skill builds the prompt.
How it works
- 1SCRIPT. Six lines, in this order, and the order is the point.
- S, Supply the material. Paste what it needs to read, first, at the top. Long material before the ask is the one ordering rule with a measured gain behind it. If you have nothing to paste, that is why the answer will be generic.
- C, Cast the role. One line. Who it is, and who it is writing for. Never "an assistant."
- R, Request one thing. The one job, and one line on why it matters. Two jobs is two prompts.
- I, Ideal answer. One example that is already right. Three if tone matters. The shape of the answer, if the example does not show it. An example steers format and tone better than any instruction.
- P, Permissions. What it must do when it does not know: say so, do not guess. Then what it may never do: invent a number, name a price, send anything. Undecided beats invented.
- T, Talk to me first. Before it starts, it lists what it needs from you, then stops. You cannot know your open questions until it has tried and found the gaps.
For an agent that runs without you, two changes and nothing else. The steps in order go between I and P, because an unattended run needs the sequence written down. And T becomes stop and escalate, because there is nobody to talk to at 2am. For more than one seat, write a BRIEF first and give each seat its own SCRIPT (see brief-prompt-skill).
The test it has to pass. Hand the six lines to a colleague with no context and ask them to write a prompt from it. If they ask what a letter means, the gloss is wrong, not the colleague.
Output format
Rough ask: "summarize customer calls." Built prompt, S C R I P T in order:
[S] TRANSCRIPT
<transcript>
[paste the call here]
</transcript>
[C] You are a customer-research analyst writing for a product team that has
not heard the call.
[R] Summarize this one call so the product team can act on it without
listening. They are deciding what to build next quarter, so what the customer
asked for matters more than how the call felt.
[I] Return exactly these four sections. Here is one done right:
- Verdict: Struggled. Three blockers, no workaround found on the call.
- Quotes: "We tried the export twice and it timed out both times" (admin)
- Feature request: scheduled exports, so nobody has to click
- Next step: rep sends the API workaround by Friday
[P] Quote the customer's own words, never paraphrase a quote. If a section has
no evidence in the transcript, write "none stated." Do not infer sentiment the
words do not support. Never invent a feature name that was not said.
[T] Before you write, list anything in the transcript you cannot place in one
of the four sections, then stop and wait for me.
The bracketed letters are there so the prompt is auditable. Drop them if the model you paste into does not need them.
Turn your ICP doc into four blocks your team and your AI both read from.
Where should our ICP live so the AI stops guessing?
Find the gaps in your ICP, then prove it on ten real deals.
Is our ICP file actually good enough for the AI to use?