platform-strategy
Help users design and execute platform business strategies. Use when someone is building a marketplace, creating an ecosystem, deciding on API strategy, thinking about multi-sided network effects, or building developer platforms.
- Installs
- 1.6K
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/refoundai/lenny-skills --skill platform-strategy- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads platform-strategy automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Platform Strategy
Help the user design and execute platform business strategies using frameworks from 24 product leaders who have built and scaled platforms.
How to Help
When the user asks for help with platform strategy:
- Understand the platform type - Clarify whether they're building a marketplace, API platform, ecosystem, or developer platform
- Identify the network effects - Help them understand which sides of the platform create value for each other
- Assess the lifecycle stage - Determine if they're in the moat-building, opening, or closing phase
- Design for trust and governance - Help them think through the rules that will govern platform participants
Core Principles
Treat internal platforms as products
Camille Fournier: "Platform engineering is not just maintaining cloud infrastructure... platforms are products, ultimately. You should be thinking about how do I create coherent offerings that make this company more productive?" Internal platforms need dedicated product management and focus on user (developer) productivity, not just technical elegance.
Understand the four-stage platform lifecycle
Brian Balfour: "The four steps are essentially, one is I call a Step Zero. It's the conditions of the market have been met. Step One is about a moat, Step Two is about a platform opening, and Step Three is about the platform closing for control and monetization." Platforms follow a predictable lifecycle from market consensus to closing for monetization.
Reduce cognitive load through clear interfaces
Jeremy Henrickson: "The more you can bake into a clear platform, it reduces the decision-making complexity for everyone who's working on the domain part of the problem." A well-defined platform with clear interfaces simplifies product development by reducing the cognitive load on individual teams.
Find compounding dynamics
Alex Komoroske: "Anything that is shaped like an ecosystem that has some kind of network effect... you have to know what you're looking for and find the dynamics of a thing that if it worked would work at an accelerating rate." Platform success comes from identifying "gardening" opportunities - projects with inherent compounding loops that grow on their own.
Build systems, not features
Aparna Chennapragada: "The way I think about how we are positioned and what we do with GitHub is... So it's a system, not just a product or a set of features." Long-term platform defensibility comes from building a comprehensive system and repository of context rather than just a single feature or tool.
Invest incrementally based on signals
Alex Komoroske: "Invest incrementally in ecosystem projects only as you receive signals of utility and adoption." Don't bet big on platform initiatives until you have evidence of demand and usage patterns.
Questions to Help Users
- "Which side of your platform is harder to acquire? That's probably where you should focus first."
- "What value does your platform provide to a user with zero other participants?"
- "What stage of the platform lifecycle are you in - building the moat, opening, or closing?"
- "How will you prevent the supply side from being commoditized or going around you?"
- "What compounding dynamics exist in your platform that accelerate as it grows?"
- "What governance rules will you enforce, and how will you handle disputes?"
Common Mistakes to Flag
- Building platforms in a vacuum - Not iterating based on actual product and developer needs
- Treating all participants equally - Not recognizing that power users and high-quality suppliers deserve different treatment
- Skipping the moat phase - Opening a platform before establishing defensibility
- Feature thinking over systems thinking - Building point solutions instead of comprehensive systems with context
- Over-investing before signals - Betting big on platform initiatives without evidence of utility and adoption
Deep Dive
For all 28 insights from 24 guests, see references/guest-insights.md
Related Skills
- platform-infrastructure
- retention-engagement
- pricing-strategy
FAQ
What does the platform-strategy skill do?
Help users design and execute platform business strategies. Use when someone is building a marketplace, creating an ecosystem, deciding on API strategy, thinking about multi-sided network effects, or building developer platforms.
How do I install platform-strategy?
Run npx skills add https://github.com/refoundai/lenny-skills --skill platform-strategy in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/platform-strategy/ (personal) or .claude/skills/platform-strategy/ (project).
Which AI agents can use platform-strategy?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is platform-strategy safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains platform-strategy?
It is published by refoundai in refoundai/lenny-skills. It has 1,609 recorded installs.
More from refoundai/lenny-skills
personal-productivity
refoundai/lenny-skills
Help users manage their time and tasks more effectively. Use when someone is overwhelmed with work, struggling with focus, trying to balance multiple responsibilities, or asking how to get more done.
writing-prds
refoundai/lenny-skills
Help users transform abstract ideas into actionable project specs that align engineering and design teams on the problem and success metrics.
ai-product-strategy
refoundai/lenny-skills
Help users decide where to apply AI effectively, manage the transition from deterministic to probabilistic software, and build long-term defensibility through verticalization and proprietary data.
competitive-analysis
refoundai/lenny-skills
Help users understand and respond to competition. Use when someone is positioning against competitors, evaluating market threats, running competitive war games, or deciding how much to focus on competitors versus customers.
founder-sales
refoundai/lenny-skills
Help users master the transition from product development to active selling by leveraging their unique status as founders to bridge the trust gap and define a scalable sales motion.
analyzing-user-feedback
refoundai/lenny-skills
Help users convert massive volumes of qualitative and quantitative feedback into high-confidence product decisions through rigorous synthesis and internal immersion.
Popular backend & apis skills
find-skills
vercel-labs/skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
entra-app-registration
microsoft/azure-skills
Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.
google-agents-cli-adk-code
google/agents-cli
This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management" — in a project that needs ADK (Agent Development Kit) API patterns and code examples. It provides a quick reference for agent types, tool definitions, orchestration patterns, callbacks, state management, the graph Workflow API, and reference recipes to study. Do NOT use for scaffolding (use google-agents-cli-scaffold) or deployment (use google-agents-cli-deploy).
embedded-captions
heygen-com/hyperframes
Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet anchor rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.
entra-agent-id
microsoft/azure-skills
Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmipath token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).
neon
neondatabase/agent-skills
Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASEURL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.