Guide · Agent skill
How to use the Partnerships Architect agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
Partnerships Architect is an agent skill, a packaged set of instructions and Python scripts that an AI coding or chat agent can load and follow. It helps a startup decide whether to sign a prospective partner, at what tier (referral, reseller, OEM, services/consulting or strategic alliance), with what joint sales commitment and at what revenue-share percentage. After this guide you will know what the skill does, how to install it, how to trigger it with a plain request and how to read its outputs before making a decision.
Partnerships Architectalirezarezvani/claude-skills · MIT Download the skill Quick start
- 1Download the ZIP. Download the partnerships-architect ZIP from the page where you found this guide.
- 2Install the skill. Unzip it into ~/.claude/skills/ for personal use or into .claude/skills/ in a project, or upload it under Settings → Capabilities → Skills in the Claude apps.
- 3Fill the intake template. Complete assets/partnership_intake_template.md honestly, writing 'unknown' where you cannot verify a field, and save it as your intake JSON.
- 4Classify the partner tier. Run partner_tier_classifier.py with your intake file to get a tier verdict and rationale.
- 5Plan the 90-day GTM. Run joint_gtm_planner.py with your GTM file to get milestones, launch motion and success criteria for the tier.
- 6Model the revshare. Run revshare_modeler.py to compare partner economics with direct-sale margin and check break-even.
- 7Decide and document kill criteria. Take the outputs to your partnership committee, make the call yourself and write unwind triggers into the contract.
What the skill makes the agent do
The skill is built for Heads of Partnerships, Heads of Business Development and founder-CEOs who are reviewing a reseller, OEM or strategic alliance proposal. It works through four questions: whether the prospect is a real partner with independent demand or is hunting preferential terms, which of five tiers to sign them at, what a 90-day joint go-to-market plan would look like, and what revenue share makes sense compared with selling direct.
The skill also surfaces kill criteria, the written conditions under which a weak partnership should be unwound. It does not sign anything. The source states that a human makes the final call.
- Classifies the partner into REFERRAL, RESELLER, OEM, SI-CONSULTING or STRATEGIC tiers
- Produces a 90-day joint GTM plan with pre-launch milestones, a launch motion, a mid-quarter checkpoint and success criteria
- Models revshare against direct-sale margin and estimates break-even partner return
- Lists kill criteria for unwinding an under-performing partnership
Install the partnerships-architect skill
Download the ZIP of the skill from the page where you found this guide. Then choose one of two install locations. For a personal install available across your projects, unzip it into ~/.claude/skills/. For a single project, unzip it into that project's .claude/skills/ folder.
If you use the Claude apps instead of a local setup, open Settings, go to Capabilities, then Skills, and upload the ZIP there.
- Personal install: ~/.claude/skills/
- Project install: .claude/skills/ inside your project folder
- Claude apps: Settings → Capabilities → Skills, then upload the ZIP
Prepare your intake file before you start
The skill needs a filled-in partnership intake file, prepared from the template included with the skill (assets/partnership_intake_template.md). The template asks for the partner's identity and type, evidence of independent demand such as named accounts they have sourced, end-customer relationships and their sales team size, the strategic value they bring, and the commitments they have offered, such as joint marketing spend, dedicated headcount, certification or sales targets.
If you cannot honestly answer a field, write 'unknown' rather than guessing. The source is clear that if several fields are unknown, the partner has not shown enough substance to evaluate, and you should go back to them before continuing.
- Fill in the template honestly before running any script
- Use 'unknown' for anything you cannot verify
- Multiple unknowns mean pause and request more information from the partner
Trigger the skill with a natural request
The skill loads when your request matches its description: a startup has been approached by a prospective partner and needs to decide whether to sign, at what tier, with what joint commitment and at what revshare. Ask in plain language, for example that you want to decide whether to sign a reseller partner who has approached you, or that you want to review an OEM proposal.
Give the agent your filled-in intake file and say which step you need. The skill is designed to run in order: classify the tier, plan the GTM, model the revshare, then decide.
- Example request: Review this reseller proposal and tell me whether we should sign them and at what tier.
- Example request: Model the revshare for this OEM deal against our direct-sale margin.
- Example request: Draft a 90-day joint GTM plan for this strategic alliance and list kill criteria.
cd commercial/skills/partnerships-architect && python3 scripts/partner_tier_classifier.py --sampleRun the three scripts in order
The skill runs three Python scripts. The tier classifier applies deterministic floors to your intake and returns a tier verdict. For example, the source says STRATEGIC requires at least five named accounts, a multi-year commitment and dedicated resources. The GTM planner produces the 90-day plan and rejects motions that do not fit the tier, such as channel-led GTM for REFERRAL. The revshare modeler computes margin per deal, a recommended band based on how deeply the partner contributes (sourced, influenced or delivered), break-even partner return, and long-term economics at projected scale.
All three scripts use only the Python 3 standard library. Each accepts --help and --sample, which is a good way to see what they expect before you use your own data.
- partner_tier_classifier.py --input intake.json --profile saas --output markdown
- joint_gtm_planner.py --input gtm.json --profile saas --output markdown
- revshare_modeler.py --input revshare.json --output markdown
python3 scripts/partner_tier_classifier.py --input intake.json --profile saas --output markdownRead the outputs and make the decision
Take the tier verdict, the GTM plan and the revshare band into your partnership review. The source treats the percentage bands as starting points, not contract terms. Negotiation, MDF policy and exclusivity remain human commercial decisions.
Write the kill criteria into the contract. The source says a partnership without a written unwind trigger tends to become a permanent obligation, for example after the executive sponsor leaves.
- Revshare bands are recommendations, not final terms
- Credit 'sourced' revshare only when the partner both introduced the deal and owned the primary relationship
- Pay the lower influenced rate for deals that would have closed anyway
- Once a partner is signed, route per-deal discount approval to deal-desk
What people use it for
- Deciding whether a company that wants reseller terms has real independent customers or is only seeking a discount
- Reviewing an OEM or white-label proposal to check whether the revshare can fund Tier-2 support cost
- Testing a strategic alliance request for named accounts and commitments before agreeing to multi-year terms
- Redesigning a partner program so that referral, reseller and alliance tiers have clear rules
- Reviewing an underperforming partnership to decide whether to re-tier, restructure the go-to-market plan or unwind it
Frequently asked questions
How do I install the partnerships-architect skill?
Download the ZIP from the page where you found this guide. Unzip it into ~/.claude/skills/ for personal use or into a project's .claude/skills/ folder. In the Claude apps, you can instead upload the ZIP under Settings → Capabilities → Skills.
What do I need to run it?
You need Python 3, because the scripts use only the standard library, and a filled-in partnership intake JSON file prepared from the included template. The skill's metadata says it runs scripts but does not use the network.
Is the partnerships-architect skill free to use?
The skill is listed under the MIT licence, as stated in its metadata. The source does not mention pricing, so check the licence text in the download for the full terms.
Does the skill sign partnership deals for me?
No. The skill produces a tier verdict, a 90-day plan, a revshare band and kill criteria. A human makes the final decision and handles contract negotiation.
What is the difference between this skill and a sales engineer or deal desk tool?
This skill is for deciding whether and how to partner. It is not for technical demos or proof-of-concept work, which the source assigns to business-growth/sales-engineer. Per-deal discount approval inside a signed contract routes to deal-desk, and acquisitions route to c-level-advisor/ma-playbook.
Why does the classifier say my partner is not a real partner?
The skill treats a prospect with no independent demand, meaning no named accounts they sourced, no end-customer relationships and no sales team of their own, as someone seeking preferential terms. Such a prospect is classed as REFERRAL rather than a reseller or OEM.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Partnerships Architect suits Heads of Partnerships, BD leads and founders reviewing a reseller, OEM or strategic alliance proposal who want a structured, repeatable decision record. It is a poor fit for technical sales enablement, channel cost economics or M&A, and its percentage bands are starting points that still need commercial and legal review before any contract is signed.
Download the skill