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 alliance review — not technical sale enablement, not channel cost economics, not M&A.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, actionable partnership-decision workflow with concrete script invocations, a clear multi-step sequence with validation gates, and a clean one-level-deep bundle layout. Its main weakness is mild redundancy between the 'Do not use for' and 'Distinct from' sections.

Suggestions

Collapse the 'Do not use for' list and the 'Distinct from' section into one, since they restate the same routing boundaries (sales-engineer, channel-economics, ma-playbook, deal-desk).

Add an explicit validate→fix→retry feedback loop for Step 2/3 (e.g. what to do when the classifier returns a lower tier than the GTM plan assumes), to lift workflow clarity toward the top anchor.

Consider moving the 7-question forcing-question library into a reference file and summarizing it inline, to reduce body length and keep SKILL.md a pure overview.

Dimension	Reasoning	Score
Conciseness	Largely lean and domain-specific with no generic concept explanations, but there is redundancy between 'Do not use for' and the later 'Distinct from' section, and the Purpose section restates the frontmatter description; minor trimming possible.	4 / 5
Actionability	Fully executable, copy-paste-ready commands for all three scripts (e.g. 'scripts/partner_tier_classifier.py --input intake.json --profile saas --output markdown') plus a '--sample' quick example, with the referenced scripts confirmed present in the bundle.	5 / 5
Workflow Clarity	A clear 5-step sequence (Intake → Tier → GTM → Revshare → Decide) with an explicit stop-gate in Step 1 and script-validated rules in Step 3, but explicit validate→fix→retry feedback loops are less spelled out than the score-5 anchor expects.	4 / 5
Progressive Disclosure	Well-organized overview pointing one level deep to a real bundle (assets/partnership_intake_template.md, three scripts, three references), each clearly signaled with a one-line description in the References section; navigation is easy and all referenced paths exist.	5 / 5
	Total	18 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is comprehensive and well-structured: it states concrete capabilities, gives explicit 'Use when' triggers with natural deal-type vocabulary, and clearly fences off adjacent skills. It is a strong, low-conflict description.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Classifies partner tier', 'designs a 90-day joint GTM plan', 'models revshare against direct-sale margin', 'surfaces kill criteria for unwinding' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both what (classify tier, design GTM plan, model revshare, surface kill criteria) and when ('Use when a startup is approached by a prospective partner and someone has to decide should we sign this partner...') with concrete trigger phrasing.	5 / 5
Trigger Term Quality	Comprehensive natural terms a Head of Partnerships would actually say — 'prospective partner', 'reseller', 'OEM', 'strategic alliance', 'revshare', 'joint GTM', 'reseller agreement', 'OEM deal' — including synonyms and deal-type variants.	5 / 5
Distinctiveness Conflict Risk	Clear niche (partner sign/tier/GTM/revshare decisions) with explicit exclusions ('not technical sale enablement, not channel cost economics, not M&A') minimizing overlap with adjacent skills.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: commercial/skills/partnerships-architect/SKILL.md
Commit: 19392f7

Reviewed: ~10 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.