Skip to main content
skill CX Codex

partnerships-ops — Claude Code skill: features and install

The partnerships-ops Claude Code skill supports partner-program design and marketing through business partners. It activates for co-marketing, integration launches, marketplace listings, and channel sales work.

MIT ★ 43 updated 2026-11-16

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add shalintripathi/saas-marketing-agents --skill partnerships-ops -a claude-code
Open on GitHub

What partnerships-ops does

The skill routes requests to one of two specialist agents. One handles co-marketing, partner enablement, and cloud marketplace work; the other designs channel programs, partner economics, incentives, and rules for disputed deals. It also covers partner recruitment, certification, campaign planning, and choosing a partner motion.

Before drafting a deliverable, it checks the project root for brand-context.md and also looks in ./.claude/brand-context.md and ./docs/brand-context.md. When found, the file’s rules and verified claims go to the relevant specialist. If it is missing, the skill points to templates/brand-context.md and labels assumptions; unsupported claims are marked [NEEDS INPUT: …].

What it helps with

  • plan a co-marketing campaign with an integration partner
  • choose a channel motion and model partner economics
  • prepare an integration launch or AWS Marketplace listing
  • settle a deal conflict between a partner and direct sales

Example prompts for the agent

  • Plan a joint campaign with our integration partner.
  • Compare reseller economics with direct sales and draft rules for a disputed account.
  • Prepare an integration launch plan and partner materials.

How to install partnerships-ops

1Skills CLI (Vercel)

npx skills add shalintripathi/saas-marketing-agents --skill partnerships-ops -a claude-code

2Manually: put the files in place

~/.claude/skills/partnerships-ops/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/partnerships-ops/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about partnerships-ops

How do I install partnerships-ops in Claude Code?

Run npx skills add shalintripathi/saas-marketing-agents --skill partnerships-ops -a claude-code. The skill file is installed at ~/.claude/skills/partnerships-ops/SKILL.md.

What does partnerships-ops do?

It supports co-marketing and the design of partner and channel programs. Requests are routed to the specialist agent responsible for that work.

How does partnerships-ops use brand-context.md?

It checks the project root, ./.claude/, and ./docs/ for the file. Its rules and verified claims are passed to the specialist; if the file is missing, the skill points to a template and labels assumptions.

Source text

SKILL.md · MIT
---
name: partnerships-ops
description: "Partner, channel, and ecosystem marketing for B2B SaaS — and the design of the partner program itself. Use this skill for co-marketing with technology alliances and channel partners, integration launches, joint campaigns and content, partner tiering and enablement, cloud-marketplace go-to-market (AWS, Azure, GCP listings, private offers, committed-spend drawdown), and for channel program architecture: whether to launch a partner program at all, which motions to run (referral, technology, services/SI, reseller), partner unit economics, margin and SPIF design, partner recruitment and certification ramp, and the rules of engagement that settle a contested deal. Also triggers on: partner marketing, co-marketing, channel, reseller, VAR, MSP, distributor, OEM, alliance, ecosystem, integration launch, marketplace listing, AWS Marketplace, private offer, MDF, joint webinar, co-branded, channel conflict, rules of engagement, deal registration, partner program design, should we build a partner program, partner economics, partner P&L, partner CAC, margin stacking, SPIF, rebate, partner recruitment, partner onboarding, partner certification, partner tiers, our partners signed up and never sold anything."
---

# Partnerships Operations

## Step 0 (always first): Load brand context

**Before producing any deliverable, look for a `brand-context.md` file** in the user's project root (also check `./.claude/brand-context.md` and `./docs/brand-context.md`). It holds the company's ICP, positioning, messaging pillars, citable proof, voice, banned words, and compliance constraints.

- **If it exists:** read it in full and treat it as binding for this run. Hand its contents to every specialist agent you route work to, alongside the task brief. Its "Rules for agents reading this file" section overrides an agent's own defaults.
- **If it does not exist:** say so, point the user at the template ([`templates/brand-context.md`](../../templates/brand-context.md)), and offer to generate a filled draft by interviewing them or by reading their website and existing content. Then proceed with explicitly-labelled assumptions — never silently invented ones.

**Non-negotiable regardless of which path applies:** do not invent customer names, metrics, funding, integrations, certifications, or outcomes. Only proof recorded in `brand-context.md` (or supplied directly in the request) may be used as fact. Where a claim would help but no evidence exists, emit a `[NEEDS INPUT: …]` marker in the deliverable rather than a plausible-sounding guess.

---

## What This Is

Partnerships Operations markets *with and through other companies* rather than directly to buyers. It covers technology alliances and integrations, channel and reseller motions, and the cloud-marketplace buying path that increasingly decides how enterprise software actually gets purchased — the listing, the private offer, and the committed-spend drawdown that makes a deal easy for a buyer to say yes to. It also holds the architecture underneath all of that: whether a partner program should exist yet, which motions it runs, what partners earn, how they are recruited and ramped, and who wins when two routes to market claim the same account.

## The Team: 2 Specialist Agents

