platform-strategy

Design and execute platform strategies for multi-sided ecosystems and developer platforms.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/cvillamarp-lgtm/skillspodcast --skill platform-strategy-cvillamarp-lgtm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: platform-strategy
Source: https://github.com/cvillamarp-lgtm/skillspodcast/tree/main/skills/platform-strategy
Command: npx skills add https://github.com/cvillamarp-lgtm/skillspodcast --skill platform-strategy-cvillamarp-lgtm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Platform leaders struggle to design scalable, robust strategies for ecosystems, marketplaces, and developer platforms across multiple participant groups.

Core Features & Use Cases

  • Lifecycle guidance: clarify platform lifecycle stages (moat, opening, closing) and how to progress with governance and incentives.
  • Network effects framing: identify and optimize value flows between participants to drive growth.
  • Governance and APIs: design governance rules, APIs, and interoperability to scale an ecosystem.
  • Use Case: You are launching a two-sided marketplace and need a structured plan to launch, regulate, and monetize participants.
  • Use cases also include internal platform teams and external partner ecosystems.

Quick Start

Propose a platform type (marketplace, API, or developer platform) and outline the first three network effects you will cultivate.

Frequently Asked Questions about platform-strategy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a governance framework for a multi-sided marketplace?

Scaling a developer platform involves identifying and optimizing network effects between participants, applying lifecycle guidance from moat building to opening and closing stages, and structuring governance rules to drive ecosystem growth.

What is the best way to structure network effects for an API platform?

Structuring network effects for an API platform requires identifying and optimizing value flows between participant groups. You cultivate these effects by designing interoperability and incentives that encourage cross-partner collaboration across the ecosystem lifecycle.

How do I manage the platform lifecycle from moat building to opening?

Managing the platform lifecycle involves clarifying stages like moat, opening, and closing. You progress through these stages by applying structured governance rules and incentives that regulate value exchange and guide cross-partner collaboration.

Can I use this approach for internal platform teams and external partner ecosystems?

Yes, this structured framework applies to both internal platform teams and external partner ecosystems. It guides the design of governance rules, APIs, and interoperability to scale multi-sided ecosystems at various lifecycle stages.

How do I launch and monetize a two-sided marketplace?

To launch and monetize a two-sided marketplace, you need a structured plan to regulate participants and cultivate initial network effects. This involves designing governance rules and value exchange incentives across platform lifecycle stages.

When should I not use a platform strategy framework for my ecosystem?

You should avoid a platform strategy framework if your ecosystem lacks multiple participant groups requiring value exchange. Without multi-sided network effects or cross-partner collaboration, structured governance and API interoperability provide limited scaling benefits.