Gtm Board And Investor Communication
github/awesome-copilot
Board meeting preparation, investor updates, and executive communication.
World-Class Partnerships & Ecosystem Playbook. An agent skill from LeoYeAI/openclaw-master-skills.
Install Partnerships Ecosystem
$ npx skills add LeoYeAI/openclaw-master-skills --skill partnerships-ecosystem -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills partnerships-ecosystem --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/partnerships-ecosystem .claude/skills/partnerships-ecosystem && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "partnerships-ecosystem" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/partnerships-ecosystem into .claude/skills/partnerships-ecosystem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "partnerships-ecosystem", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/partnerships-ecosystemType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add LeoYeAI/openclaw-master-skills --skill partnerships-ecosystem -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills partnerships-ecosystem --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/partnerships-ecosystem .agents/skills/partnerships-ecosystem && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "partnerships-ecosystem" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/partnerships-ecosystem into .agents/skills/partnerships-ecosystem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "partnerships-ecosystem", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill partnerships-ecosystem -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills partnerships-ecosystem --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/partnerships-ecosystem .cursor/skills/partnerships-ecosystem && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "partnerships-ecosystem" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/partnerships-ecosystem into .cursor/skills/partnerships-ecosystem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "partnerships-ecosystem", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/LeoYeAI/openclaw-master-skills.git --path skills/partnerships-ecosystem--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add LeoYeAI/openclaw-master-skills --skill partnerships-ecosystem -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills partnerships-ecosystem --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/partnerships-ecosystem .gemini/skills/partnerships-ecosystem && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "partnerships-ecosystem" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/partnerships-ecosystem into .gemini/skills/partnerships-ecosystem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "partnerships-ecosystem", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install LeoYeAI/openclaw-master-skills partnerships-ecosystemInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add LeoYeAI/openclaw-master-skills --skill partnerships-ecosystem -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/partnerships-ecosystem .github/skills/partnerships-ecosystem && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "partnerships-ecosystem" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/partnerships-ecosystem into .github/skills/partnerships-ecosystem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "partnerships-ecosystem", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill partnerships-ecosystem -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills partnerships-ecosystem --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/partnerships-ecosystem .opencode/skills/partnerships-ecosystem && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "partnerships-ecosystem" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/partnerships-ecosystem into .opencode/skills/partnerships-ecosystem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "partnerships-ecosystem", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
partnerships-ecosystem- GitHub stars
- 2.2k
- Token cost
- ~5k tokens
- SKILL.md length
- 2,132 words
- Files
- 3 (incl. references)
- Skills in repo
- 1,235
- Repo updated
- First seen
- Licence
- MIT
At a glance
World-Class Partnerships & Ecosystem Playbook. An agent skill from LeoYeAI/openclaw-master-skills.
- Works in 12 steps: The Partnership Hierarchy (Priority Order) → The Four Pillars (Non-Negotiable) → Partnership Types & When to Use Each → …
- : strategic alliances
- SKILL.md covers Core Philosophy, 1. The Partnership Hierarchy…, 2. The Four Pillars… and 3. Partnership Types & When to…, plus 10 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Partnerships Ecosystem is an agent skill from LeoYeAI/openclaw-master-skills. World-Class Partnerships & Ecosystem Playbook. Use for: strategic alliances, joint ventures, channel partner management, partner tiering, co-marketing, co-selling, ecosystem-led growth (ELG), ecosystem mapping, supplier relationships, industry networking, partnership governance, joint business plans (JBPs), QBRs, deal registration, partner enablement, MDF allocation, partnership legal frameworks (NDAs, MOUs, JV agreements), commercial models (revenue share, referral fees, reseller margins, licensing), partnership…
Its SKILL.md is about 5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `README.md` and `references/extended-frameworks.md`).
It sits in Business, Finance & HR, covering OKRs and executive reporting, Startup and business strategy and Go-to-market strategy. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.
When your agent uses it
- : strategic alliances
- Channel partner management
- Partner tiering
- Ecosystem-led growth (ELG)
Example prompts
- “/partnerships-ecosystem”
Workflow steps
12 steps, taken from the step headings in SKILL.md.
- The Partnership Hierarchy (Priority Order)
- The Four Pillars (Non-Negotiable)
- Partnership Types & When to Use Each
- Strategic Alliance Lifecycle
- Strategic Fit Assessment (Score 1–5 Per Dimension)
- Channel Partner Programme
- Partnership KPIs & Metrics
- Joint Ventures — Decision Framework
- Ecosystem-Led Growth (ELG)
- Co-Marketing Framework
- Supplier Relationship Management
- Legal & Commercial Frameworks
What it can do on your machine
Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Partnerships Ecosystem loads about 5k tokens when it runs, and up to ~6.8k if it reads all its reference files. Until then it costs about 227 tokens; SKILL.md has 2,132 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 2,132 words, ~4,992 tokens.
Download SKILL.mdSave it as
.claude/skills/partnerships-ecosystem/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- partnerships-ecosystem
- description
- World-Class Partnerships & Ecosystem Playbook. Use for: strategic alliances, joint ventures, channel partner management, partner tiering, co-marketing, co-selling, ecosystem-led growth (ELG), ecosystem mapping, supplier relationships, industry networking, partnership governance, joint business plans (JBPs), QBRs, deal registration, partner enablement, MDF allocation, partnership legal frameworks (NDAs, MOUs, JV agreements), commercial models (revenue share, referral fees, reseller margins, licensing), partnership KPIs, partner onboarding, RACI matrices, co-innovation, marketplace strategy, platform ecosystems, API partner programmes, and anti-patterns. Trigger when discussing ANY partnership, alliance, channel, ecosystem, co-marketing, supplier, or business development topic. Also trigger for GTM strategy involving partners or indirect sales. If in doubt, use this skill.
World-Class Partnerships & Ecosystem Playbook
You are operating as a world-class partnerships strategist and advisor. Every piece of advice must meet the standard of professional partnership management — strategically sound, commercially precise, and grounded in real-world execution experience. No fluff. No generic advice.
Core Philosophy
PARTNERSHIPS ARE NOT A DEPARTMENT — THEY ARE A DISCIPLINE.You are an ecosystem architect, not just a deal-maker. The agreement is just the beginning.
1. The Partnership Hierarchy (Priority Order)
Every partnership decision should be evaluated against this hierarchy:
- Mutual Value Creation — The #1 principle. Every partnership must produce measurable value for both parties. One-sided relationships collapse.
- Strategic Alignment — Shared vision, complementary capabilities, overlapping ICP. Without alignment, execution is futile.
- Governance & Accountability — Decision rights, escalation paths, cadenced reviews. Structure is liberation, not control.
- Operational Excellence — RACI clarity, joint business plans, enablement, deal registration. Strategy without execution is fantasy.
- Ecosystem Mindset — You are simultaneously a hub AND a spoke. Your partners have their own ecosystems. Network effects compound.
- Transparency as Default — Share goals, constraints, roadmaps, performance data openly. Information asymmetry kills partnerships.
- Long-Term Orientation — Optimise for compounding trust, not quick wins.
- Measured Outcomes — Leading + lagging indicators. If you can't measure it, you can't improve it.
2. The Four Pillars (Non-Negotiable)
Every successful partnership rests on four pillars. If any is weak, the partnership fails.
| Pillar | Definition | Failure Mode |
|---|---|---|
| Mutually Beneficial Economics | Clear, agreed model for how value flows | Hidden agendas, one party subsidising |
| Robust Governance | Decision protocols, steering committees, cadences | Drift, stagnation, decision paralysis |
| Shared Core Values | Aligned ethics, quality standards, cultural fit | Cultural friction, broken trust |
| Rigorous Engagement Model | Defined RACI, resource commitments, accountability | Unclear ownership, finger-pointing |
3. Partnership Types & When to Use Each
| Type | Use When | Complexity | Commitment |
|---|---|---|---|
| Referral / Affiliate | Introductions only; testing partner fit | Low | Low |
| Co-Marketing | Joint demand generation; audience expansion | Low–Med | Medium |
| Channel / Reseller | Scaling distribution via third-party sales | Medium | Medium |
| Technology / Integration | Products complement each other; shared customers | Medium | Medium–High |
| Strategic Alliance | Deep collaboration; shared resources; joint innovation | High | High |
| Joint Venture | Separate entity needed; shared equity; regulated market entry | Very High | Very High |
| Platform Ecosystem | API-first; third-party developers extend your product | High | Long-term |
4. Strategic Alliance Lifecycle
| Phase | Duration | Key Activities | Deliverables |
|---|---|---|---|
| 1. Discovery & Scouting | Ongoing | Scan ecosystems, monitor competitor alliances, attend events | Partner prospect pipeline |
| 2. Due Diligence | 4–12 weeks | Strategic fit assessment, capability audit, cultural review | DD report, go/no-go |
| 3. Structuring | 2–8 weeks | Define economics, governance, RACI, IP, exit clauses | Alliance charter, MOU, JBP |
| 4. Launch & Activation | 4–12 weeks | Internal enablement, joint press, pilot campaign | Launch plan, first pipeline |
| 5. Operate & Scale | Ongoing | QBRs, pipeline mgmt, co-selling, joint product dev | QBR decks, revenue reports |
| 6. Renew or Exit | Annual review | Performance vs JBP, relationship health, strategic relevance | Renewal or exit plan |
5. Strategic Fit Assessment (Score 1–5 Per Dimension)
| Dimension | Evaluate | Weight |
|---|---|---|
| Market Alignment | Overlapping ICP, complementary geos, shared segments | High |
| Capability Complement | Skills, tech, or IP filling a genuine gap | High |
| Cultural Compatibility | Decision speed, risk appetite, communication style | Medium |
| Financial Health | Revenue stability, funding runway, co-investment willingness | Medium |
| Strategic Intent | Long-term vision alignment, resource commitment | High |
Score 20+ = strong candidate. 15–19 = investigate further. <15 = deprioritise.
6. Channel Partner Programme
The Four Ps of Partner Ecosystem Success
- Product — Partner-ready: APIs, docs, sandbox, integration guides
- Programme — Tiers, incentives, enablement, compliance, support
- Partners — Deliberate recruitment, qualification, segmentation
- People — Internal team: partner managers, channel marketing, enablement
Partner Tiering Model
| Tier | Criteria | Benefits | Obligations |
|---|---|---|---|
| Platinum / Elite | Top 5–10% revenue, deep certification, co-sell commitment | Highest MDF, exec sponsor, priority leads, co-branded content | QBRs, certified staff, pipeline commitments |
| Gold | Consistent revenue, moderate cert, active pipeline | Moderate MDF, deal reg priority, joint webinars, dedicated PM | Monthly reporting, training targets |
| Silver | Early-stage, exploring fit, growing pipeline | Self-service portal, standard commission, marketing templates | Annual agreement, basic cert, brand compliance |
| Referral / Affiliate | Introductions only | Referral fee / rev share, directory listing | Valid referrals, compliance with terms |
Partner Lifecycle
- Recruitment & Qualification — Define Ideal Partner Profile (IPP). Score prospects before onboarding.
- Onboarding (First 90 Days) — Welcome kit, certification path (30/60/90 milestones), portal access, assigned PM, first joint campaign within 60 days.
- Enablement — Multi-format: e-learning, live training, sandbox, sales playbooks, certifications.
- Performance Management — Scorecard combining leading indicators (training, portal logins, deal regs) with lagging (revenue, close rate, CSAT). Invest in top performers; exit underperformers.
7. Partnership KPIs & Metrics
Leading Indicators (Forward-Looking)
| KPI | What It Measures |
|---|---|
| Training completion rate | Partner competency and commitment |
| Portal login frequency | Mindshare and programme stickiness |
| Deal registrations per partner | Future revenue signal |
| Partner activation rate (within 90 days) | Onboarding quality |
Lagging Indicators (Results)
| KPI | What It Measures |
|---|---|
| Partner-sourced revenue (% of total) | Channel contribution to business |
| Partner-influenced pipeline | Deals where partners contributed |
| Average deal size (partner vs direct) | Partner quality and positioning |
| Co-sell win rate | Effectiveness of joint selling |
| Partner attrition rate (annual) | Programme / relationship problems |
| Partner Lifetime Value (PLV) | Cumulative long-term value |
| NPS / CSAT (partner-delivered customers) | Brand quality maintenance |
| Customer retention (partner channel) | Post-sale support quality |
Critical Rule: Never measure only lagging indicators. By the time revenue shows a problem, it's too late. Balance with leading indicators for 60–90 day forward visibility.
8. Joint Ventures — Decision Framework
Use a JV only when:
- Dedicated, ring-fenced capital investment is required
- Shared equity is necessary for long-term incentive alignment
- Target market requires local legal entity for regulatory compliance
- The venture needs its own brand, team, and operational independence
If all answers are "no" — use a lighter structure (alliance, rev-share, licensing).
JV Structuring Essentials
| Element | Best Practice |
|---|---|
| Ownership Split | Based on contribution. Avoid 50/50 without deadlock resolution. |
| Governance | Board with clear voting, deadlock mechanisms, reserved matters |
| Funding | Initial cap, call-for-capital, dilution consequences |
| IP | What each party contributes; who owns new IP; licensing on dissolution |
| Exit | Tag-along, drag-along, buy-sell, put/call provisions |
| Reporting | Monthly financials, quarterly board, annual audit, real-time dashboards |
9. Ecosystem-Led Growth (ELG)
ELG treats your partner ecosystem as the primary engine for customer acquisition, conversion, and expansion. Unlike direct sales, ELG scales exponentially through network effects.
Ecosystem Maturity Model
| Stage | Partners | Partner Revenue % | Focus |
|---|---|---|---|
| 1. Foundation | <5 | <5% | Strategy, first partner lead, 3–5 high-potential partners |
| 2. Emerging | 5–15 | 5–15% | Formalise tiering, enablement, deal reg, QBR cadence |
| 3. Scaling | 15–50 | 15–30% | Automate ops, marketplace listings, co-sell playbooks, PRM |
| 4. Optimised | 50+ | 30–50% | Multi-partner plays, ecosystem intelligence, advisory board, EQLs |
| 5. Ecosystem-Led | 100+ | 50%+ | Platform ecosystem, API-first enablement, ecosystem fund |
Ecosystem Flywheel
- Attract — Clear value prop, low-friction onboarding, visible success stories
- Enable — Training, tools, content, co-selling support
- Activate — Joint pipeline via co-marketing, co-selling, marketplace listings
- Amplify — Celebrate wins publicly, share ecosystem data, multi-partner plays
10. Co-Marketing Framework
Campaign Steps
- Partner Selection — Brand credibility, complementary product, engaged audience, reliable team
- Joint Value Proposition — Why customers care about the combined offering; not just two logos
- Campaign Planning — Shared goals, target audience, tactics, responsibilities, timeline, budget/MDF
- Lead Management — Agree capture, scoring, distribution, SLAs, attribution, CRM handoff upfront
- Measurement — Awareness (impressions, engagement), Demand (leads, MQLs, CPL), Revenue (pipeline, closed-won), Efficiency (MDF ROI)
Co-Marketing Tactics Menu
| Tactic | Effort | Impact | Best For |
|---|---|---|---|
| Joint webinar | Medium | High | Lead gen, thought leadership |
| Co-authored content | Low–Med | Medium | SEO, credibility |
| Joint case study | Medium | High | Bottom-of-funnel proof |
| Co-branded landing page | Low | Medium | Campaign hub, lead capture |
| Joint conference slot | High | High | Executive visibility |
| Integrated product demo | Med–High | High | Technical audiences |
| Co-sponsored research | High | Very High | Industry authority |
Quick Win Rule: Always start a new co-marketing partnership with a single pilot campaign. Test working rhythms before committing to larger programmes.
11. Supplier Relationship Management
Supplier Segmentation (Kraljic Matrix)
| Segment | Spend | Strategic Importance | Approach |
|---|---|---|---|
| Strategic | High | High | Deep partnership, joint innovation, multi-year contracts |
| Leverage | High | Low | Competitive bidding, cost optimisation, SLA enforcement |
| Bottleneck | Low | High | Risk mitigation, diversification, relationship investment |
| Routine | Low | Low | Automate procurement, standardise contracts |
Show full SKILL.md (854 more words)Show less
Key Practices
- Joint Business Planning with strategic suppliers (shared KPIs, innovation targets)
- Supplier Scorecards quarterly (quality, delivery, cost, responsiveness, innovation)
- Risk Register (financial health, geographic concentration, single-source deps, regulatory exposure)
- Innovation Collaboration (invite strategic suppliers into product development)
- Multi-jurisdictional compliance framework mapping suppliers to regulations per jurisdiction
12. Legal & Commercial Frameworks
Agreement Types
| Agreement | Use Case |
|---|---|
| NDA | Pre-engagement confidentiality |
| MOU | Non-binding framework for exploration |
| Alliance Agreement | Formalised strategic alliance (scope, economics, governance, IP, term) |
| Channel Partner Agreement | Reseller/distributor/referral terms (territory, pricing, SLAs) |
| JV Agreement | Separate entity (equity, board, capital, IP, exit, deadlock) |
| Co-Marketing Agreement | Joint campaigns (responsibilities, leads, brand, costs, measurement) |
| Supplier Agreement | Upstream procurement (specs, pricing, payment, warranties, liability) |
Commercial Models
| Model | Best For |
|---|---|
| Revenue Share | SaaS, marketplace, platform ecosystems |
| Referral Fee | Low-touch, advisory relationships |
| Reseller Margin | Channel distribution, geographic expansion |
| Joint Investment | Strategic alliances, co-innovation |
| MDF / Co-op Funds | Channel marketing, co-marketing campaigns |
| Licensing | Technology partnerships, white-label |
| Equity / Token Swap | Deep alliances, Web3 ecosystems |
Negotiation Principles
- Anchor to value — Frame terms around value created, not cost/effort
- Build in flexibility — Annual reviews, performance-based adjustments, change-of-scope provisions
- Protect downside — Termination for convenience, IP reversion, data return obligations
- Speed to signature — Modular templates with standard terms + deal-specific schedule. Over-lawyered = dead
13. Governance Model (Three Layers)
| Layer | Cadence | Who | Purpose |
|---|---|---|---|
| Executive Sponsors | Quarterly | C-level / VP | Strategic direction, blockers, major investments |
| Joint Steering Committee | Monthly | Senior managers | Pipeline review, campaigns, escalations, JBP alignment |
| Working Groups | Weekly/Biweekly | Functional leads | Day-to-day execution across sales, marketing, product |
Each layer needs a written charter: membership, decision rights, meeting cadence, escalation triggers.
14. Industry Networking
Networking as a System
- Contact Database — Structured DB with conversation history, interests, next actions (Notion, Airtable, CRM)
- Touchpoint Cadence — Monthly (inner circle), quarterly (wider network), biannually (dormant)
- Value-First Principle — Lead with value: introductions, articles, feedback, invitations. Never reach out only when you need something.
- Follow-Up Discipline — Within 48 hours. Second touchpoint within 30 days. The event is the beginning.
- Annual Relationship Audit — Identify gaps, dormant high-value relationships, over-indexed areas
Networking Channels
| Channel | Top Tactics |
|---|---|
| Conferences | Speaking slots, curated side meetings, after-event dinners |
| Associations | Committee leadership, content contribution, award nominations |
| Accelerators | Mentorship, demo days, investor introductions |
| Online Communities | LinkedIn/X thought leadership, Slack/Discord, podcast guesting |
| Hackathons | Participation, sponsorship, judging |
| Advisory Boards | Join/form with complementary leaders |
| Investor Networks | Demo days, syndicate participation, deal partner roles |
Say less than necessary. Listen more. Ask questions. Offer specific help. Relationships endure on curiosity and delivered value, not volume of words.
15. Anti-Patterns (What Not to Do)
| Anti-Pattern | Symptom | Fix |
|---|---|---|
| Logo Collecting | Many partners, zero activation | Set activation thresholds before signing |
| Press Release Partnership | Big announcement, no follow-through | Never announce without 90-day activation plan |
| Founder-to-Founder Only | Collapses when one person leaves | Multi-thread: 3+ people from each side engaged |
| One-Sided Value | Partner disengages over time | Annual value exchange audit; rebalance or exit |
| Governance Theatre | QBRs happen but nothing changes | Tie governance to JBP execution; independent owner |
| Channel Conflict Avoidance | Direct and channel competing silently | Clear rules of engagement, deal reg priority |
| Over-Engineering Agreements | 6+ months to sign; momentum dies | Modular templates; start with MOU for pilots |
| Measuring Activity Not Outcomes | Tracking webinars, not revenue | Metrics hierarchy: activity → pipeline → revenue |
16. Implementation Roadmap
| Phase | Months | Actions |
|---|---|---|
| Foundation | 1–3 | Audit existing partnerships, define ecosystem strategy, create IPP, draft legal templates, build basic portal, approach 3–5 partners, assign ownership |
| Build | 4–6 | Formalise JBPs for top 3, launch first co-marketing pilot, implement deal reg in CRM, design tiering/enablement, establish QBR cadence |
| Scale | 7–12 | Expand to 10–15 partners, launch enablement content, implement PRM, build co-sell playbooks, create metrics dashboard, run first partner satisfaction survey |
| Optimise | 13–18 | Multi-partner plays, EQLs, partner advisory board, automated lifecycle workflows, marketplace presence, set partner revenue % target |
17. Essential Templates
Joint Business Plan (JBP) — Must Include:
- Partnership Vision (2–3 sentences, 12-month horizon)
- Shared Goals (3–5 measurable objectives with owners and deadlines)
- Target Customers (ICP segments, named accounts if applicable)
- GTM Motions (co-selling, co-marketing, enablement plays)
- Resource Commitments (headcount, budget, exec time, tech)
- Governance (cadence, escalation, decision rights)
- Success Metrics (KPIs with baselines, targets, review frequency)
- Risk Register (top 5 risks with mitigations and owners)
QBR Agenda (80 Minutes)
- Partnership Health Check (10 min) — Relationship score, governance adherence, open issues
- Performance Review (20 min) — Pipeline, revenue, KPIs vs JBP targets
- Customer Wins & Learnings (15 min) — Case studies, feedback, competitive insights
- Co-Marketing Review (10 min) — Campaign results, upcoming plans
- Strategic Alignment (15 min) — Market changes, roadmap updates, strategic pivots
- Action Items & Next Quarter (10 min) — Commitments, owners, deadlines
Partner Evaluation Scorecard
| Criteria | Weight | Score (1–5) |
|---|---|---|
| Market alignment with ICP | 20% | ___ |
| Complementary capabilities | 20% | ___ |
| Cultural and values fit | 15% | ___ |
| Financial stability / runway | 10% | ___ |
| Technical integration readiness | 15% | ___ |
| Executive sponsorship commitment | 10% | ___ |
| Existing customer overlap | 10% | ___ |
Recommended Tech Stack
| Function | Tools |
|---|---|
| PRM | Impartner, Allbound, PartnerStack, Crossbeam |
| Co-Selling & Pipeline | Crossbeam, Reveal, Tackle.io |
| Co-Marketing Automation | Impartner PMA, WorkSpan, Kiflo |
| CRM Integration | Salesforce Partner Cloud, HubSpot Partner Hub |
| Communication | Slack Connect, MS Teams shared channels |
| Analytics | Tableau, Looker, built-in PRM analytics |
| LMS | Skilljar, Docebo, Thought Industries |
| Contract Management | DocuSign CLM, Ironclad, PandaDoc |
Remember: Start with three partners. Go deep, not wide. Prove the model. Measure everything. Then scale relentlessly. Partnerships compound — treat every interaction as a long-term investment.
BUILD – DOCUMENT – RESEARCH – LEARN – REPEAT© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in skills/partnerships-ecosystem of LeoYeAI/openclaw-master-skills.
- SKILL.md
- README.md
- references/extended-frameworks.md
Open the folder on GitHubat commit e5199b5
Compare with similar skills
Partnerships Ecosystem next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Partnerships Ecosystem this skillLeoYeAI/openclaw-master-skills | 2.2k | — | ~5k | Automated safety check: Pass | MIT | |
| Gtm Board And Investor Communicationgithub/awesome-copilot | 40k | 1 repos | ~4.7k | Automated safety check: Pass | MIT | |
| Strategy Frameworksmagnus919/hermes-profiles | 289 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Security Commsbriiirussell/cybersecurity-skills | 413 | — | ~3.8k | Automated safety check: Pass | MIT | |
| Product Strategistdavila7/claude-code-templates | 33k | 3 repos | ~248 | Automated safety check: Pass | MIT | |
| Marketingzeuikli/claude-code-workspace | 156 | — | ~461 | Automated safety check: Pass | None |
Similar skills
- Official
Strategy Frameworks
magnus919/hermes-profiles
CEO methodology for strategic planning, competitive analysis, growth strategy, and resource allocation.
Security Comms
briiirussell/cybersecurity-skills
Translate technical security work into the language of non-security audiences — board, executives, engineering, customer success, customers, legal, procurement, sales.
Product Strategist
davila7/claude-code-templates
Strategic product leadership toolkit for Head of Product including OKR cascade generation, market analysis, vision setting, and team scaling.
Marketing
zeuikli/claude-code-workspace
行銷策略全流程：受眾分析、GTM 規劃、A/B 測試設計、KPI 設定、競品定位。適合在規劃行銷活動、制定上市策略、或設計成長實驗時使用。
Process Mapper
alirezarezvani/claude-skills
A skill your agent uses when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff…
More from LeoYeAI/openclaw-master-skills
All 1,200 skills in this repoDevOps Pipeline Management
LeoYeAI/openclaw-master-skills
Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.
Feishu Document Collaboration
LeoYeAI/openclaw-master-skills
Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.
Files Memory System
LeoYeAI/openclaw-master-skills
Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.
GEO-Claw AI Visibility Agent
LeoYeAI/openclaw-master-skills
Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.
Google Workspace CLI
LeoYeAI/openclaw-master-skills
Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.
HealthFit Health Advisors
LeoYeAI/openclaw-master-skills
Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.
Related
Questions about Partnerships Ecosystem
What does Partnerships Ecosystem do?
World-Class Partnerships & Ecosystem Playbook. An agent skill from LeoYeAI/openclaw-master-skills. Partnerships Ecosystem is an agent skill from LeoYeAI/openclaw-master-skills. World-Class Partnerships & Ecosystem Playbook.
When should I use Partnerships Ecosystem?
Partnerships Ecosystem fits situations like: : strategic alliances; channel partner management; partner tiering; ecosystem-led growth (ELG).
How do I install Partnerships Ecosystem in Claude Code?
Run `npx skills add LeoYeAI/openclaw-master-skills --skill partnerships-ecosystem -a claude-code`. Or copy the skill folder (skills/partnerships-ecosystem in LeoYeAI/openclaw-master-skills) into .claude/skills/partnerships-ecosystem in your project. Claude Code loads it when a task matches its description.
How do I install Partnerships Ecosystem in Codex?
Run `npx skills add LeoYeAI/openclaw-master-skills --skill partnerships-ecosystem -a codex`. Or copy the skill folder (skills/partnerships-ecosystem in LeoYeAI/openclaw-master-skills) into .agents/skills/partnerships-ecosystem in your project. Codex loads it when a task matches its description.
Can I use Partnerships Ecosystem in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill partnerships-ecosystem -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/partnerships-ecosystem, .gemini/skills/partnerships-ecosystem, .github/skills/partnerships-ecosystem and .opencode/skills/partnerships-ecosystem in your project.
What does Partnerships Ecosystem need to run?
SKILL.md names no scripts, command-line tools or credentials: Partnerships Ecosystem is instructions for the agent only.
Does Partnerships Ecosystem access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Partnerships Ecosystem safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Partnerships Ecosystem use?
Partnerships Ecosystem is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Partnerships Ecosystem use?
About 5k tokens (SKILL.md is roughly 20k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.8k tokens, read only when the agent opens those files.
What are the alternatives to Partnerships Ecosystem?
Skills that share tags, products or a category with Partnerships Ecosystem: Gtm Board And Investor Communication (github/awesome-copilot, 40k stars), Strategy Frameworks (magnus919/hermes-profiles, 289 stars), Security Comms (briiirussell/cybersecurity-skills, 413 stars) and Product Strategist (davila7/claude-code-templates, 33k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Partnerships Ecosystem?
LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,161 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.
Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.