Write a clear, empathetic EOL announcement with rationale, customer impact, and next steps.
SkillScore77Maintained
Automatic
◆Product Management pack
Last verified 8/23/2026
What it changes
Passed 17 of 22 test cases with the skill, and 8 of 22 without it.
Without skill36%
With skill77%
Checks it passed that the model alone missed
The timeline explicitly identifies the data export deadline date.
The impact section explicitly lists migration friction points for developers.
The replacement solution section explicitly names SalesPulse Classic as the legacy tool.
and 11 more in the full report
10 fixed7 passed either way4 still failing1 broke
Pass-rate lift
+41 pp
Tokens
+151%
Agent turns
0%
Response time
+2%
Model gemini-3.6-flashMeasured 8/23/2026v117 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
Draft the core announcement statement for sunsetting InvoiceBot. We want a clear, direct single-sentence announcement without corporate jargon.
What was checked, without and with the skill
Checked
Without skill
With skill
The announcement statement explicitly specifies the sunset date for InvoiceBot in a single sentence.
Missed
Passed
case-10 · gemini-3.6-flash · 8/23/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md339 linessingle file
Purpose
Craft a clear, empathetic End-of-Life (EOL) message that communicates product or feature discontinuation, explains the rationale, addresses customer impact, provides transition support, and positions the replacement solution. Use this to maintain customer trust during difficult transitions and reduce churn by demonstrating care and offering a clear path forward.
This is not a generic sunset announcement—it's a customer-centric communication that acknowledges loss while framing the change as progress.
Key Concepts
The EOL Messaging Framework
An effective EOL message balances honesty about the change with empathy for customer impact. It includes:
Company context: Who you are and your commitment to customers
The announcement: What's being discontinued and what's replacing it
The rationale: Why this decision benefits customers (not just the business)
Current product context: What the product was and who it served
Customer impact: How this affects users (acknowledge the disruption)
Transition solution: What the replacement is and how it improves on the old
Support measures: How you'll help customers migrate
Timeline: Key dates and milestones
Call to action: Next steps and contact info
Why This Works
Empathy-first: Acknowledges customer disruption before justifying the decision
Clarity: No ambiguity about what's changing and when
Support-focused: Shows you're not abandoning customers mid-transition
Future-oriented: Frames change as progress, not loss
Anti-Patterns (What This Is NOT)
Not a terse shutdown notice: "We're discontinuing Product X. Goodbye."
Not business-centric: Don't lead with "This reduces our costs"
Not vague: "Soon" is not a timeline
Not defensive: Don't blame customers ("low usage forced us to shut down")
When to Use This
Discontinuing a product, feature, or service
Migrating customers from legacy to new platform
Sunsetting an acquisition target's product
Deprecating a technology stack or API
When NOT to Use This
For minor feature tweaks (don't over-communicate small changes)