[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EV8S3592WH2EZ2FB463M6G":3,"skill-same:01M7EV8S3592WH2EZ2FB463M6G":47},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EV8S3592WH2EZ2FB463M6G","partnership-manager",null,"Build strategic partnerships — sourcing, structuring deals, co-marketing, and managing partner relationships.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-partnership-manager\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: partnership-manager\ndescription: Build strategic partnerships — sourcing, structuring deals, co-marketing, and managing partner relationships.\ncategory: business-marketing\n---\n\n## Overview\n\nPartnerships accelerate growth by borrowing trust, distribution, and capabilities: co-marketing, integrations, resellers, and strategic alliances. This skill covers the partnership lifecycle — identifying the right partners, structuring win-win deals, launching joint initiatives, and managing relationships for compounding returns.\n\n## When to use\n\n- Finding partnership opportunities\n- Structuring a co-marketing deal\n- Negotiating partnership terms\n- Launching an integration partnership\n- Building a partner program\n- Fixing underperforming partnerships\n\n- Building technology integration partnerships\n- Managing strategic alliance relationships\n- Creating partner advisory boards\n- Exiting underperforming partnerships\n## Core concepts\n\n**Partnership types.** Co-marketing (joint campaigns, shared audiences), product integrations (better together story), reseller\u002Freferral (they sell you), distribution (bundled or embedded), strategic alliances (deeper, multi-threaded). Match type to the goal.\n\n**Partner fit.** Overlapping (not identical) audiences, complementary (not competing) offerings, compatible brand values, and mutual benefit that's roughly balanced. Asymmetric partnerships die — both sides must win clearly.\n\n**Deal structure.** Define: what each side contributes (audience, product, budget, effort), what each side gets (leads, revenue, brand), exclusivity (rarely wise), term and renewal, IP and brand usage, data sharing rules, and exit clauses. Put it in writing — even \"simple\" partnerships.\n\n**Co-marketing plays.** Joint webinars, co-branded content\u002Fguides, integration announcements, shared booths at events, newsletter swaps, bundled offers. Each needs: shared goal, agreed promotion commitments from both sides, and lead-sharing rules.\n\n**Partner enablement.** Partners sell you only if it's easy: one-pagers, pitch decks, demo environments, deal registration, training, and a responsive contact. Treat partners like a sales channel that needs enablement.\n\n**Relationship management.** Executive sponsor on both sides, quarterly business reviews, shared dashboards, joint planning. Partnerships decay without active management — assign an owner.\n\n\n**Partnership types.** Technology (integrations, APIs), channel (resellers, distributors), strategic alliances (joint GTM), content (co-marketing), and referral.\nEach type needs different agreements, metrics, and management rhythms — do not manage them identically.\nStart with the type matching your biggest gap (distribution? credibility? capability?).\n**Partner lifecycle.** Recruit → onboard → activate (first joint win) → grow (expand scope) → optimize or exit.\nMost partnerships die between onboard and activate — the first joint win is the critical milestone.\nDesign onboarding around reaching that first win in 90 days.\n**Co-selling motions.** Joint account planning, warm introductions, coordinated outreach, and shared deal support.\nCo-selling needs: clear rules of engagement, shared CRM visibility, and joint pipeline reviews.\nWithout operational integration, \"strategic partnerships\" remain press releases.\n## Practical workflow\n\n1. **Define partnership goals.** Distribution? Credibility? Product capability? Set targets (leads, revenue, integrations shipped).\n2. **Build the target list.** Map your ecosystem: who shares your buyers? Score candidates on audience overlap, brand fit, and likelihood to engage. Prioritize 10–20.\n3. **Outreach with a specific idea.** Don't pitch \"let's partner\" — pitch a concrete joint initiative (webinar, integration, co-branded guide). Specificity gets replies; vagueness gets ignored.\n4. **Structure the deal.** Negotiate contributions and benefits explicitly. Document in a partnership agreement or MOU. Agree on promotion commitments (e.g., \"two emails to 50k list\") — vague promises produce vague results.\n5. **Launch jointly.** Coordinate announcements, run the co-marketing play, enable their team, track shared metrics in one dashboard both sides see.\n6. **Manage and expand.** Quarterly reviews: what worked, pipeline generated, next initiatives. Double down on winners; sunset partnerships where effort exceeds return. Turn great partners into case studies that attract more partners.\n\n**Partnership one-pager:** partner profile → why now → joint value proposition → proposed initiative → each side's commitments → success metrics → timeline → owner.\n\n\n**Partner tiering:** strategic (joint roadmap, executive sponsors, co-selling) → growth (co-marketing, referral motions) → long-tail (self-serve referral links, minimal touch). Allocate your time 50\u002F30\u002F20 across tiers. Review tiering quarterly — partners migrate as they prove out or fade.\n\n**Partner launch package:** co-branded one-pager, joint solution brief, referral process doc (how leads are passed and tracked), SPIF\u002Fincentive terms, 30-60-90 day joint plan with named owners on both sides, and a shared Slack channel. Partnerships without a launch package drift into logo-swaps.\n\n**Partner business plan (annual):** joint objectives → target accounts\u002Fsegments → planned activities by quarter → investment from each side → pipeline and revenue targets → governance (QBR cadence, executive sponsors).\nBoth sides sign — mutual commitment separates real partnerships from logo swaps.\n**Conflict resolution:** documented escalation path → 48-hour resolution SLA → executive sponsor involvement for strategic partners → termination clauses for repeated violations.\nAddress conflicts immediately; festering disputes kill partnerships slowly.\n## Common pitfalls\n\n- **Vague agreements.** \"Let's collaborate\" with no defined commitments. Specificity or nothing.\n- **Asymmetric value.** One side does all the work. Partnerships need balanced give-and-get.\n- **No owner.** Partnerships managed by \"everyone\" are managed by no one. Assign one owner per partner.\n- **Logo-slide partnerships.** Announced with fanfare, never activated. Launch with a real joint initiative.\n- **Ignoring small partners.** Chasing only big logos while nimble smaller partners drive actual pipeline. Portfolio approach.\n- **No exit criteria.** Keeping zombie partnerships alive out of politeness. Review quarterly; sunset the duds.\n- **Partner conflict.** Overlapping partners competing for the same deals. Define territories\u002Frules of engagement upfront.\n- **Partnerships without pipeline targets.** Activity (meetings, MOUs) mistaken for progress. Every partnership gets a pipeline goal and a review date — kill or fix those that miss twice.\n- **Single-threaded relationships.** One champion each side. When they leave, the partnership dies. Build multi-threaded connections from day one.\n- **Partner quantity over quality.** Dozens of inactive partnerships. Five active partnerships beat fifty logos — prune annually.\n- **Asymmetric investment.** You invest heavily; they do nothing. Require reciprocal commitments upfront; measure both sides quarterly.\n- **Messy exits.** Partnerships fading without closure. Formal sunsets protect relationships and reputations.\n- **No success metrics.** Partnerships without KPIs drift. Define success upfront; review quarterly.\n","## Overview\n\nPartnerships accelerate growth by borrowing trust, distribution, and capabilities: co-marketing, integrations, resellers, and strategic alliances. This skill covers the partnership lifecycle — identifying the right partners, structuring win-win deals, launching joint initiatives, and managing relationships for compounding returns.\n\n## When to use\n\n- Finding partnership opportunities\n- Structuring a co-marketing deal\n- Negotiating partnership terms\n- Launching an integration partnership\n- Building a partner program\n- Fixing underperforming partnerships\n\n- Building technology integration partnerships\n- Managing strategic alliance relationships\n- Creating partner advisory boards\n- Exiting underperforming partnerships\n## Core concepts\n\n**Partnership types.** Co-marketing (joint campaigns, shared audiences), product integrations (better together story), reseller\u002Freferral (they sell you), distribution (bundled or embedded), strategic alliances (deeper, multi-threaded). Match type to the goal.\n\n**Partner fit.** Overlapping (not identical) audiences, complementary (not competing) offerings, compatible brand values, and mutual benefit that's roughly balanced. Asymmetric partnerships die — both sides must win clearly.\n\n**Deal structure.** Define: what each side contributes (audience, product, budget, effort), what each side gets (leads, revenue, brand), exclusivity (rarely wise), term and renewal, IP and brand usage, data sharing rules, and exit clauses. Put it in writing — even \"simple\" partnerships.\n\n**Co-marketing plays.** Joint webinars, co-branded content\u002Fguides, integration announcements, shared booths at events, newsletter swaps, bundled offers. Each needs: shared goal, agreed promotion commitments from both sides, and lead-sharing rules.\n\n**Partner enablement.** Partners sell you only if it's easy: one-pagers, pitch decks, demo environments, deal registration, training, and a responsive contact. Treat partners like a sales channel that needs enablement.\n\n**Relationship management.** Executive sponsor on both sides, quarterly business reviews, shared dashboards, joint planning. Partnerships decay without active management — assign an owner.\n\n\n**Partnership types.** Technology (integrations, APIs), channel (resellers, distributors), strategic alliances (joint GTM), content (co-marketing), and referral.\nEach type needs different agreements, metrics, and management rhythms — do not manage them identically.\nStart with the type matching your biggest gap (distribution? credibility? capability?).\n**Partner lifecycle.** Recruit → onboard → activate (first joint win) → grow (expand scope) → optimize or exit.\nMost partnerships die between onboard and activate — the first joint win is the critical milestone.\nDesign onboarding around reaching that first win in 90 days.\n**Co-selling motions.** Joint account planning, warm introductions, coordinated outreach, and shared deal support.\nCo-selling needs: clear rules of engagement, shared CRM visibility, and joint pipeline reviews.\nWithout operational integration, \"strategic partnerships\" remain press releases.\n## Practical workflow\n\n1. **Define partnership goals.** Distribution? Credibility? Product capability? Set targets (leads, revenue, integrations shipped).\n2. **Build the target list.** Map your ecosystem: who shares your buyers? Score candidates on audience overlap, brand fit, and likelihood to engage. Prioritize 10–20.\n3. **Outreach with a specific idea.** Don't pitch \"let's partner\" — pitch a concrete joint initiative (webinar, integration, co-branded guide). Specificity gets replies; vagueness gets ignored.\n4. **Structure the deal.** Negotiate contributions and benefits explicitly. Document in a partnership agreement or MOU. Agree on promotion commitments (e.g., \"two emails to 50k list\") — vague promises produce vague results.\n5. **Launch jointly.** Coordinate announcements, run the co-marketing play, enable their team, track shared metrics in one dashboard both sides see.\n6. **Manage and expand.** Quarterly reviews: what worked, pipeline generated, next initiatives. Double down on winners; sunset partnerships where effort exceeds return. Turn great partners into case studies that attract more partners.\n\n**Partnership one-pager:** partner profile → why now → joint value proposition → proposed initiative → each side's commitments → success metrics → timeline → owner.\n\n\n**Partner tiering:** strategic (joint roadmap, executive sponsors, co-selling) → growth (co-marketing, referral motions) → long-tail (self-serve referral links, minimal touch). Allocate your time 50\u002F30\u002F20 across tiers. Review tiering quarterly — partners migrate as they prove out or fade.\n\n**Partner launch package:** co-branded one-pager, joint solution brief, referral process doc (how leads are passed and tracked), SPIF\u002Fincentive terms, 30-60-90 day joint plan with named owners on both sides, and a shared Slack channel. Partnerships without a launch package drift into logo-swaps.\n\n**Partner business plan (annual):** joint objectives → target accounts\u002Fsegments → planned activities by quarter → investment from each side → pipeline and revenue targets → governance (QBR cadence, executive sponsors).\nBoth sides sign — mutual commitment separates real partnerships from logo swaps.\n**Conflict resolution:** documented escalation path → 48-hour resolution SLA → executive sponsor involvement for strategic partners → termination clauses for repeated violations.\nAddress conflicts immediately; festering disputes kill partnerships slowly.\n## Common pitfalls\n\n- **Vague agreements.** \"Let's collaborate\" with no defined commitments. Specificity or nothing.\n- **Asymmetric value.** One side does all the work. Partnerships need balanced give-and-get.\n- **No owner.** Partnerships managed by \"everyone\" are managed by no one. Assign one owner per partner.\n- **Logo-slide partnerships.** Announced with fanfare, never activated. Launch with a real joint initiative.\n- **Ignoring small partners.** Chasing only big logos while nimble smaller partners drive actual pipeline. Portfolio approach.\n- **No exit criteria.** Keeping zombie partnerships alive out of politeness. Review quarterly; sunset the duds.\n- **Partner conflict.** Overlapping partners competing for the same deals. Define territories\u002Frules of engagement upfront.\n- **Partnerships without pipeline targets.** Activity (meetings, MOUs) mistaken for progress. Every partnership gets a pipeline goal and a review date — kill or fix those that miss twice.\n- **Single-threaded relationships.** One champion each side. When they leave, the partnership dies. Build multi-threaded connections from day one.\n- **Partner quantity over quality.** Dozens of inactive partnerships. Five active partnerships beat fifty logos — prune annually.\n- **Asymmetric investment.** You invest heavily; they do nothing. Require reciprocal commitments upfront; measure both sides quarterly.\n- **Messy exits.** Partnerships fading without closure. Formal sunsets protect relationships and reputations.\n- **No success metrics.** Partnerships without KPIs drift. Define success upfront; review quarterly.\n",{"name":5,"category":24,"description":7},"business-marketing","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-partnership-manager",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill partnership-manager",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill partnership-manager",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill partnership-manager","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-partnership-manager\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]