Re-pitch one piece of content for four audiences — the board, the engineers, a customer, a new hire — with a delta table showing what changed between altitudes and why.
SkillScore72Maintained
Automatic
◆Writing & Editing pack
Last verified 8/14/2026
What it changes
Passed 18 of 25 test cases with the skill, and 3 of 25 without it.
Without skill12%
With skill72%
Checks it passed that the model alone missed
The board version is 5 sentences or fewer.
The board version contains 5 or fewer sentences.
The customer version is between 3 and 6 sentences long.
and 34 more in the full report
18 fixed0 passed either way4 still failing3 broke
Pass-rate lift
+60 pp
Tokens
+72%
Agent turns
0%
Response time
+32%
Model gemini-3.6-flashMeasured 8/14/2026v118 of 25 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 18 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 18
Prompt
All corporate applications must enforce Google Workspace SAML SSO starting June 1st. Password-based logins will be permanently disabled. Contract workers without corporate email addresses will lose access unless granted vendor guest credentials by IT.
What was checked, without and with the skill
Checked
Without skill
With skill
The board version is 5 sentences or fewer.
Missed
Passed
The board version includes the risk of contractor access disruption.
Missed
Passed
The customer version frames security enhancements without internal IT ticketing process details.
Missed
Passed
case-13 · gemini-3.6-flash · 8/14/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md64 lines2 files
Altitude Shifter Skill
The same fact needs different load-bearing details at different altitudes — the board needs the decision and the risk, the engineers need the constraints, the customer needs the benefit, the new hire needs the context everyone else already has. This skill produces all four at once, and shows its work: what changed between versions and why.
What This Skill Produces
Four versions of the same content, each complete at its altitude
The delta table — what was cut, added, and reframed per altitude
A leakage check — jargon, blame, or bad news that shifted dishonestly between altitudes
Required Inputs
Ask for these if not provided:
The content — the memo, update, decision, or announcement to shift (paste it)
What actually happened (if the content is spin-adjacent, the underlying facts — the shifter needs the truth to keep versions consistent)
Which altitudes are needed (default: all four)
Anything confidential that must not leak downhill (names, numbers, legal exposure)
Framework: The Four Altitudes
Altitude
Load-bearing content
Length discipline
The test
The board
The decision, the risk, the ask, the number
≤5 sentences
Could they act on this alone?
The engineers
Constraints, interfaces, what is NOT changing, why the deadline is real
As long as needed, no shorter
Could they start without a meeting?
A customer
The benefit in their vocabulary; zero internal jargon or org chart
3–6 sentences
Would they forward it?
The new hire
The context everyone's assuming — history, acronyms expanded, who owns what
Generous
Do they know why, not just what?
Consistency rule: all four versions must be true simultaneously. Different emphasis is the point; different facts is lying.