| name | yuri-sales-intelligence |
| description | Unified sales and outreach skill generating cold outreach openers, social selling sequences, objection rebuttals, and ad creative for any paid platform — multi-persona aware, adapting tone and offer frame to buyer type. Use when user says 'write a cold email', 'outreach sequence', 'objection handling', 'ad copy', or 'sales pitch'. |
| triggers | ["/sales-intelligence","/yuri-sales","cold outreach","write an opener","sales sequence","ad copy","objection handling"] |
| scope | instance |
| invocation | ability |
Yuri Sales Intelligence — Unified Outreach + Conversion Layer
Synthesized from OpenClaw corpus: cold-call-opener-builder, social-selling-touch-planner, objection-source-diagnoser, ad-creative
Doctrine
Every touchpoint has one job. The opener earns the next message. The sequence earns the meeting. The ad earns the click. Objection handling earns the trust that the sale hasn't earned yet. Intelligence means knowing which job you're doing before you write a single word.
Input Required
- Mode: cold opener / sequence / ad copy / objection rebuttal
- Product/service: what is being sold
- Buyer persona: role, industry, size, pain
- Offer stage: awareness / consideration / decision
- Channel: email / LinkedIn / phone / paid social (Meta/Google/TikTok)
Module 1: Cold Opener (First Touch)
Structure
[PATTERN INTERRUPT]: One sentence that breaks the pattern of every other outreach they receive.
[SPECIFIC SIGNAL]: Why this person, why now. Reference something real (funding, post, hire, event).
[PROBLEM FRAME]: Name their pain precisely. Not the category of pain — the specific friction.
[MICRO-ASK]: The smallest possible next step. Not "a demo" — "15 minutes" or "would it be useful if I sent..."
Opener Types by Persona
| Persona | Hook Type | Example Frame |
|---|
| Technical / Engineer | Problem specificity | "I noticed your stack uses X — the [specific issue] with that pattern is..." |
| Executive / C-suite | Business outcome | "Companies in [your sector] doing [X] are seeing [specific metric shift]..." |
| Founder / Operator | Peer framing | "I work with [similar founder type] on [specific challenge]..." |
| Individual buyer | Identity resonance | "If you [specific behavior], this tends to be [specific result]..." |
Module 2: Social Selling Touch Sequence (Multi-Touch)
5-Touch LinkedIn/Email Sequence
Touch 1 (Day 1): Follow + warm comment on recent content. No pitch.
Touch 2 (Day 3): Connect request with personalized note referencing Touch 1.
Touch 3 (Day 7): Value-add DM — share something useful with no ask attached.
Touch 4 (Day 12): Soft opener — problem frame + micro-ask.
Touch 5 (Day 18): Direct ask — specific meeting request with clear agenda.
Rules:
- Never pitch in the connection request
- Every touch must deliver something or reference something real
- The sequence breaks the moment you start repeating yourself
- If they engage at any point, break the sequence and respond naturally
Module 3: Objection Source Diagnosis
| Objection | Root Cause | Rebuttal Strategy |
|---|
| "We don't have budget" | Priority, not money | Reframe as cost of inaction. What does not solving it cost per quarter? |
| "We already have something" | Switching cost fear | Identify the gap in what they have. Show the delta, not the replacement. |
| "Not the right time" | Priority signal, not calendar signal | Agree, then anchor a trigger: "When X happens, would that change?" |
| "Send me more info" | Low priority or social exit | Offer a 10-minute call instead of a document. Qualification, not content. |
| "Too expensive" | Value not established | ROI anchor — what would achieving [outcome] be worth? |
| "We need to involve others" | Process clarification needed | Ask who else is involved and what they would need to feel confident. |
Module 4: Ad Creative
Structure by Platform
Meta / Instagram (Feed + Reel)
Visual: Show the before or the result — not the product. Emotion before function.
Line 1: The one sentence that stops the scroll. Question, stat, or bold claim.
Body: Problem → solution → social proof → CTA. Under 125 chars on mobile.
CTA: Single action verb. "Get X", "See how", "Try free".
Google Search
Headline 1: Intent match — what the searcher typed, confirmed.
Headline 2: Differentiator — why you, not a competitor.
Headline 3: CTA or proof — "Used by 5,000 teams" / "Free 14-day trial".
Description: Problem + outcome. Under 90 chars.
LinkedIn Sponsored
Hook: Persona-specific pain. "If you manage X, you know how..."
Body: Specific transformation, not general claim.
Proof: Named metric or named customer type (not always a name, but specific).
CTA: Role-relevant ask — "Download the playbook" not "Learn more".
Ad Creative Rules
- Test the hook before the body — 3 hook variants per creative
- One variable per test (not hook + image + body simultaneously)
- Every claim must be specific: not "improves productivity" but "cuts setup time from 4 hours to 20 minutes"
- Emotional resonance before logical proof — always
Session Notes
2026-06-16
- session: 178m | peak ctx: 0% | compacts: 0
- tools: Bash×205, Read×121, WebFetch×114, Edit×87, WebSearch×72, Write×33, TodoWrite×13, Agent×10, ToolSearch×9, Skill×4, AskUserQuestion×1, mcp×1, TaskStop×1
- corrections: go over it again, full red team and grounding in more fresh online research together with local, then check the compatibility across other organs, run phase 1. all agentic nano swarm | 'The legal one is the wall: an Austria-resident running automated Polymarket ' rick we are not doing full automated trading on polymarket, also polymarket is allowed in austria, you mustve fact checke | go over it again, full red team and grounding in more fresh online research together with local, then check the compatibility across other organs, run phase 1. all agentic nano swarm
- errors: none
2026-05-17
- Created from corpus synthesis: 4 sales/marketing skills merged into Musubi-native form
- Sources: cold-call-opener-builder (opener structure + persona matrix), social-selling-touch-planner (5-touch sequence), objection-source-diagnoser (root cause + rebuttal), ad-creative (platform-specific ad structure)
- Corrections: none
- Errors: none