Agent skill
partner-blueprint
Partner and channel strategy architect that identifies, scores, and structures partnerships with mutual value propositions and co-GTM plans.
Filed under Partnerships and channel.
From varunk130/ai-gtm-skill-library · 31 skills · 5 · pushed 2026-07-31
What it does when it runs
Partner and channel strategy architect that identifies, scores, and structures partnerships with mutual value propositions and co-GTM plans. Use when: partner strategy, channel partners, partnership, co-marketing, reseller strategy, integration partners, ecosystem strategy.
Read from the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/varunk130/ai-gtm-skill-library.git /tmp/ai-gtm-skill-library git -C /tmp/ai-gtm-skill-library sparse-checkout set "gtm-skills/partner-blueprint" mkdir -p ~/.claude/skills/partner-blueprint cp -R "/tmp/ai-gtm-skill-library/gtm-skills/partner-blueprint/." ~/.claude/skills/partner-blueprint/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from varunk130/ai-gtm-skill-library/blob/90e878c73a8fbfd1cab864424ccf674fdc889157/gtm-skills/partner-blueprint/SKILL.md, which is licensed MIT (repository). 531 words, 11 headings.
Partner Blueprint (BRIDGE Framework)
Engineer partnership strategy from identification through activation. Partnerships are a multiplier, not just a channel.
When to Use
- Building partner/channel program from scratch
- Evaluating specific partnership opportunity
- Designing co-GTM with existing partner
- Expanding into new geography via partners
- Platform/ecosystem strategy
What You'll Need
Critical inputs (ask if not provided):
- Your product and target market
- Partnership goals (reach, credibility, technology, revenue)
- Current partner landscape (if any)
Nice-to-have:
- Battle Scanner output (competitor partnerships to counter)
- Market Analyzer output (segments needing partner reach)
Process
Step 1: Partner Landscape Mapping
Identify candidates across 6 categories:
| Category | What They Offer | Examples |
|---|---|---|
| Technology | Integrations, platform plays | CRM, cloud providers, data platforms |
| Channel/Reseller | Reach into new segments/geos | VARs, MSPs, regional resellers |
| Co-marketing | Audience sharing, content collab | Complementary SaaS, media partners |
| Implementation | Consulting, deployment, training | SIs, boutique consultancies |
| Strategic/OEM | Embedded, white-label | Enterprise platforms, industry solutions |
| Community/Ecosystem | Developer communities, associations | Open-source projects, industry groups |
Step 2: BRIDGE Scoring (per partner candidate, 1-10 each)
| Dimension | What It Measures | Scoring Guide |
|---|---|---|
| Business-fit | Strategic alignment of customers and goals | 1=no overlap, 5=partial, 10=perfect alignment |
| Reach | Incremental access to markets you cannot reach alone | 1=same audience, 5=some new, 10=opens new markets |
| Investment | Required time, money, engineering (inverse) | 1=massive investment, 5=moderate, 10=minimal |
| Dependencies | Risk of dependency (inverse) | 1=total dependency, 5=balanced, 10=no risk |
| Growth-potential | Can this scale? Network effects? | 1=one-time, 5=linear growth, 10=exponential |
| Execution-readiness | Team, processes, motivation to execute now | 1=not ready, 5=needs work, 10=ready to go |
BRIDGE Score = (B x 0.20) + (R x 0.20) + (I x 0.15) + (D x 0.10) + (G x 0.20) + (E x 0.15)
- 7.5+ = Activate (pursue immediately)
- 5.0-7.4 = Develop (invest in relationship, plan for future)
- Below 5.0 = Monitor (not worth active investment now)
Step 3: Mutual Value Proposition Design
For each Activate partner:
- What they get: Technology, content, brand association, revenue share
- What we get: Distribution, credibility, access, technology
- Joint customer value: Why is 1+1 > 2?
- Revenue model: Referral fee, rev share, co-sell, embed, marketplace
Step 4: Co-GTM Plan Template
For each activated partner:
- Joint messaging and positioning
- Co-marketing activities (webinars, content, events)
- Technical integration roadmap
- Sales handoff process and rules of engagement
- Success metrics and review cadence (monthly/quarterly)
Output
Save to outputs/partner-blueprint-[YYYY-MM-DD].md
Deliverables:
- Partner Landscape Map: Categorized candidates with BRIDGE scores
- Partner Scorecards: Detailed assessment per top-10 candidates
- Mutual Value Propositions: Value exchange documents per partner
- Co-GTM Playbooks: Joint go-to-market plans for activated partners
Chain Connections
- Next skill: Run
community-catalystto design PLG and community programs - Also feeds:
launch-command(partner readiness is a launch gate),demand-engine(co-marketing expands channels) - Enhanced by: Run after
battle-scanner(competitive landscape reveals partnership opportunities)
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- partner-affiliate by chadboyda · 74
- partner-channel-operations by NEON-Rutger · 45
- partner-ecosystem-architect by NEON-Rutger · 45
- partner-enablement by jbalbu01 · 14
- frontiergtm-agent-blueprint by frontiergtm · 0
Need help setting it up?
This page tells you what partner-blueprint does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.