Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when generating a sales-call prospect briefing: follow the fixed field-label set, emoji priority vocabulary, and cheat-sheet schema.
.claude/skills/sales-briefing-format/SKILL.md| Model | Eval pass | Runs |
|---|---|---|
| gemini-3.6-flash | 90% | 10 |
| Model | Lift | Δ tokens | Δ turns | Cases | Verified |
|---|---|---|---|---|---|
| gemini-3.5-flashbest | +100% | — | 0% | 24 | 86d ago |
| gemini-3.6-flash | +82% | +150% | 0% | 22 | 52d ago |
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-08 | ✗→✓ | ▲ Improved | — | — |
| case-02 | ✗→✓ | ▲ Improved | — | — |
| case-04 | ✗→✓ | ▲ Improved | — | — |
| case-14 | ✗→✓ | ▲ Improved | — | — |
| case-01 | ✗→✓ | ▲ Improved | — | — |
Enforces the fixed structure of a sales-call prep briefing: an emoji-coded header, a fixed six-bullet field set in a fixed order with verbatim bold labels, the five extra follow-up fields, and the quick-reference cheat-sheet column schema. Apply whenever the task is to produce or format a prospect briefing or an at-a-glance call sheet.
The first line of each prospect block is, EXACTLY:
**<priority emoji> Company Name** (Call Time) <status icon>The company name and the leading priority emoji are inside the same **bold** span. The call time is in parentheses. Immediately on the NEXT line, the priority reason in *italics* — never inline, never a bullet.
Every briefing body is EXACTLY these six bullets, in THIS order, each opening with the bold label spelled character-for-character as shown:
- **What they do:** one-line company description- **Recent news:** key development (date)- **Key person:** Name (Title)—relevant note- **Pain point signal:** specific signal with its source- **Your angle:** recommended positioning- **Opening line:** suggested starter, wrapped in double quotesDo NOT rename a label, pluralize it, or swap a synonym. The label is the K — it is Pain point signal:, not Challenges:, Pain points:, or Signals:. It is Your angle:, not Positioning: or Approach:. It is Opening line:, not Hook:, Icebreaker:, or Talking point:.
The header emoji is drawn ONLY from this set, matched to the situation:
| Emoji | Meaning | |-------|---------| | ⭐ | high priority — strong signals (hot inbound, exec replied, demo/pricing request) | | 🔄 | follow-up from a previous conversation | | 🆕 | new prospect — full research done | | ⚠️ | needs attention — action overdue / ball was dropped |
Never substitute another emoji (🔥, ✅, 📞, ❗) or a text tag like [HIGH].
When the prospect is a follow-up, append these FIVE bullets AFTER the six core bullets, in this order, with verbatim labels:
- **Last conversation:** Date—spoke with Name (Role)- **What happened:** brief summary- **Objection raised:** key concern- **What resonated:** what worked- **Status:** current stateWhen asked for a cheat sheet / at-a-glance / one-line-per-prospect sheet, output a markdown table whose columns are EXACTLY, in this order:
| Time | Company | Key Person | One-Liner | Priority |The Priority cell uses the R3 emoji. Header text is verbatim: One-Liner (capital L, hyphenated), not One liner / Summary / Note.
ideally asks a question, and is in double quotes. Never generic ("How are you?") and never an immediate pitch.
scaling ops team"), never vague ("They might like our product").
BEFORE (base default — prose, renamed fields, no emoji header):
> Brightside Health — 10am > Brightside is a regional insurer. They recently announced a Blue Cross > partnership. You'll be speaking with James, the COO. A good talking point is > their growth. Suggested opener: ask about the partnership.
AFTER (conforming):
> 🆕 Brightside Health (10am) 🆕 > Newly researched regional insurer — fresh Blue Cross momentum. > > - What they do: Regional health insurer covering the upper Midwest. > - Recent news: Announced Blue Cross partnership (last week). > - Key person: James (COO)—owns operational tooling decisions. > - Pain point signal: Scaling claims ops post-partnership (press release). > - Your angle: Position agent-monitoring as the control plane for their growing automation. > - Opening line: "Congrats on the Blue Cross tie-up — how's the ops team absorbing the volume?"
BEFORE (hot inbound, base picks 🔥 or a text tag):
> 🔥 Helios Energy HIGH PRIORITY] (2pm)
AFTER:
> ⭐ Helios Energy (2pm) ⭐ > CTO replied personally to a demo request — strongest buying signal.
BEFORE (base omits the follow-up block, just narrates history):
> Vertex Systems — we last talked March 3 with Priya. She worried about > migration cost but liked the audit trail. They're still evaluating.
AFTER (six core bullets first, then the five follow-up bullets):
> 🔄 Vertex Systems (call) 🔄 > Re-engaging an evaluating prospect — audit trail already landed. > > - What they do: Enterprise workflow software vendor. > - Recent news: Continued platform expansion. > - Key person: Priya (Director)—evaluation owner. > - Pain point signal: Migration cost sensitivity (last call). > - Your angle: De-risk migration with phased rollout + audit-trail proof. > - Opening line: "Last time migration cost was the sticking point — want to walk through a phased path?" > - Last conversation: March 3—spoke with Priya (Director) > - What happened: Demoed audit trail; stalled on migration cost. > - Objection raised: Migration cost too high. > - What resonated: The audit-trail / compliance reporting. > - Status: Evaluating.
BEFORE (base writes prose or a wrongly-columned table):
> 10am Acme (Tom), 11am Brightside (James), 12pm Lumen (Dana)
AFTER:
> | Time | Company | Key Person | One-Liner | Priority | > |------|---------|------------|-----------|----------| > | 10am | Acme Mfg | Tom (Proc) | Follow up on Q3 tool-consolidation timeline | 🔄 | > | 11am | Brightside | James (COO) | Blue Cross growth angle | 🆕 | > | 12pm | Lumen | Dana (Ops) | Shipment-tracking pain, fresh research | 🆕 |
BEFORE: - **Opening line:** How are you today?
AFTER: - **Opening line:** "Saw your post on shipment-tracking pain — is that still the team's biggest headache?"
dropped the ball / promised a call and never made it." 🔄 is a normal follow-up; ⚠️ flags the overdue recovery. If it is both overdue AND a prior conversation, ⚠️ wins in the header; still append the five follow-up bullets if there is history.
still emit all six labels — fill the value with a best inference or (to research). Never drop a bullet to "save space."
emoji inside the bold span and an optional status icon after the time. When only one signal exists, reuse the same priority emoji in both slots rather than inventing a new symbol.
exact five columns; the follow-up nature shows in Priority (🔄), not in extra columns.
each; do not merge into a shared header or a table (that is the cheat-sheet shape, not the full briefing shape).
before the bold or as a trailing tag.
Pain point signal:, Your angle:, Opening line:;DON'T substitute Challenges:, Positioning:, Hook:.
[HIGH] text tags.One-Liner; DON'T write Summary or One liner.Pain points:, Approach:, Icebreaker:).One-Liner header.**<emoji> Company** (Time) <icon> + italic reason on the next line.Time | Company | Key Person | One-Liner | Priority.| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-08 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-02 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-04 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-14 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-01 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-11 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-15 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-07 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-18 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-05 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-16 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-21 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-06 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-09 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-03 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-10 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-19 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-12 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-13 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-17 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-20 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-22 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
DecimalAI ran this skill against gemini-3.5-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted. The headline lift of +82 percentage points is the difference between those two pass rates over the 22 comparable cases.
The per-case answers from this run were removed by the retention sweep, so the case table below shows the verdicts without the text either arm produced. The counts above were recorded at the time and are unaffected. Answers are now kept for 180 days.
| Model | Method | Date | Lift |
|---|---|---|---|
| gemini-3.5-flash | verified | 6/27/2026 | +100% |
Other measured skills in the registry, with their headline benchmark lift.