asgard-ai-platform/grad-coopetition
Apply the Co-opetition Value Net framework (Brandenburger and Nalebuff, 1996) to map cooperative and competitive dynamics in business relationships. Use this skill when the user needs to identify complementors, analyze the PARTS framework, or design strategies that simultaneously cooperate and compete with the same players.
npx skills add https://github.com/asgard-ai-platform/skills --skill grad-coopetition
Co-opetition recognizes that business relationships are never purely competitive or purely cooperative. The Value Net model extends Porter's focus on rivalry by adding complementors — players whose products increase the value of yours. The PARTS framework (Players, Added value, Rules, Tactics, Scope) provides a structured approach to changing the game rather than just playing it.
Trigger conditions:
When NOT to use:
IRON LAW: Every Business Relationship Contains BOTH Cooperative
and Competitive Elements
There is NO purely competitive or purely cooperative relationship.
A supplier cooperates (provides inputs) AND competes (captures margin).
A competitor competes (takes share) AND cooperates (grows the category).
Any analysis that labels a player as ONLY competitor or ONLY partner
is incomplete. Always map BOTH dimensions.
Place the focal firm at the center and map four player types: Customers, Suppliers, Competitors (whose products DECREASE your value), and Complementors (whose products INCREASE your value). Key insight: a player can occupy multiple roles (Samsung supplies displays to Apple AND sells competing phones).
For each player, calculate added value:
Systematically evaluate five levers to change the game:
| Lever | Question | Action |
|-------|----------|--------|
| Players | Who is in the game? Should we add/remove players? | Bring in new complementors, attract new competitors to reduce supplier power |
| Added value | How can we increase our added value? | Differentiate, build switching costs, create loyal customers |
| Rules | What rules govern the game? Can we change them? | Contracts, regulations, industry standards, MFN clauses |
| Tactics | How do perceptions shape the game? | Signaling, commitments, transparency vs fog |
| Scope | What is the boundary of the game? | Link or de-link games, expand or narrow scope |
For each key relationship, specify:
# Co-opetition Analysis: {Focal Firm}
## Value Net Map
- Customers / Suppliers / Competitors / Complementors: {list each, note dual roles}
## Added Value Assessment
| Player | Added Value | Leverage |
|--------|-------------|----------|
| {Focal firm} | {assessment} | {high/medium/low} |
## PARTS Analysis
| Lever | Current State | Recommended Change |
|-------|---------------|-------------------|
| Players / Added value / Rules / Tactics / Scope | {current} | {action} |
## Co-opetition Strategy
- Cooperate on: {activities} | Compete on: {activities} | Boundary rules: {policy}
references/coopetition-game-theory.mdreferences/parts-framework-guide.mdTake asgard-ai-platform/grad-coopetition from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.