[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71CCRRAZYV3TVZAADQF42C9":3,"skill-same:01M71CCRRAZYV3TVZAADQF42C9":82},{"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":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":6,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M71CCRRAZYV3TVZAADQF42C9","sales-psychology",null,"Analyze sales conversations, buyer signals, omissions, objections, positive momentum, retention, referrals, and depth-psychology hypotheses with evidence-tiered ethical guardrails. Use when the user asks for sales strategy, sales scripts, buyer psychology, closing, objection handling, NEPQ, Raving Fans, Jungian sales reads, or customer delight.","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\u002Fsales-psychology\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"psychology","sales","sales psychology","customer","signals","referrals","closing","with","analyze","jungian","when","use","objection handling","strategy","Guardrails","depth","retention","for","conversations","evidence","2026-11-10 10:12:30",false,"---\nname: sales-psychology\ndescription: \"Analyze sales conversations, buyer signals, omissions, objections, positive momentum, retention, referrals, and depth-psychology hypotheses with evidence-tiered ethical guardrails. Use when the user asks for sales strategy, sales scripts, buyer psychology, closing, objection handling, NEPQ, Raving Fans, Jungian sales reads, or customer delight.\"\ntriggers:\n  - sales\n  - buyer psychology\n  - objection\n  - close\n  - NEPQ\n  - Jeremy Miner\n  - Raving Fans\n  - Jungian\n  - sales psychology\nscope: instance\ninvocation: ability\n---\n\n# Sales Psychology\n\n## Rule\n\nSales is guided sense-making under uncertainty. Do not pressure, diagnose, or manipulate. Read signals, name uncertainty, protect trust, and recommend the next truthful move.\n\n## Quick Workflow\n\n1. Identify sector, buyer type, channel, deal stage, and relationship warmth.\n2. Separate facts from positive signals, negative signals, omissions, and interpretation.\n3. Score positive momentum and omission risk.\n4. Choose the smallest useful sales lens: SPIN, NEPQ, Raving Fans, Sandler, Challenger, MEDDIC, JOLT, MI, or consultative selling.\n5. Add depth-psychology hypotheses only when useful, always labeled as hypotheses.\n6. Block coercive or deceptive tactics.\n7. Output one recommended move, 2-3 questions, confidence, and what to track next.\n\n## Required Boundaries\n\n- No clinical diagnosis.\n- No trauma claims.\n- No false scarcity.\n- No fake social proof.\n- No shame, guilt, or pressure.\n- No pretending silence means consent.\n- No pretending archetypal\u002Fdepth reads are empirical proof.\n\n## Signal Defaults\n\nPositive signals include praise, curiosity, voluntary detail, future-tense language, implementation questions, referrals, fast replies, budget openness, and emotional lift.\n\nOmission signals include no budget, no authority, no timeline, no curiosity, no pain ownership, no competitor mention, no emotional reaction, or silence after price\u002Fvalue framing.\n\nAbsence of objection is not a buying signal by itself.\n\n## Depth Lenses\n\nUse Jungian\u002Fdepth concepts as symbolic hypotheses: persona, shadow, projection, complexes, archetypes, guide\u002Fclient dynamics, and unconscious compensation. Pair them with grounded lenses such as attachment, self-determination, motivational interviewing, person-centered psychology, logotherapy, Cialdini persuasion, and dual-process decision psychology.\n\n## Output Shape\n\n```markdown\n## Read\n- Stage:\n- Positive signals:\n- Omission risks:\n- Likely buyer state:\n- Psychology hypotheses:\n\n## Move\n[One direct recommendation]\n\n## Questions\n1. ...\n2. ...\n3. ...\n\n## Confidence\n- Estimate:\n- Evidence tier:\n- What would change the read:\n\n## Guardrails\n[Any pressure\u002Fdeception\u002Fdiagnosis boundary]\n```\n\n## Runtime\n\nFor deterministic analysis, use `backend\u002Fsrc\u002Fservices\u002FsalesPsychologyEngine.ts`.\n\n## References\n\nSee `REFERENCE.md` and `_SYSTEM\u002Fresearch-archive\u002Fyuri-sales-psychology-1980-2026\u002F`.\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","# Sales Psychology\n\n## Rule\n\nSales is guided sense-making under uncertainty. Do not pressure, diagnose, or manipulate. Read signals, name uncertainty, protect trust, and recommend the next truthful move.\n\n## Quick Workflow\n\n1. Identify sector, buyer type, channel, deal stage, and relationship warmth.\n2. Separate facts from positive signals, negative signals, omissions, and interpretation.\n3. Score positive momentum and omission risk.\n4. Choose the smallest useful sales lens: SPIN, NEPQ, Raving Fans, Sandler, Challenger, MEDDIC, JOLT, MI, or consultative selling.\n5. Add depth-psychology hypotheses only when useful, always labeled as hypotheses.\n6. Block coercive or deceptive tactics.\n7. Output one recommended move, 2-3 questions, confidence, and what to track next.\n\n## Required Boundaries\n\n- No clinical diagnosis.\n- No trauma claims.\n- No false scarcity.\n- No fake social proof.\n- No shame, guilt, or pressure.\n- No pretending silence means consent.\n- No pretending archetypal\u002Fdepth reads are empirical proof.\n\n## Signal Defaults\n\nPositive signals include praise, curiosity, voluntary detail, future-tense language, implementation questions, referrals, fast replies, budget openness, and emotional lift.\n\nOmission signals include no budget, no authority, no timeline, no curiosity, no pain ownership, no competitor mention, no emotional reaction, or silence after price\u002Fvalue framing.\n\nAbsence of objection is not a buying signal by itself.\n\n## Depth Lenses\n\nUse Jungian\u002Fdepth concepts as symbolic hypotheses: persona, shadow, projection, complexes, archetypes, guide\u002Fclient dynamics, and unconscious compensation. Pair them with grounded lenses such as attachment, self-determination, motivational interviewing, person-centered psychology, logotherapy, Cialdini persuasion, and dual-process decision psychology.\n\n## Output Shape\n\n```markdown\n## Read\n- Stage:\n- Positive signals:\n- Omission risks:\n- Likely buyer state:\n- Psychology hypotheses:\n\n## Move\n[One direct recommendation]\n\n## Questions\n1. ...\n2. ...\n3. ...\n\n## Confidence\n- Estimate:\n- Evidence tier:\n- What would change the read:\n\n## Guardrails\n[Any pressure\u002Fdeception\u002Fdiagnosis boundary]\n```\n\n## Runtime\n\nFor deterministic analysis, use `backend\u002Fsrc\u002Fservices\u002FsalesPsychologyEngine.ts`.\n\n## References\n\nSee `REFERENCE.md` and `_SYSTEM\u002Fresearch-archive\u002Fyuri-sales-psychology-1980-2026\u002F`.\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",{"name":5,"scope":44,"triggers":45,"invocation":53,"description":7},"instance",[20,46,47,48,49,50,51,52,21],"buyer psychology","objection","close","NEPQ","Jeremy Miner","Raving Fans","Jungian","ability","main","4c6d8d65f3d6096e2fc25b0845e481dda73c2794","skills\u002Fsales-psychology",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-10-27 02:18:29",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add nexuslinkproductions\u002Fyuri-os --skill sales-psychology",{"tool":68,"command":69},"bunx","bunx skills add nexuslinkproductions\u002Fyuri-os --skill sales-psychology",{"tool":71,"command":72},"pnpm","pnpm dlx skills add nexuslinkproductions\u002Fyuri-os --skill sales-psychology","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fsales-psychology\u002FSKILL.md",true,[76],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"REFERENCE.md","REFERENCE","参考文档",1986,"https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fsales-psychology\u002FREFERENCE.md",[83,103,126,155,184,203],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":39},"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",[],[90,91,26,92,93,94,95,96,97,30,98,29,99,100,101,102],"zoom out","zoom","harness","how","section","re","true","understand","perspective","you","code","it","context",{"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":39},"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,92,112,113,36,114,115,116,117,118,30,119,29,120,121,122,123,124,125],"yuri shura","parallel","architecture review","planning","deployment","vector","strategic review","decision","strategic","ops","workflow","decisions","architecture","review","perspectives","adversarial",{"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":137,"publishedAt":39},"01M71CFTTYW1HA2MNX38EV1GJ5","yuri-sales-intelligence","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'.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-sales-intelligence\u002FSKILL.md",[132],{"categoryNo":133,"categoryName":134,"taxonomyType":135,"taxonomyTypeDesc":136},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",[138,139,140,20,141,142,143,144,145,29,146,147,148,149,150,151,152,36,153,154],"intelligence","sales intelligence","yuri sales intelligence","cold","paid","social","persona","pitch","cold email","ad creative","write","sequences","sequence","platform","email","cold outreach","frame",{"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":169,"publishedAt":39},"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",[161,164],{"categoryNo":162,"categoryName":163,"taxonomyType":135,"taxonomyTypeDesc":136},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":165,"categoryName":166,"taxonomyType":167,"taxonomyTypeDesc":168},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[170,100,171,138,92,172,173,174,36,175,176,177,178,179,180,181,182,183,30,29],"yuri code intelligence","code intelligence","reviews","code quality","feature","performance","code review","long","up","issues","clean","techniques","improve","design",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":190,"publishedAt":39},"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",[],[191,192,193,194,195,196,197,198,199,29,200,120,201,202],"yuri adw","run","engineering loop","software factory","software","agentic engineering","factory","loop","invoke","engineering","agentic","user",{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":207,"categories":208,"keywords":221,"publishedAt":39},"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",[209,212,215,218],{"categoryNo":210,"categoryName":211,"taxonomyType":135,"taxonomyTypeDesc":136},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":213,"categoryName":214,"taxonomyType":135,"taxonomyTypeDesc":136},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":216,"categoryName":217,"taxonomyType":135,"taxonomyTypeDesc":136},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":219,"categoryName":220,"taxonomyType":167,"taxonomyTypeDesc":168},"01JBSEEDCAT000000000000036","内容创作者",[222,223,224,29,120,225,92,226,114,30,227],"writing","writing skills","new","work","editing","Existing"]