Developer platform skills

Skills for building and running the developer-facing surface of a SaaS product: public APIs and their lifecycle, webhooks, SDKs, the developer portal, and the connector marketplace around it.

Written for platform PMs, API and DX engineers, SDK authors, and partner engineering: design and policy work, not code generation. Every skill is tool-agnostic: it teaches the decision, not one vendor's console.

• developer-relations-skills: DevRel strategy & execution: for developer advocates, DevRel managers, community managers
• dev-event-organizer-skills: Technical event operations: for event organizers, conference producers, hackathon leads, community builders

Part of the samber skills ecosystem

Install every skill in this repo, not just one. Skills here are atomic by design and reference each other freely: picking a single skill leaves its sibling skills uninstalled, so cross-references and routed handoffs go nowhere.

skills.sh (universal): works with any Agent Skills-compatible tool:

npx skills add samber/developer-platform-skills

Claude.ai:

1. add as a plugin marketplace: open Settings -> Capabilities -> Plugins
2. click Add -> Add marketplace -> Add from a repository
3. enter samber/developer-platform-skills
4. then Sync

Claude Code: install the plugin:

/plugin marketplace add samber/developer-platform-skills
/plugin install developer-platform-skills@developer-platform-skills

Codex (OpenAI): install via the Codex CLI:

codex plugin add github:samber/developer-platform-skills

Cursor: copy into Cursor's skills directory:

git clone https://github.com/samber/developer-platform-skills.git ~/.cursor/skills/developer-platform-skills

Cursor auto-discovers skills from .agents/skills/ and .cursor/skills/.

Gemini CLI: install as a Gemini extension:

gemini extensions install https://github.com/samber/developer-platform-skills

Update with gemini extensions update developer-platform-skills.

This collection covers the full developer-platform surface.

developer-platform-kickoff: Routes any developer-platform task to the right skill in this collection, returning a ranked short-list, an ordered chain, and an honest gap list.

• developer-platform-career: Plans a developer-platform career from the candidate side: role track, company archetype, portfolio signals, interview prep, and offer benchmarking.
• developer-platform-hiring: Builds the hiring side of a developer-platform role: scorecard, interview loop, sourcing channels, and compensation stance.

• api-error-design: Designs a public API's error surface so integrators self-serve fixes: error-code taxonomy, RFC 9457 envelope, and retryability signals.
• api-idempotency-retry: Designs idempotency-key support and client retry guidance, from key scoping and replay windows to backoff, retry budgets, and SDK defaults.
• api-rate-limit-policy: Defines the rate-limit policy a public API publishes: quota and burst numbers, response headers, the 429 contract, and override paths.
• public-api-design-review: Audits a REST API surface against cited rules, buckets every finding as Must-change or Improvement, and designs the standing review program.
• public-graphql-api-design: Designs a public GraphQL surface: the GraphQL-or-not gate, schema conventions, cursor pagination, complexity ceilings, and the federation trust boundary.
• public-grpc-api-design: Decides whether to expose gRPC publicly, then designs the proto conventions, breaking-change gates, error model, and transcoding path.

• api-auth-key-management: Designs the API-key surface a platform issues: key format, hashed storage, least-privilege scoping, zero-downtime rotation, and lifecycle governance.
• oauth2-provider-design: Designs the OAuth2 authorization server offered to third-party apps: an OAuth 2.1 baseline, scope taxonomy, consent, and app verification.

• api-reference-quality: Audits a published API reference endpoint by endpoint, then drives remediation through a staged source-of-truth rollout with CI gates.

• api-versioning-policy: Defines an API's versioning and deprecation policy: version scheme, breaking-change definition, notice windows, sunset signalling, and enforcement.

• api-integration-surface-strategy: Decides which integration surfaces a platform offers external developers and AI agents, and in what build order, sequenced by reversal cost.
• bulk-data-sharing-design: Designs bulk file and lake export as a product surface: delivery format, partitioning contract, cadence and freshness posture, credentials, and cost allocation.
• etl-connector-strategy: Plans a vendor's presence as a source connector on customers' ETL platforms: demand gate, build path, certification target, and funded maintenance.
• mcp-server-offering: Designs a product's MCP server for AI agents: a curated workflow-level tool set, write-safety patterns, hosting and auth posture, and versioning.
• sql-jdbc-access-design: Designs customer-facing live SQL access: the architecture gate on scan economics, tenant isolation, schema-stability contract, BI connectivity, and pricing shape.
• webhook-platform-design: Designs a provider-side outbound webhook platform: event taxonomy, signed payload envelope, retry and dead-letter policy, and the consumer debugging surface.

• api-test-mode-design: Designs the test/sandbox mode integrators build against: isolation model, test keys, magic values, deterministic events, reset, and the path to live.

• sdk-portfolio-strategy: Decides which languages get official SDKs and in what order, with build model, support tiers, versioning, and end-of-life policy.

• developer-portal-design: Designs an external developer portal: information architecture, the signup-to-first-call path, self-service surface placement, search, RBAC, and build-vs-buy.

• api-status-communication: Designs how an API platform tells consumers what is happening: status-page modeling, incident cadence, public postmortems, and SLA reporting.
• integration-error-observability: Designs how a platform surfaces integration failures to external developers: delivery logs, correlation IDs, error-rate aggregation, and notification posture.

• integration-listing-optimization: Optimizes a vendor's listing on a third-party app marketplace: funnel instrumentation, indexed keyword placement, media ordering, reviews, and badges.
• integration-partnership-strategy: Decides which technology partners to integrate with and how deep each goes, using a demand-data scorecard, depth ladder, and pipeline attribution.
• partner-app-onboarding: Designs the partner-developer journey from signup to first submitted app: entry gate, sandbox provisioning, education, support ladder, and funnel checkpoints.

• app-marketplace-launch-marketing: Designs a marketplace launch and ongoing app co-marketing program: founding cohort size, reveal coordination, featuring menu, and budget split.
• app-marketplace-listing-standards: Writes the listing-content rulebook an operator enforces on submissions: required fields, media geometry, quality bar, taxonomy, badges, and staleness policy.
• app-marketplace-monetization-model: Designs how a marketplace earns on the operator side: merchant-of-record posture, billing rails, fee stack, waiver programs, payouts, and tax split.
• app-marketplace-review: Designs the operator-side review and approval process for third-party apps: pipeline shape, permission audits, re-review triggers, and the enforcement ladder.
• connector-marketplace-strategy: Decides whether to build a connector marketplace, join others', or buy embedded iPaaS, then designs governance, curation, take rate, and seeding.

Give a ⭐️ if this project helped you!

Copyright © 2026 Samuel Berthe.

This project is under MIT license.