mcpbeat Sign in

Grad Business Ecosystems Agent Skill

Apply Moore's business ecosystem framework to analyze how firms co-evolve through four stages (birth, expansion, authority, renewal) and occupy different ecosystem roles. Use this skill when the user needs to map ecosystem dynamics in a platform or industry, evaluate keystone vs dominator strategies, assess ecosystem health, or when they ask 'what stage is this ecosystem in', 'how should we position in this ecosystem', or 'why is this ecosystem declining despite having a dominant player'.

3k tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
223
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/asgard-ai-platform/skills --skill grad-business-ecosystems

What comes with it

6 622 bytes besides the instruction
examples/sample_scenario.md

The instruction itself

13 sections, as written by the author

Business Ecosystems (Moore)

Overview

Moore's business ecosystem framework conceptualizes industries as co-evolving communities of firms, customers, and other stakeholders that collectively create and capture value. Ecosystems progress through four stages (birth, expansion, authority, renewal), and participants occupy distinct roles — keystone, dominator, or niche player — each with different strategies and implications for ecosystem health.

When to Use

  • Analyzing platform-based markets or multi-firm value creation networks
  • Evaluating strategic positioning within an industry ecosystem
  • Assessing why an ecosystem is thriving, stagnating, or collapsing
  • Planning entry strategy into an existing ecosystem or designing a new one

When NOT to Use

  • When the industry is best modeled as atomistic competition (no co-evolution)
  • When the analysis focuses on a single firm's internal strategy (use RBV or dynamic capabilities)
  • When formal supply chain analysis with contractual specificity is needed

Assumptions

IRON LAW: Ecosystem health depends on DIVERSITY and PRODUCTIVITY — a
dominant player that extracts too much value destroys the ecosystem
it depends on.

Key assumptions:

  • Firms co-evolve — strategy is shaped by and shapes the broader ecosystem
  • Value is created collectively and distributed among ecosystem participants
  • Ecosystem leadership requires nurturing the ecosystem, not just capturing value
  • Ecosystems have life cycles — what works in birth stage fails in renewal stage

Methodology

Step 1: Define the Ecosystem Boundary

Identify the ecosystem: core value proposition, platform or focal firm, and key participant categories (suppliers, complementors, customers, competitors).

Step 2: Assess the Ecosystem Stage

| Stage | Characteristics | Key Challenge |

|-------|----------------|---------------|

| Birth | Entrepreneurs define value proposition around a seed innovation | Protect ideas, build initial partnerships |

| Expansion | Scaling to broad market, attracting complementors | Achieve critical mass, fend off alternative ecosystems |

| Authority | Stable architecture, clear leader, standards established | Maintain bargaining power, encourage continued innovation |

| Renewal | Mature ecosystem faces disruption or stagnation | Reinvent or be displaced by new ecosystems |

Step 3: Map Ecosystem Roles

Classify key participants: keystone (creates shared value, maintains platform health), dominator (captures most value, controls ecosystem), niche player (specializes in narrow segment).

Step 4: Evaluate Ecosystem Health

Assess three health metrics: productivity (value created per participant), robustness (survival rate of participants), and niche creation (diversity of roles and opportunities).

Output Format

## Ecosystem Analysis: [Context]

### Ecosystem Definition
- Core value proposition: [what the ecosystem delivers]
- Focal firm/platform: [the central orchestrator]
- Key participants: [complementors, suppliers, customers, competitors]

### Stage Assessment
- Current stage: [birth / expansion / authority / renewal]
- Evidence: [indicators supporting this assessment]
- Trajectory: [evolving toward which next stage]

### Role Map
| Participant | Role | Value Created | Value Captured | Strategy |
|-------------|------|---------------|----------------|----------|
| [name] | [keystone/dominator/niche] | [contribution] | [share] | [approach] |

### Health Assessment
- Productivity: [high/medium/low] — [evidence]
- Robustness: [high/medium/low] — [evidence]
- Niche creation: [high/medium/low] — [evidence]
- Overall health: [thriving / stable / declining / collapsing]

### Implications
1. [Strategic recommendation for target firm]
2. [Risk of ecosystem decline and mitigation]

Gotchas

  • Ecosystem is NOT a metaphor for "industry" — it specifically implies co-evolution and interdependence
  • Keystone strategy is not altruism — it is enlightened self-interest that sustains the value network
  • Dominator strategies can succeed short-term but often destroy ecosystem health long-term
  • Platform ecosystems add network effects dynamics not in Moore's original biological metaphor
  • Do not assume one firm controls the ecosystem — leadership can shift, especially during renewal
  • The four stages are not deterministic — ecosystems can skip stages or regress

References

  • Moore, J. F. (1993). Predators and prey: A new ecology of competition. *Harvard Business Review*, 71(3), 75-86.
  • Iansiti, M., & Levien, R. (2004). *The Keystone Advantage: What the New Dynamics of Business Ecosystems Mean for Strategy, Innovation, and Sustainability*. Harvard Business School Press.
  • Adner, R. (2012). *The Wide Lens: A New Strategy for Innovation*. Portfolio/Penguin.

Other skills for the same job

different authors, same section of the catalogue
Protocolsio Integration
by christophacham
×4

Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.

16k tokens
Tailored Resume Generator
by frostant
×4

Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances

3k tokens
Excalidraw Diagram Generator
by github
vendor ×3

Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.

36k tokens scripts
Expo Dev Client
by openai
vendor ×3

Build and distribute Expo development clients locally or via TestFlight

961 tokens
Executing Plans
by ZhanlinCui
×3

Use when you have a written implementation plan to execute in a separate session with review checkpoints

542 tokens
Anndata
by christophacham
×3

Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.

16k tokens
Benchling Integration
by christophacham
×3

Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.

14k tokens
Biopython
by christophacham
×3

Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.

24k tokens

How to use it

Copy the folder

Take asgard-ai-platform/grad-business-ecosystems 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.