| # | Agent | File | What They Do |
|---|-------|------|-------------|
| 1 | Partner Ecosystem Marketer | `agents/partner-ecosystem-marketer.md` | Owns partner tiering and joint business plans, co-marketing campaign design (joint webinars, co-authored research, co-branded assets, integration launches), partner enablement and MDF programs, and cloud-marketplace GTM: listing content, pricing dimensions, private offers, CPPO, and committed-spend strategy. |
| 2 | Channel Program Architect | `agents/partner-channel-program-architect.md` | Designs the program rather than marketing through it: the readiness gate that may answer "not yet", motion selection (referral, technology, services/SI, reseller), partner unit economics on both sides including partner CAC versus direct, margin/rebate/SPIF architecture with clawbacks, recruitment and first-deal certification ramp, coverage and pruning, and the rules of engagement and channel-conflict adjudication ladder — including the compensation-neutrality decision for direct reps. |

## How to Use

### Routing User Requests

**Co-marketing & alliances** → Partner Ecosystem Marketer
- "Design a joint campaign with our integration partner"
- "Plan the launch of our new integration"
- "Build a partner tiering model and joint business plan"
- "Create a co-marketing kit our partners can actually run"

**Marketplace GTM** → Partner Ecosystem Marketer
- "Write our AWS Marketplace listing and pricing dimensions"
- "How should we use private offers and committed spend?"
- "Plan a marketplace-led motion for enterprise buyers"

**Program design, economics & conflict** → Channel Program Architect
- "Should we even build a partner program yet?"
- "Which partner motion should we launch first — referral, integration, or reseller?"
- "Model whether this reseller is worth signing, and compare partner CAC to direct"
- "Write our rules of engagement — direct and a partner are both claiming this account"
- "Design the margin bands, rebates and SPIFs, and what gets clawed back"
- "Our partners all signed up and none of them sold anything"

### Working Method

1. **Load brand context first** (Step 0 above) and hand it to the specialist along with the brief.
2. **Route to the specialist** whose remit matches the request. Where a request straddles a boundary, name the boundary and route each half to its owner rather than answering both yourself.
3. **Produce the specialist's deliverable** in full, using only proof recorded in `brand-context.md` or supplied in the request. Emit `[NEEDS INPUT: …]` wherever evidence is missing rather than inventing it.
4. **Name the handoffs.** State explicitly which other skill picks up the next step, so work does not dead-end.

**Boundaries this skill respects.** The counterparty test decides ownership: if it is a **person**, it belongs to `social-influencer-partnerships`; if it is a **company with a contract or a listing**, it belongs here. Earned media and third-party gatekeepers stay with the comms skill; link acquisition stays with `seo-link-building-strategist`. Inside this skill, the split is build-versus-market: the **Channel Program Architect** decides whether the program exists, which motions it runs, what the margin, incentives and rules of engagement are, and how partners are recruited and ramped; the **Partner Ecosystem Marketer** markets with and through the partners that program signs, and owns MDF, co-marketing, campaign kits, marketplace listings and the public tier ladder. Margin never funds a campaign and MDF never funds margin.

## Output Standards

- Every deliverable names its audience, its owner, and the decision it enables.
- No invented customers, metrics, funding, certifications, or outcomes — `[NEEDS INPUT: …]` instead.
- Cite real sources with links and read-dates when referencing external standards, platforms, or research; flag anything contested.
- Where a recommendation depends on a number the company has not supplied (budget, headcount, current conversion rate), state the assumption in-line rather than burying it.

© shalintripathi · MIT · shalintripathi/saas-marketing-agents

Similar skills

All skills for Marketing and content →

From the same set19

The whole set →
seo-growth The seo-growth Claude Code skill coordinates SEO work for B2B SaaS, from keyword research to technical audits. It activates for requests about organic traffic, content, and international search. CX Codex +1 ★ 43repo stars sales-enablement The sales-enablement Claude Code skill supports B2B sales work, from outbound planning to deal strategy. It activates for discovery calls, demos, proposals, RFPs, and buyer security reviews. CX Codex +1 ★ 43repo stars saas-marketing-suite The saas-marketing-suite Claude Code skill routes B2B SaaS marketing requests to specialist agents. It selects teams for cross-discipline work or when the right specialist is unclear. CX Codex +1 ★ 43repo stars product-marketing-ops The product-marketing-ops Claude Code skill supports B2B SaaS positioning and go-to-market planning. It activates for product launches, competitor analysis, campaign planning, and market expansion decisions. CX Codex +1 ★ 43repo stars paid-media-ops The paid-media-ops Claude Code skill supports paid advertising operations for B2B SaaS. It covers campaign planning, conversion signals, budgets, and media channels. CX Codex +1 ★ 43repo stars marketing-project-mgmt The marketing-project-mgmt Claude Code skill coordinates campaign plans, team capacity, marketing sprints, and client work. It activates for requests about campaign timelines, workload allocation, or QBR preparation. CX Codex +1 ★ 43repo stars marketing-analytics This Claude Code skill routes marketing analytics tasks to relevant specialists. Use it for campaign reviews, conversion tests, customer research, dashboards, and funnel analysis. CX Codex +1 ★ 43repo stars growth-ops growth-ops — a Claude Code skill for product-led growth and customer marketing. It routes work on activation, interactive demos, retention, and expansion to specialist agents. CX Codex +1 ★ 43repo stars

Project sponsors

Companies that keep this analytics open