[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71CFTTYW1HA2MNX38EV1GJ5":3,"skill-same:01M71CFTTYW1HA2MNX38EV1GJ5":80},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":6,"ownerHtmlUrl":63,"ownerBlogUrl":6,"ownerDescription":64,"updatedAt":65,"install":66,"resources":79},"01M71CFTTYW1HA2MNX38EV1GJ5","yuri-sales-intelligence",null,"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'.","nexuslinkproductions\u002Fyuri-os","nexuslinkproductions","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F273246263?v=4","01M718YX9NZRCW50B59B8ZVDKN","Marcel Spatz","01M718YXAQ7530F4B1VKN6SFQV",2,"MIT","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-sales-intelligence\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"sales intelligence","yuri sales intelligence","sales","intelligence","frame","cold outreach","for","email","platform","sequence","sequences","write","ad creative","cold email","when","pitch","persona","social","paid","cold","2026-11-10 10:12:30",false,"---\nname: yuri-sales-intelligence\ndescription: \"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'.\"\ntriggers:\n  - \"\u002Fsales-intelligence\"\n  - \"\u002Fyuri-sales\"\n  - \"cold outreach\"\n  - \"write an opener\"\n  - \"sales sequence\"\n  - \"ad copy\"\n  - \"objection handling\"\nscope: instance\ninvocation: ability\n---\n\n# Yuri Sales Intelligence — Unified Outreach + Conversion Layer\n\n*Synthesized from OpenClaw corpus: cold-call-opener-builder, social-selling-touch-planner, objection-source-diagnoser, ad-creative*\n\n## Doctrine\n\nEvery 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.\n\n## Input Required\n\n- **Mode**: cold opener \u002F sequence \u002F ad copy \u002F objection rebuttal\n- **Product\u002Fservice**: what is being sold\n- **Buyer persona**: role, industry, size, pain\n- **Offer stage**: awareness \u002F consideration \u002F decision\n- **Channel**: email \u002F LinkedIn \u002F phone \u002F paid social (Meta\u002FGoogle\u002FTikTok)\n\n## Module 1: Cold Opener (First Touch)\n\n### Structure\n```\n[PATTERN INTERRUPT]: One sentence that breaks the pattern of every other outreach they receive.\n[SPECIFIC SIGNAL]: Why this person, why now. Reference something real (funding, post, hire, event).\n[PROBLEM FRAME]: Name their pain precisely. Not the category of pain — the specific friction.\n[MICRO-ASK]: The smallest possible next step. Not \"a demo\" — \"15 minutes\" or \"would it be useful if I sent...\"\n```\n\n### Opener Types by Persona\n\n| Persona | Hook Type | Example Frame |\n|---------|-----------|---------------|\n| Technical \u002F Engineer | Problem specificity | \"I noticed your stack uses X — the [specific issue] with that pattern is...\" |\n| Executive \u002F C-suite | Business outcome | \"Companies in [your sector] doing [X] are seeing [specific metric shift]...\" |\n| Founder \u002F Operator | Peer framing | \"I work with [similar founder type] on [specific challenge]...\" |\n| Individual buyer | Identity resonance | \"If you [specific behavior], this tends to be [specific result]...\" |\n\n## Module 2: Social Selling Touch Sequence (Multi-Touch)\n\n### 5-Touch LinkedIn\u002FEmail Sequence\n\n```\nTouch 1 (Day 1): Follow + warm comment on recent content. No pitch.\nTouch 2 (Day 3): Connect request with personalized note referencing Touch 1.\nTouch 3 (Day 7): Value-add DM — share something useful with no ask attached.\nTouch 4 (Day 12): Soft opener — problem frame + micro-ask.\nTouch 5 (Day 18): Direct ask — specific meeting request with clear agenda.\n```\n\n**Rules**:\n- Never pitch in the connection request\n- Every touch must deliver something or reference something real\n- The sequence breaks the moment you start repeating yourself\n- If they engage at any point, break the sequence and respond naturally\n\n## Module 3: Objection Source Diagnosis\n\n| Objection | Root Cause | Rebuttal Strategy |\n|-----------|------------|-------------------|\n| \"We don't have budget\" | Priority, not money | Reframe as cost of inaction. What does not solving it cost per quarter? |\n| \"We already have something\" | Switching cost fear | Identify the gap in what they have. Show the delta, not the replacement. |\n| \"Not the right time\" | Priority signal, not calendar signal | Agree, then anchor a trigger: \"When X happens, would that change?\" |\n| \"Send me more info\" | Low priority or social exit | Offer a 10-minute call instead of a document. Qualification, not content. |\n| \"Too expensive\" | Value not established | ROI anchor — what would achieving [outcome] be worth? |\n| \"We need to involve others\" | Process clarification needed | Ask who else is involved and what they would need to feel confident. |\n\n## Module 4: Ad Creative\n\n### Structure by Platform\n\n**Meta \u002F Instagram (Feed + Reel)**\n```\nVisual: Show the before or the result — not the product. Emotion before function.\nLine 1: The one sentence that stops the scroll. Question, stat, or bold claim.\nBody: Problem → solution → social proof → CTA. Under 125 chars on mobile.\nCTA: Single action verb. \"Get X\", \"See how\", \"Try free\".\n```\n\n**Google Search**\n```\nHeadline 1: Intent match — what the searcher typed, confirmed.\nHeadline 2: Differentiator — why you, not a competitor.\nHeadline 3: CTA or proof — \"Used by 5,000 teams\" \u002F \"Free 14-day trial\".\nDescription: Problem + outcome. Under 90 chars.\n```\n\n**LinkedIn Sponsored**\n```\nHook: Persona-specific pain. \"If you manage X, you know how...\"\nBody: Specific transformation, not general claim.\nProof: Named metric or named customer type (not always a name, but specific).\nCTA: Role-relevant ask — \"Download the playbook\" not \"Learn more\".\n```\n\n### Ad Creative Rules\n- Test the hook before the body — 3 hook variants per creative\n- One variable per test (not hook + image + body simultaneously)\n- Every claim must be specific: not \"improves productivity\" but \"cuts setup time from 4 hours to 20 minutes\"\n- Emotional resonance before logical proof — always\n\n## Session Notes\n\n### 2026-06-16\n- session: 178m | peak ctx: 0% | compacts: 0\n- 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\n- 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\n- errors: none\n\n### 2026-05-17\n- Created from corpus synthesis: 4 sales\u002Fmarketing skills merged into Musubi-native form\n- 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)\n- Corrections: none\n- Errors: none\n","# Yuri Sales Intelligence — Unified Outreach + Conversion Layer\n\n*Synthesized from OpenClaw corpus: cold-call-opener-builder, social-selling-touch-planner, objection-source-diagnoser, ad-creative*\n\n## Doctrine\n\nEvery 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.\n\n## Input Required\n\n- **Mode**: cold opener \u002F sequence \u002F ad copy \u002F objection rebuttal\n- **Product\u002Fservice**: what is being sold\n- **Buyer persona**: role, industry, size, pain\n- **Offer stage**: awareness \u002F consideration \u002F decision\n- **Channel**: email \u002F LinkedIn \u002F phone \u002F paid social (Meta\u002FGoogle\u002FTikTok)\n\n## Module 1: Cold Opener (First Touch)\n\n### Structure\n```\n[PATTERN INTERRUPT]: One sentence that breaks the pattern of every other outreach they receive.\n[SPECIFIC SIGNAL]: Why this person, why now. Reference something real (funding, post, hire, event).\n[PROBLEM FRAME]: Name their pain precisely. Not the category of pain — the specific friction.\n[MICRO-ASK]: The smallest possible next step. Not \"a demo\" — \"15 minutes\" or \"would it be useful if I sent...\"\n```\n\n### Opener Types by Persona\n\n| Persona | Hook Type | Example Frame |\n|---------|-----------|---------------|\n| Technical \u002F Engineer | Problem specificity | \"I noticed your stack uses X — the [specific issue] with that pattern is...\" |\n| Executive \u002F C-suite | Business outcome | \"Companies in [your sector] doing [X] are seeing [specific metric shift]...\" |\n| Founder \u002F Operator | Peer framing | \"I work with [similar founder type] on [specific challenge]...\" |\n| Individual buyer | Identity resonance | \"If you [specific behavior], this tends to be [specific result]...\" |\n\n## Module 2: Social Selling Touch Sequence (Multi-Touch)\n\n### 5-Touch LinkedIn\u002FEmail Sequence\n\n```\nTouch 1 (Day 1): Follow + warm comment on recent content. No pitch.\nTouch 2 (Day 3): Connect request with personalized note referencing Touch 1.\nTouch 3 (Day 7): Value-add DM — share something useful with no ask attached.\nTouch 4 (Day 12): Soft opener — problem frame + micro-ask.\nTouch 5 (Day 18): Direct ask — specific meeting request with clear agenda.\n```\n\n**Rules**:\n- Never pitch in the connection request\n- Every touch must deliver something or reference something real\n- The sequence breaks the moment you start repeating yourself\n- If they engage at any point, break the sequence and respond naturally\n\n## Module 3: Objection Source Diagnosis\n\n| Objection | Root Cause | Rebuttal Strategy |\n|-----------|------------|-------------------|\n| \"We don't have budget\" | Priority, not money | Reframe as cost of inaction. What does not solving it cost per quarter? |\n| \"We already have something\" | Switching cost fear | Identify the gap in what they have. Show the delta, not the replacement. |\n| \"Not the right time\" | Priority signal, not calendar signal | Agree, then anchor a trigger: \"When X happens, would that change?\" |\n| \"Send me more info\" | Low priority or social exit | Offer a 10-minute call instead of a document. Qualification, not content. |\n| \"Too expensive\" | Value not established | ROI anchor — what would achieving [outcome] be worth? |\n| \"We need to involve others\" | Process clarification needed | Ask who else is involved and what they would need to feel confident. |\n\n## Module 4: Ad Creative\n\n### Structure by Platform\n\n**Meta \u002F Instagram (Feed + Reel)**\n```\nVisual: Show the before or the result — not the product. Emotion before function.\nLine 1: The one sentence that stops the scroll. Question, stat, or bold claim.\nBody: Problem → solution → social proof → CTA. Under 125 chars on mobile.\nCTA: Single action verb. \"Get X\", \"See how\", \"Try free\".\n```\n\n**Google Search**\n```\nHeadline 1: Intent match — what the searcher typed, confirmed.\nHeadline 2: Differentiator — why you, not a competitor.\nHeadline 3: CTA or proof — \"Used by 5,000 teams\" \u002F \"Free 14-day trial\".\nDescription: Problem + outcome. Under 90 chars.\n```\n\n**LinkedIn Sponsored**\n```\nHook: Persona-specific pain. \"If you manage X, you know how...\"\nBody: Specific transformation, not general claim.\nProof: Named metric or named customer type (not always a name, but specific).\nCTA: Role-relevant ask — \"Download the playbook\" not \"Learn more\".\n```\n\n### Ad Creative Rules\n- Test the hook before the body — 3 hook variants per creative\n- One variable per test (not hook + image + body simultaneously)\n- Every claim must be specific: not \"improves productivity\" but \"cuts setup time from 4 hours to 20 minutes\"\n- Emotional resonance before logical proof — always\n\n## Session Notes\n\n### 2026-06-16\n- session: 178m | peak ctx: 0% | compacts: 0\n- 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\n- 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\n- errors: none\n\n### 2026-05-17\n- Created from corpus synthesis: 4 sales\u002Fmarketing skills merged into Musubi-native form\n- 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)\n- Corrections: none\n- Errors: none\n",{"name":5,"scope":49,"triggers":50,"invocation":57,"description":7},"instance",[51,52,29,53,54,55,56],"\u002Fsales-intelligence","\u002Fyuri-sales","write an opener","sales sequence","ad copy","objection handling","ability","main","4c6d8d65f3d6096e2fc25b0845e481dda73c2794","skills\u002Fyuri-sales-intelligence",0,"https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions","Building deterministic AI governance and continuity systems. Workflow architect + visual storyteller","2026-11-11 16:42:59",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add nexuslinkproductions\u002Fyuri-os --skill yuri-sales-intelligence",{"tool":72,"command":73},"bunx","bunx skills add nexuslinkproductions\u002Fyuri-os --skill yuri-sales-intelligence",{"tool":75,"command":76},"pnpm","pnpm dlx skills add nexuslinkproductions\u002Fyuri-os --skill yuri-sales-intelligence","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-sales-intelligence\u002FSKILL.md",true,[],[81,103,126,155,174,199],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":44},"01M71CG1AME5WC0A79AE65WT0X","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[88,89,90,91,92,93,94,95,96,97,98,99,100,38,101,102],"zoom out","zoom","code","it","context","re","section","how","understand","use","harness","with","perspective","true","you",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":44},"01M71CFY9ATD0BAXV6B14HFG7C","yuri-shura","6-perspective adversarial review for high-stakes turns (architecture decisions, refactor planning, deployment review) — fans out architect, adversary (7-vector attack), maintainer, ops, product, and security perspectives in parallel, then consolidates. Use when user says 'review this decision', '\u002Fshura', 'adversarial review', 'what could go wrong', 'architecture review', or 'deployment review'.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-shura\u002FSKILL.md",[],[110,111,112,113,114,30,115,116,98,117,118,119,120,121,122,123,38,124,97,125],"yuri shura","strategic review","decision","vector","deployment","planning","architecture review","parallel","perspectives","adversarial","review","architecture","decisions","workflow","ops","strategic",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":140,"publishedAt":44},"01M71CFQMBFTFADJNGP0Z2WCYK","yuri-code-intelligence","Unified code quality intelligence layer that diagnoses code smells (Long Method, Feature Envy, design pattern issues), prescribes targeted Fowler refactoring techniques, and reviews code for security, performance, and clarity. Use when user says 'review this code', 'refactor this', 'what's wrong with this method', 'code smells', or 'clean this up'.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-code-intelligence\u002FSKILL.md",[132,135],{"categoryNo":133,"categoryName":134,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":136,"categoryName":137,"taxonomyType":138,"taxonomyTypeDesc":139},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[27,141,90,142,38,97,143,144,145,146,147,148,149,150,30,151,152,153,98,154],"code intelligence","yuri code intelligence","design","improve","techniques","clean","issues","long","code review","performance","feature","code quality","reviews","up",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":44},"01M71CFP32RT6GD3GKNHCJP8VP","yuri-adw","Invoke when user asks to run the ADW loop \u002F agentic engineering loop \u002F software factory workflow.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-adw\u002FSKILL.md",[],[162,163,123,164,165,166,38,167,168,169,170,171,172,173],"yuri adw","run","user","agentic","engineering","invoke","loop","factory","agentic engineering","software","software factory","engineering loop",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":192,"publishedAt":44},"01M71CFK4VPEKY6A73237P7RSN","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[180,183,186,189],{"categoryNo":181,"categoryName":182,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":184,"categoryName":185,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":187,"categoryName":188,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":190,"categoryName":191,"taxonomyType":138,"taxonomyTypeDesc":139},"01JBSEEDCAT000000000000036","内容创作者",[193,194,195,97,114,196,98,197,123,38,198],"writing skills","writing","Existing","editing","work","new",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":207,"publishedAt":44},"01M71CFGS93M91C0J7SSPXM1NS","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[205,206],{"categoryNo":184,"categoryName":185,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":190,"categoryName":191,"taxonomyType":138,"taxonomyTypeDesc":139},[194,208,209,210,211,212,213,90,214,102,123,38,97,30,98],"writing plans","plans","spec","multi-step task","multi","task","requirements"]