mcpbeat Sign in

Strategic Alliances Agent Skill

Structures partnerships that change what the business can do — technology integrations, channel and reseller arrangements, joint ventures, and OEM relationships. Use this to evaluate or structure a strategic partnership, decide between partnering and building, negotiate commercial terms of an alliance, or diagnose a partnership that is signed but not producing. For audience-borrowing partnerships, use `marketing:partnership-marketing`.

827 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
220
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/cbrock84/headcount --skill strategic-alliances

The instruction itself

6 sections, as written by the author

Strategic alliances

Distinct from marketing partnerships. Those borrow an audience; these change what the business can

do or where it can sell.

Partner, build, or buy

Partner when the capability is genuinely outside your core, the partner is materially better at it,

and the arrangement can be unwound. Build when it is core, or when depending on someone else creates

unacceptable exposure. Buy when you need control and speed and the thesis holds.

The question that decides it: **what happens if this partner becomes a competitor, is acquired by

one, or simply loses interest?** If the answer is existential, do not partner — that is a build or

buy decision wearing a cheaper price tag.

Structure by what each side actually wants

Partnerships fail on asymmetry of motivation more than on terms. Before structuring, establish what

the partner gets, whether it is material to them, and who inside their organization is accountable

for it.

A partnership that is strategically important to you and a rounding error to them will not be

executed, whatever was signed. Being the small partner is workable — being the small *and

uninteresting* partner is not.

Terms that determine whether it works

  • Exclusivity — expensive, occasionally worth it, and always time-boxed. Perpetual exclusivity

given away early is a recurring regret.

  • Economics — who books revenue, on what split, and what happens to it if volume grows tenfold.
  • Roadmap commitments — what each side will build and by when, with a remedy if they do not.
  • Data — what flows where, under what basis, and what happens to it at termination.
  • Customer ownership — who holds the relationship, and who may market to them afterward. Most

disputed, most often left vague.

  • Termination and transition — notice, and what continues for customers mid-contract. Negotiate

the exit while everyone is friendly, because it will not be negotiable later.

Making it produce

Signed is not launched. Partnerships need a named owner on each side, a joint plan with dates, and a

regular review that either side can bring problems to.

The characteristic failure: a signed agreement, a press release, and no operational plan. Six months

later both sides believe the other did not deliver, and neither is wrong.

Enable the partner properly. Their team needs to know what to say and when to bring you in, and they

will not learn it from the contract.

Diagnosing a stalled partnership

Almost always one of: no accountable owner on one side, misaligned incentives at the level of the

people doing the work, a promised technical dependency that never shipped, or a partner whose

strategy moved.

Say it plainly and early. Partnerships die quietly for a year before anyone admits it, and that year

is the cost.

How to use it

Copy the folder

Take cbrock84/strategic-alliances from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.