agentsclimarketplace
Sign in

Develop platform product thinking

Skill alexe-ev/product-plugins/technical-product/skills/develop-platform-product-thinking

Apply platform and API product thinking to define developer experience, extensibility, and ecosystem strategy. Use this skill when a team is building a platform, API, or developer-facing product.From its SKILL.md

Install
npx -y skills add alexe-ev/product-plugins --skill develop-platform-product-thinking

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.3 KB, 402 tokens by cl100k_base, as published. Nobody here has run it

Develop Platform Product Thinking

Purpose

Help teams apply platform product thinking to define a clear developer experience, extension model, and ecosystem strategy.

Skill type

Conceptual skill

Use this skill when

  • A product is evolving into a platform with external developers or partners
  • An API product needs developer experience strategy
  • A team is deciding how much to expose vs. internalize in a platform
  • An ecosystem or marketplace strategy needs to be defined

Do not use this skill when

  • The goal is technical API design (a technical, not product, skill)
  • The goal is internal tool or workflow automation

Required inputs

  • Product type and current capabilities
  • Developer or partner audience

Optional inputs

  • Current API or integration surface
  • Developer feedback
  • Competitive platform landscape
  • Business model for the platform

Upstream context

Works best when:

  • Product strategy is defined
  • Target developer segment is identified

Downstream handoff

Output can feed:

  • prioritize-architecture-aware (platform strategy informs architectural priorities)
  • develop-positioning-messaging (platform needs developer-facing positioning)

Instructions

  1. Define the platform layer: what does it expose, to whom, and why?
  2. Identify the developer/partner value proposition.
  3. Define the developer experience principles.
  4. Assess the extensibility model: open / controlled / hybrid.
  5. Identify ecosystem opportunities and risks.
  6. Define the build vs. partner vs. ecosystem boundary.

Output

Provide:

  • Platform layer definition
  • Developer/partner value proposition
  • Developer experience principles
  • Extensibility model recommendation
  • Ecosystem opportunity and risk assessment
  • Build vs. partner boundary decision
  • Open questions

Risks / caveats

  • Platform products have two customers: end users and developers — both must win
  • Over-opening a platform creates quality and support risks
  • Developer adoption requires excellent documentation — factor it into the platform plan

What ships with it: 4 files

7.4 KB alongside SKILL.md

examples/

Keep looking

Skills are one crate of 326,512. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.