partnerships-architect
Use when a startup is approached by a prospective partner and someone has to decide should we sign this partner, at what partner tier (referral / reseller / OEM / SI-consulting / strategic alliance), with what joint GTM commitment, and at what revshare. Classifies partner tier from independent-demand evidence vs. preferential-terms hunting, designs a 90-day joint GTM plan, models revshare against direct-sale margin, and surfaces kill criteria for unwinding under-performing partnerships. For Head of Partnerships, Head of BD, and Founder-CEOs doing reseller agreement, OEM deal, or strategic alli
Profile →npx skills add alirezarezvani/claude-skills --skill partnerships-architect --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# partnerships-architect ## Purpose Help Head of Partnerships, Head of BD, and Founder-CEOs answer four questions when a prospective partner shows up: 1. **Is this a real partner, or someone hunting preferential terms without independent demand?** 2. **At what tier should we sign them?** (Referral / Reseller / OEM / SI-Consulting / Strategic Alliance) 3. **What's the 90-day joint GTM plan that proves the partnership works?** 4. **What revshare makes economic sense — and at what point does the partnership beat direct sale?** The skill emits a tier verdict + GTM plan + revshare band with explicit kill criteria. It does **not** sign the deal. The human, after running this skill, decides. ## When to use - A prospective partner has approached and asked for reseller / OEM / "strategic" terms - You're designing a new partner program tier structure - You're reviewing an existing partnership that's underperforming and need to decide: re-tier, restructure GTM, or unwind - A Big Logo wants a "strategic alliance" — and you need to validate it's real, not vendor-lock theatre - A consulting firm or SI wants services revshare on your product - A platform vendor offers OEM / white-label and you ne
- Purpose
- When to use
- Workflow
- Step 1 — Intake (≈ 20 min)
- Step 2 — Tier classify
- Step 3 — Joint GTM plan
- Step 4 — Revshare model
- Step 5 — Decide
- Scripts
- Quick example
- References
- Assumptions
- Anti-patterns
- Distinct from
Emits a 5-tier partner classification with deterministic floors per tier for the built-in sample partner cd commercial/skills/partnerships-architect && python3 scripts/partner_tier_classifier.py --sample
What does the partnerships-architect skill do?
Use when a startup is approached by a prospective partner and someone has to decide should we sign this partner, at what partner tier (referral / reseller / OEM / SI-consulting / strategic alliance), with what joint GTM commitment, and at what revshare. Classifies partner tier from independent-demand evidence vs. preferential-terms hunting, designs a 90-day joint GTM plan, models revshare against direct-sale margin, and surfaces kill criteria for unwinding under-performing partnerships. For Head of Partnerships, Head of BD, and Founder-CEOs doing reseller agreement, OEM deal, or strategic alli
How do I install it?
Run `npx skills add alirezarezvani/claude-skills --skill partnerships-architect --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.