Includes explicit `Why now` and `Traction` fields in the narrative block.
and 14 more in the full report
10 fixed9 passed either way4 still failing0 broke
Pass-rate lift
+43 pp
Tokens
+9%
Agent turns
0%
Response time
-25%
Model gemini-3.6-flashMeasured 8/14/2026v119 of 23 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
Map out a demo storyline for an upcoming Forrester Wave briefing on Endpoint Security. Forrester evaluates solution architecture, automated threat remediation, and administrator user experience. Create the demo steps.
What was checked, without and with the skill
Checked
Without skill
With skill
Maps each numbered demo step directly to a specific Forrester evaluation criterion.
Missed
Passed
Presents demo steps using criterion-to-action mapping formatting.
Missed
Passed
case-12 · 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.md98 linessingle file
Analyst Relations Brief Skill
Prepare a crisp, credible analyst briefing that lands the company's narrative and positions it well for evaluations. Analysts reward clear differentiation backed by evidence — not marketing gloss.
What This Skill Produces
A briefing objective and the one message to land
A tight company + product narrative and market framing
Differentiation and proof points an analyst can verify
A demo storyline mapped to the analyst's evaluation criteria
Anticipated tough questions with honest answers, plus follow-ups
Required Inputs
Ask for these if not provided:
The analyst / firm and their coverage area, plus any evaluation (Magic Quadrant, Wave, MarketScape) in play
Objective — inclusion in an evaluation, repositioning, launch awareness, feedback
Company & product basics — what it does, who it's for, traction
Differentiation and the proof (customers, metrics, architecture)
Roadmap themes you can share (and what's confidential)
Known analyst views or prior feedback, if any
Never fabricate metrics, customers, or roadmap dates — mark [to confirm] and flag anything under NDA.
Process
Set the objective — what a good outcome looks like and the single message to land.
Frame the market — the category, the shift, and where you play; align to the analyst's taxonomy.
Tell the narrative — problem, approach, why now, why you.
Prove it — evidence that survives scrutiny; concede limits honestly.
Map the demo to the analyst's criteria — show, don't tell.