Template for documenting co-built solutions, integrations, and GTM motions with partners.
NewMaintained
Automatic
◆Sales & GTM pack
Last verified 8/23/2026
What it changes
Passed 20 of 23 test cases with the skill, and 20 of 23 without it.
Without skill87%
With skill87%
Checks it passed that the model alone missed
The response specifies pairing the blueprint with a dedicated co-sell playbook.
1 fixed19 passed either way2 still failing1 broke
Pass-rate lift
0 pp
Tokens
+0%
Agent turns
0%
Response time
-5%
Model gemini-3.6-flashMeasured 8/23/2026v120 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
A test case the skill fixed. Same model, same prompt, with and without the skill.
Prompt
We just finished drafting the technical architecture and marketing value narrative for our joint HR tech integration blueprint. What complementary artifact should field reps receive so they know how to pitch and progress live co-selling opportunities?
What was checked, without and with the skill
Checked
Without skill
With skill
The response specifies pairing the blueprint with a dedicated co-sell playbook.
Missed
Passed
case-05 · 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.md25 linessingle file
Joint Solution Blueprint Skill
When to Use
Launching or refreshing a co-built integration or packaged service.
Equipping field teams with architecture, value props, and proof points.
Coordinating enablement across product, marketing, and partner teams.
Framework
Use Case Definition – target persona, pain point, and success metrics.
Architecture Overview – system diagram, data flows, dependencies, security notes.
Value Narrative – customer outcomes, ROI proof, competitive differentiation.
Go-To-Market Plays – positioning, pricing principles, launch checklist, asset library.
Support & Lifecycle – roles, escalation paths, roadmap commitments.
Templates
One-page solution brief with messaging + CTA.
Architecture diagram checklist.
Launch plan with tasks, owners, and deadlines.
Tips
Keep diagrams simple enough for sales decks, with appendix for technical deep dives.
Include customer stories or beta insights to increase credibility.
Pair with build-co-sell-playbook so reps know how to pitch + progress deals.