MCPInstall

platform-product-manager

Expert platform and API product management guidance for developer-focused products. Use when planning API product strategy, designing APIs, improving developer experience (DX), creating developer documentation, building SDKs, planning API versioning and deprecation, building developer communities, creating integration marketplaces, or measuring platform health. Covers REST, GraphQL, webhooks, and platform ecosystems.

Installs
158
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/ncklrs/startup-os-skills --skill platform-product-manager
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads platform-product-manager automatically when relevant.

  3. 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 Product Manager

Strategic product management expertise for API-first and developer-focused platforms — from API design and developer experience to ecosystem building and platform metrics.

Philosophy

Great platform products aren't about features. They're about making developers successful.

The best API and platform products:

  1. Developer experience is product experience — DX is your primary differentiator
  2. APIs are user interfaces — Design them with the same care as visual UIs
  3. Documentation is product — Great docs reduce support, increase adoption, drive success
  4. Ecosystem multiplies value — Your integrations make your platform stickier

How This Skill Works

When invoked, apply the guidelines in rules/ organized by:

  • api-* — API design principles, standards, and patterns
  • dx-* — Developer experience, onboarding, and success
  • docs-* — Developer documentation strategy and standards
  • sdk-* — SDK and library strategy
  • versioning-* — API versioning, deprecation, and migration
  • community-* — Developer community and ecosystem building
  • marketplace-* — Integration marketplace and partner strategy
  • metrics-* — Platform health and success metrics

Core Frameworks

Platform Maturity Model

StageFocusKey MetricsTeam Structure
FoundationCore API, basic docsAPI uptime, error ratesPM + Engineers
GrowthDX, SDKs, onboardingTime-to-first-call, activation+ DevRel, DX engineers
ScaleEcosystem, marketplaceIntegration count, partner revenue+ Partner team
PlatformNetwork effects, flywheelPlatform GMV, ecosystem valueFull platform org

The Developer Journey

┌─────────────┐   ┌─────────────┐   ┌─────────────┐   ┌─────────────┐
│  DISCOVER   │ → │   EVALUATE  │ → │   ADOPT     │ → │   EXPAND    │
│             │   │             │   │             │   │             │
│ - Search    │   │ - Docs      │   │ - Signup    │   │ - More APIs │
│ - Content   │   │ - Sandbox   │   │ - First call│   │ - Higher    │
│ - Referral  │   │ - Pricing   │   │ - Use case  │   │   volume    │
│             │   │             │   │   solved    │   │ - Referral  │
└─────────────┘   └─────────────┘   └─────────────┘   └─────────────┘

API Design Hierarchy

                    ┌─────────────────┐
                    │   CONSISTENCY   │  ← Predictable patterns
                    ├─────────────────┤
                    │   SIMPLICITY    │  ← Easy to understand
                    ├─────────────────┤
                    │   DISCOVERABILITY│ ← Self-documenting
                    ├─────────────────┤
                    │   RELIABILITY   │  ← Stable and trustworthy
                    ├─────────────────┤
                    │   PERFORMANCE   │  ← Fast and efficient
                    └─────────────────┘

Developer Success Metrics Stack

┌─────────────────────────────────────────────────────────────────┐
│                    BUSINESS OUTCOMES                            │
│        Revenue, Retention, Net Dollar Retention                 │
├─────────────────────────────────────────────────────────────────┤
│                    DEVELOPER SUCCESS                            │
│     Active Developers, API Calls, Use Cases Completed           │
├─────────────────────────────────────────────────────────────────┤
│                    DEVELOPER EXPERIENCE                         │
│   Time-to-First-Call, Activation Rate, Support Tickets          │
├─────────────────────────────────────────────────────────────────┤
│                    PLATFORM HEALTH                              │
│        Uptime, Latency, Error Rates, Documentation Quality      │
└─────────────────────────────────────────────────────────────────┘

Platform Types

TypeExamplesKey Success FactorPrimary Metric
Infrastructure APIStripe, Twilio, AWSReliability + DXAPI calls, uptime
Data APIPlaid, ClearbitData quality + freshnessData coverage
Aggregation PlatformZapier, SegmentIntegrations + easeConnections made
Developer ToolsGitHub, VercelWorkflow fit + speedActive projects
Embedded PlatformShopify AppsDistribution + valueInstall rate, GMV

