[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M751ASQ9GQZNNWKKWD9E75PW":3,"skill-same:01M751ASQ9GQZNNWKKWD9E75PW":49},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":31,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M751ASQ9GQZNNWKKWD9E75PW","partnership-strategy",null,"Identifies, prioritizes, and structures business partnerships that produce measurable revenue - matching partnership type to goal, setting economics with real rev-share ranges, and enforcing a pilot-before-contract rule. Use when someone asks \"should we partner with X\", \"how do we structure a reseller deal\", \"what rev share is normal\", \"our partnerships never produce anything\", or \"which partners should we prioritize\". Do NOT use for choosing between partnerships and other distribution channels - use channel-strategy instead - or for the overall market-entry plan a partnership sits inside - use go-to-market-planner instead.","SkillMedev\u002Fskills","SkillMedev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F298078254?v=4","01M74ZSGTQ918CB0VXW4EG3RMX","SkillMe","01M74ZSGVBT497NA95CBT8JTY4",25,"MIT","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpartnership-strategy\u002FSKILL.md",[],[],"2026-11-11 18:11:01",false,"---\nname: partnership-strategy\ndescription: Identifies, prioritizes, and structures business partnerships that produce measurable revenue - matching partnership type to goal, setting economics with real rev-share ranges, and enforcing a pilot-before-contract rule. Use when someone asks \"should we partner with X\", \"how do we structure a reseller deal\", \"what rev share is normal\", \"our partnerships never produce anything\", or \"which partners should we prioritize\". Do NOT use for choosing between partnerships and other distribution channels - use channel-strategy instead - or for the overall market-entry plan a partnership sits inside - use go-to-market-planner instead.\nmetadata:\n  title: \"Partnership Strategy\"\n---\n\n# Partnership Strategy\n\nMost partnerships are press releases that produce nothing: signed with fanfare, staffed by nobody, dead within two quarters. A real partnership creates measurable value for both sides and has a named owner accountable for a number. This skill separates strategic partnerships from logo-swap theater and structures the deal so the partner's people are actually incentivized to sell.\n\n## Operating procedure\n\nFit-test before structuring, pilot before contract - in that order, because a well-structured deal with a bad-fit partner still produces nothing, and a deep contract before a proven motion locks in the failure.\n\n### Step 1: Gather inputs\n\n1. The goal - awareness, reach into a locked market, product stickiness, or a new revenue line. One primary goal; a partnership chasing three goals achieves none.\n2. Candidate partners, if any exist, with what is known about their customer base.\n3. Your ACV, margin, and sales motion - these bound what economics you can offer.\n4. Capacity - who on your side would own this, at what fraction of their time. If the answer is nobody, stop here.\n\n### Step 2: Match the partnership type to the goal\n\n- Co-marketing (shared content, events, audiences): low commitment, fast, modest upside. For awareness.\n- Technology \u002F integration: your product connects to theirs, increasing stickiness and reach. Often the highest ROI for software. For retention and product depth.\n- Distribution \u002F channel (they sell or resell you): high ceiling, slow to build, needs enablement. For reach into a locked market.\n- OEM \u002F embed (white-labeled into their product): deep and durable, but you cede the customer relationship. Price for that loss.\n\n### Step 3: Run the strategic fit test\n\nAll four must pass before any deal talk:\n\n1. Shared customer, non-competing product - same buyer, no cannibalization.\n2. Mutual value - both sides get something they cannot easily build alone. One-sided partnerships die quietly.\n3. Strategic, not opportunistic - it advances your distribution or product strategy, not just a logo for the website.\n4. Capacity to execute - both sides can actually staff it. An unstaffed partnership is a press release.\n\n### Step 4: Structure the economics\n\nDefine the value exchange concretely - who provides what, who gets what - and put money where you want motion. Practitioner ranges:\n\n- Referral fees: 10-20% of first-year contract value for a warm intro that closes; one-time.\n- Reseller \u002F channel margin: 20-40% off list, scaling with how much of the sale (demo, close, first-line support) the partner owns. Under 20%, their reps will not bother; the deal fails economically before it fails operationally.\n- Co-sell splits: full quota credit or retirement for the partner's rep on sourced deals - split commissions kill co-sell motions.\n- OEM \u002F embed: per-unit or revenue-based royalty, floor-protected; you are trading margin for distribution and losing the customer relationship, so price durability in.\n\nAgree success metrics up front - sourced leads, sourced revenue, integration adoption - with a review cadence.\n\n### Step 5: Pilot before contract\n\nThe pilot-before-contract rule: never sign a multi-year or exclusive agreement before a lightweight pilot proves the motion. Default pilot: 90 days, one segment or region, a simple letter agreement, and a numeric success bar set in advance (e.g., 10 sourced qualified opportunities or 2 closed deals). If the pilot misses the bar, renegotiate or walk - do not sign the big contract hoping scale fixes what the pilot exposed. Exclusivity is only ever traded for a committed, contractual number.\n\n### Step 6: Build the operating motion\n\nPartnerships fail from the lack of an operating motion far more often than from the contract:\n\n- Name one owner on each side accountable for the number.\n- Enable the partner's team: training, collateral, a clear pitch. An untrained partner sales force sells nothing.\n- Stand up a biweekly sync and a shared pipeline view.\n- Reduce friction relentlessly: the lower the effort for their reps, the more they sell.\n\n### Step 7: Prioritize the portfolio\n\nScore every candidate on reach × fit × ease of execution (1-5 each) and concentrate on the top two or three. One deep partnership beats ten shallow MOUs.\n\n## Worked artifact: deal one-pager template\n\n```\nPARTNERSHIP ONE-PAGER - [FILL: partner] x [FILL: your company]\nGoal (one):            [FILL: awareness \u002F locked-market reach \u002F stickiness \u002F revenue line]\nType:                  [FILL: co-marketing \u002F integration \u002F distribution \u002F OEM]\nFit test:              shared buyer [Y\u002FN]  mutual value [Y\u002FN]  strategic [Y\u002FN]  staffed [Y\u002FN]\nValue exchange:        we provide [FILL]; they provide [FILL]\nEconomics:             [FILL: e.g., 15% referral fee first-year ACV \u002F 30% reseller margin]\nPilot (90 days):       scope [FILL: segment\u002Fregion]; success bar [FILL: numeric];\n                       decision date [FILL]\nOwners:                us [FILL name, % time]; them [FILL name]\nMetrics + cadence:     [FILL: sourced pipeline $, sourced revenue $]; biweekly sync\nKill criteria:         pilot misses bar by >50%, or no partner-sourced activity in 60 days\n```\n\n## Deliverable\n\nProduce a partnership plan: target partners scored on reach\u002Ffit\u002Fease, the recommended type per target matched to the stated goal, a deal structure with concrete value exchange and economics inside the practitioner ranges, a 90-day pilot design with a numeric success bar, and the operating motion with named owners, enablement plan, and review cadence.\n\n## Do NOT\n\n- Do not sign for the press release with no operating plan - announcement-only partnerships damage credibility with the partner's team for the real attempt later.\n- Do not structure a channel deal under 20% margin and expect motion; the partner's reps optimize their own commission math.\n- Do not grant exclusivity without a committed contractual number in return.\n- Do not skip the pilot because the partner is big; big partners are the slowest to produce and the costliest to unwind.\n- Do not pursue a logo whose customers are not your buyers - reach without fit is zero.\n- Do not leave the partnership ownerless after signing; nobody's job means nothing happens.\n\n## Quality bar\n\n- Each target passes all four fit-test gates explicitly, or is cut with the failed gate named.\n- Economics fall inside the stated ranges or the deviation is justified in writing.\n- Every deal has a 90-day pilot with a numeric bar and a decision date before any long-term contract.\n- One named owner per side, with time allocation, appears in the plan.\n- Kill criteria exist for every partnership, not just success metrics.\n","# Partnership Strategy\n\nMost partnerships are press releases that produce nothing: signed with fanfare, staffed by nobody, dead within two quarters. A real partnership creates measurable value for both sides and has a named owner accountable for a number. This skill separates strategic partnerships from logo-swap theater and structures the deal so the partner's people are actually incentivized to sell.\n\n## Operating procedure\n\nFit-test before structuring, pilot before contract - in that order, because a well-structured deal with a bad-fit partner still produces nothing, and a deep contract before a proven motion locks in the failure.\n\n### Step 1: Gather inputs\n\n1. The goal - awareness, reach into a locked market, product stickiness, or a new revenue line. One primary goal; a partnership chasing three goals achieves none.\n2. Candidate partners, if any exist, with what is known about their customer base.\n3. Your ACV, margin, and sales motion - these bound what economics you can offer.\n4. Capacity - who on your side would own this, at what fraction of their time. If the answer is nobody, stop here.\n\n### Step 2: Match the partnership type to the goal\n\n- Co-marketing (shared content, events, audiences): low commitment, fast, modest upside. For awareness.\n- Technology \u002F integration: your product connects to theirs, increasing stickiness and reach. Often the highest ROI for software. For retention and product depth.\n- Distribution \u002F channel (they sell or resell you): high ceiling, slow to build, needs enablement. For reach into a locked market.\n- OEM \u002F embed (white-labeled into their product): deep and durable, but you cede the customer relationship. Price for that loss.\n\n### Step 3: Run the strategic fit test\n\nAll four must pass before any deal talk:\n\n1. Shared customer, non-competing product - same buyer, no cannibalization.\n2. Mutual value - both sides get something they cannot easily build alone. One-sided partnerships die quietly.\n3. Strategic, not opportunistic - it advances your distribution or product strategy, not just a logo for the website.\n4. Capacity to execute - both sides can actually staff it. An unstaffed partnership is a press release.\n\n### Step 4: Structure the economics\n\nDefine the value exchange concretely - who provides what, who gets what - and put money where you want motion. Practitioner ranges:\n\n- Referral fees: 10-20% of first-year contract value for a warm intro that closes; one-time.\n- Reseller \u002F channel margin: 20-40% off list, scaling with how much of the sale (demo, close, first-line support) the partner owns. Under 20%, their reps will not bother; the deal fails economically before it fails operationally.\n- Co-sell splits: full quota credit or retirement for the partner's rep on sourced deals - split commissions kill co-sell motions.\n- OEM \u002F embed: per-unit or revenue-based royalty, floor-protected; you are trading margin for distribution and losing the customer relationship, so price durability in.\n\nAgree success metrics up front - sourced leads, sourced revenue, integration adoption - with a review cadence.\n\n### Step 5: Pilot before contract\n\nThe pilot-before-contract rule: never sign a multi-year or exclusive agreement before a lightweight pilot proves the motion. Default pilot: 90 days, one segment or region, a simple letter agreement, and a numeric success bar set in advance (e.g., 10 sourced qualified opportunities or 2 closed deals). If the pilot misses the bar, renegotiate or walk - do not sign the big contract hoping scale fixes what the pilot exposed. Exclusivity is only ever traded for a committed, contractual number.\n\n### Step 6: Build the operating motion\n\nPartnerships fail from the lack of an operating motion far more often than from the contract:\n\n- Name one owner on each side accountable for the number.\n- Enable the partner's team: training, collateral, a clear pitch. An untrained partner sales force sells nothing.\n- Stand up a biweekly sync and a shared pipeline view.\n- Reduce friction relentlessly: the lower the effort for their reps, the more they sell.\n\n### Step 7: Prioritize the portfolio\n\nScore every candidate on reach × fit × ease of execution (1-5 each) and concentrate on the top two or three. One deep partnership beats ten shallow MOUs.\n\n## Worked artifact: deal one-pager template\n\n```\nPARTNERSHIP ONE-PAGER - [FILL: partner] x [FILL: your company]\nGoal (one):            [FILL: awareness \u002F locked-market reach \u002F stickiness \u002F revenue line]\nType:                  [FILL: co-marketing \u002F integration \u002F distribution \u002F OEM]\nFit test:              shared buyer [Y\u002FN]  mutual value [Y\u002FN]  strategic [Y\u002FN]  staffed [Y\u002FN]\nValue exchange:        we provide [FILL]; they provide [FILL]\nEconomics:             [FILL: e.g., 15% referral fee first-year ACV \u002F 30% reseller margin]\nPilot (90 days):       scope [FILL: segment\u002Fregion]; success bar [FILL: numeric];\n                       decision date [FILL]\nOwners:                us [FILL name, % time]; them [FILL name]\nMetrics + cadence:     [FILL: sourced pipeline $, sourced revenue $]; biweekly sync\nKill criteria:         pilot misses bar by >50%, or no partner-sourced activity in 60 days\n```\n\n## Deliverable\n\nProduce a partnership plan: target partners scored on reach\u002Ffit\u002Fease, the recommended type per target matched to the stated goal, a deal structure with concrete value exchange and economics inside the practitioner ranges, a 90-day pilot design with a numeric success bar, and the operating motion with named owners, enablement plan, and review cadence.\n\n## Do NOT\n\n- Do not sign for the press release with no operating plan - announcement-only partnerships damage credibility with the partner's team for the real attempt later.\n- Do not structure a channel deal under 20% margin and expect motion; the partner's reps optimize their own commission math.\n- Do not grant exclusivity without a committed contractual number in return.\n- Do not skip the pilot because the partner is big; big partners are the slowest to produce and the costliest to unwind.\n- Do not pursue a logo whose customers are not your buyers - reach without fit is zero.\n- Do not leave the partnership ownerless after signing; nobody's job means nothing happens.\n\n## Quality bar\n\n- Each target passes all four fit-test gates explicitly, or is cut with the failed gate named.\n- Economics fall inside the stated ranges or the deviation is justified in writing.\n- Every deal has a 90-day pilot with a numeric bar and a decision date before any long-term contract.\n- One named owner per side, with time allocation, appears in the plan.\n- Kill criteria exist for every partnership, not just success metrics.\n",{"name":5,"metadata":24,"description":7},{"title":25},"Partnership Strategy","main","97a13607d669157a4a16d5ba79b77f208319f7b9","skills\u002Fpartnership-strategy",3,"https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills","https:\u002F\u002Fskillme.dev","https:\u002F\u002Fgithub.com\u002FSkillMedev","MCP-native catalog of Claude Agent Skills. Browse, recommend, install, and auto-apply skills in chat. Open source, every skill free and clonable on GitHub.","2026-10-14 03:19:31",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add SkillMedev\u002Fskills --skill partnership-strategy",{"tool":41,"command":42},"bunx","bunx skills add SkillMedev\u002Fskills --skill partnership-strategy",{"tool":44,"command":45},"pnpm","pnpm dlx skills add SkillMedev\u002Fskills --skill partnership-strategy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpartnership-strategy\u002FSKILL.md",true,[],[50,60,67,74,81,88],{"skillNo":51,"name":52,"nameZh":53,"description":54,"descriptionZh":55,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":59},"01M75271B256DF3FX2VG5VRYEE","zone-2-cardio-plan","有氧运动计划","Use when someone asks to build a steady-state cardio plan, train an aerobic base or Zone 2, structure easy or endurance weekly cardio, train by heart-rate zones, or improve resting heart rate, VO2, or endurance. Builds a heart-rate-zone aerobic training block with session structure, modality choice, and progression. General fitness guidance, not medical advice. Do NOT use to design a strength or lifting program (use Strength Training Plan), high-intensity interval conditioning, HIIT, or circuits (use Conditioning & HIIT Program), or a mobility\u002Fflexibility routine (use Mobility Routine).","当有人要求制定稳态有氧训练计划、进行有氧基础训练或达到第二区间、安排轻松或耐力型的每周有氧训练、按心率区间训练，或提高静息心率、最大摄氧量或耐力时，可以使用此方案。该方案构建了一个包含训练计划结构、训练方式选择和进度安排的心率区间有氧训练模块。本方案仅提供一般健身指导，不构成医疗建议。请勿用于设计力量或举重训练计划（请使用力量训练计划）、高强度间歇训练 (HIIT) 或循环训练（请使用体能训练和 HIIT 计划），或灵活性\u002F柔韧性训练（请使用灵活性训练计划）。","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzone-2-cardio-plan\u002FSKILL.md",[],[],"2026-11-11 18:27:18",{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":59},"01M7526VP1QBBKYBE17S1WR86Y","youtube-script-writer","Writes retention-engineered long-form YouTube scripts on a hook\u002Fbody\u002Fpayoff architecture - a first-30-seconds hook that survives the retention cliff, a beat-sheet body with mini-hooks and bridges, timed pattern interrupts, and a payoff that over-delivers - with B-roll and editing cues marked inline. Use when someone says \"script my next video\", \"my retention graph dies at the start\", \"tighten this draft\", or \"outline a video on X\". Do NOT use for the 3-second opener of TikTok, Reels, or Shorts - use video-hook-writer instead; do NOT use for spoken voiceover synced to on-screen tutorial actions - use narration-script instead; do NOT use for a sales demo built on a buyer's discovery notes - use demo-script instead; do NOT use to design the thumbnail and title - use thumbnail-concept instead.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-script-writer\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":59},"01M7526P2T0WKMHDXS4Q58237T","win-back-campaign","Designs segmented win-back email sequences for dormant users - dormancy tiers, a three-beat sequence with a single proportional incentive, and a suppression rule - and measures success by re-activation, not opens. Use when someone says \"our users went quiet\", \"design a win-back campaign\", \"how do I re-engage lapsed customers\", \"should we email people who haven't logged in for months\", or lifecycle messaging has stopped landing with a lapsed segment. Do NOT use for recovering an unfinished checkout - use abandoned-cart-sequence instead. Do NOT use for diagnosing and fixing why active customers cancel - use churn-reduction instead. Do NOT use for building always-on onboarding or nurture flows - use email-drip-builder instead.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwin-back-campaign\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":59},"01M7526HF2RCDJ50P93WRZRHVV","wikipedia-style","Writes neutral, verifiable, encyclopedic prose following Wikipedia's core content policies and manual of style - NPOV, inline citations, notability-backed claims, and a strict ban on promotional language. Use when someone asks \"write this like a Wikipedia article\", \"draft a Wikipedia page for this company or person\", \"make this neutral and encyclopedic\", or \"why does my article draft keep getting rejected\". Do NOT use for persuasive or opinion writing - use op-ed-writer instead; for thesis-driven academic papers, use academic-essay; for verifying claims in existing text, use fact-checker.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwikipedia-style\u002FSKILL.md",[],[],{"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":59},"01M7526D43CTGRKGKNQ2GB0KVX","whitepapers","Structures and writes authoritative B2B whitepapers - a standalone executive summary, a data-sized problem statement, methodology, evidence-driven findings, recommendations, and a soft call to action - flagging every claim that needs a real citation. Use when a marketer asks \"write a whitepaper on this topic\", \"turn our research into a lead-gen asset\", \"make this credible enough for executives\", or a draft reads like a product pitch instead of analysis. Do NOT use for customer-story-driven proof - use case-study-builder instead; for policy audiences, use policy-brief.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwhitepapers\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":59},"01M75268423Y3K50SY5WC2NX2G","white-space-analysis","Finds unmet market gaps by ranking jobs-to-be-done on importance versus satisfaction, overlaying them against current solutions and workarounds, and validating that each gap is real, winnable, and worth winning. Use when someone asks \"where are the gaps in this market\", \"what's underserved here\", \"where should we play next\", or is hunting for product, feature, or market-entry opportunities. Do NOT use for profiling competitors and building battle cards - use competitive-intelligence instead; for putting a dollar figure on an identified opportunity - use market-sizing instead; for extracting jobs-to-be-done from raw customer interviews - use jtbd-extractor instead.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwhite-space-analysis\u002FSKILL.md",[],[]]