API Style Comparison

StyleBest ForComplexityFlexibilityCaching
RESTCRUD operations, simple resourcesLowMediumExcellent
GraphQLComplex data fetching, mobileMediumHighManual
gRPCInternal services, high perfHighLowN/A
WebhooksReal-time events, async flowsLowMediumN/A
WebSocketBi-directional, real-timeMediumHighN/A

Anti-Patterns

  • API-first without developer-first — Technically great API that's hard to use
  • Documentation as afterthought — Docs written after API is "done"
  • Breaking changes without warning — Surprising developers with incompatibilities
  • Vanity integrations — Building integrations nobody uses for marketing
  • Platform before product-market fit — Building ecosystem before core value
  • Ignoring support signals — Not treating support tickets as product feedback
  • One-size-fits-all SDK — Same SDK strategy for all languages/use cases
  • Versioning without migration path — New versions without upgrade guides

FAQ

What does the platform-product-manager skill do?

Expert platform and API product management guidance for developer-focused products. Use when planning API product strategy, designing APIs, improving developer experience (DX), creating developer documentation, building SDKs, planning API versioning and deprecation, building developer communities, creating integration marketplaces, or measuring platform health. Covers REST, GraphQL, webhooks, and platform ecosystems.

How do I install platform-product-manager?

Run npx skills add https://github.com/ncklrs/startup-os-skills --skill platform-product-manager 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-product-manager/ (personal) or .claude/skills/platform-product-manager/ (project).

Which AI agents can use platform-product-manager?

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-product-manager 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-product-manager?

It is published by ncklrs in ncklrs/startup-os-skills. It has 158 recorded installs.

More from ncklrs/startup-os-skills

View all →

community-builder

ncklrs/startup-os-skills

Expert community-led growth and community management guidance. Use when building developer communities, Discord/Slack communities, online communities, managing community platforms, designing member onboarding, creating engagement programs, running ambassador programs, measuring community health, setting up moderation systems, or implementing DevRel strategies. Use for community-led growth, member activation, user-generated content programs, and community governance.

Marketing & SEO630 installs

proposal-writer

ncklrs/startup-os-skills

Expert sales proposal and pricing presentation strategist. Use when writing proposals, executive summaries, ROI business cases, pricing presentations, SOWs (Statement of Work), RFP responses, or competitive positioning documents. Covers proposal structure, terms positioning, design formatting, follow-up strategy, and win-rate optimization.

Docs & Writing594 installs

motion-designer

ncklrs/startup-os-skills

Advanced motion designer with decades of After Effects and motion graphics experience, specialized in creating engaging video specifications for Remotion. Use when creating video specs, planning motion graphics, designing animations, or when asked to "create a video", "design motion graphics", "plan video content", or "spec out a video". Produces detailed scene-by-scene specifications with timing, audio, sound effects, and animation descriptions.

Frontend & Design574 installs

website-copy-specialist

ncklrs/startup-os-skills

Expert website copywriting for SaaS and B2B companies. Use when writing homepage copy, feature pages, about pages, pricing pages, comparison pages, product tours, integration pages, use case pages, demo/contact pages, or navigation microcopy. Use for website messaging hierarchy, value proposition development, and page-level conversion optimization.

Marketing & SEO552 installs

vsl-storyboard-writer

ncklrs/startup-os-skills

Open the skill to read its SKILL.md instructions.

Docs & Writing467 installs

remotion-animation

ncklrs/startup-os-skills

Generates animation configurations for Remotion including spring configs, interpolations, easing functions, and timing logic. Focuses ONLY on animation parameters, NOT component implementation. Use when defining animation behavior or when asked to "configure animations", "setup spring configs", "define easing curves".

Frontend & Design442 installs

Popular backend & apis skills

View category →

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.

OfficialBackend & APIs4.1M installs

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.

OfficialBackend & APIs566.7K installs

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).

Backend & APIs514.8K installs

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.

Backend & APIs453.3K installs

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).

OfficialBackend & APIs336.6K installs

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.

Backend & APIs237.1K installs