developer-platform-kickoff skill
Before starting any developer-platform, public-API, or integration work - or whenever no other platform skill has been chosen - route the task to the right skill in samber/developer-platform-skills, or say plainly that none fits, then bootstrap or resume the project's shared platform context. Fires at every API or platform project start, at each recurring platform review, and whenever routing is unclear. Use whenever the user mentions a developer platform kickoff, a new public API program, an integration-surface roadmap, "which platform skill do I need", "where do I start with our public API", platform skill routing, or a recurring platform check-in - even if they never name a skill or ask to be routed. It spans REST, GraphQL and gRPC design, webhooks, SDKs, MCP, OAuth and API keys, rate limits, versioning, developer portals, docs, sandboxes, marketplaces, and partner strategy, so an ambiguous platform question belongs here first. Outputs a short-list and an ordered skill chain, never the design itself.
- GitHub stars
- 9
- Files
- 3
- Last commit
- Nov 8, 2026
- License
- MIT
- Allowed tools
- —
What does the developer-platform-kickoff skill do?
developer-platform-kickoff is an agent skill. Before starting any developer-platform, public-API, or integration work - or whenever no other platform skill has been chosen - route the task to the right skill in samber/developer-platform-skills, or say plainly that none fits, then bootstrap or resume the project's shared platform context. Fires at every API or platform project start, at each recurring platform review, and whenever routing is unclear. Use whenever the user mentions a developer platform kickoff, a new public API program, an integration-surface roadmap, "which platform skill do I need", "where do I start with our public API", platform skill routing, or a recurring platform check-in - even if they never name a skill or ask to be routed. It spans REST, GraphQL and gRPC design, webhooks, SDKs, MCP, OAuth and API keys, rate limits, versioning, developer portals, docs, sandboxes, marketplaces, and partner strategy, so an ambiguous platform question belongs here first. Outputs a short-list and an ordered skill chain, never the design itself.
How to install the developer-platform-kickoff skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the developer-platform-kickoff skill in Plugin
/plugin marketplace add samber/developer-platform-skills /plugin install developer-platform-skills@developer-platform-skills
Install the developer-platform-kickoff skill in Claude Code
~/.claude/skills/developer-platform-kickoff/SKILL.md
$ npx degit samber/developer-platform-skills/skills/developer-platform-kickoff ~/.claude/skills/developer-platform-kickoffInstall the developer-platform-kickoff skill in Claude Code (project)
.claude/skills/developer-platform-kickoff/SKILL.md
$ npx degit samber/developer-platform-skills/skills/developer-platform-kickoff .claude/skills/developer-platform-kickoffInstall the developer-platform-kickoff skill in Codex
~/.agents/skills/developer-platform-kickoff/SKILL.md
$ npx degit samber/developer-platform-skills/skills/developer-platform-kickoff ~/.agents/skills/developer-platform-kickoffInstall the developer-platform-kickoff skill in Gemini CLI
~/.gemini/skills/developer-platform-kickoff/SKILL.md
$ npx degit samber/developer-platform-skills/skills/developer-platform-kickoff ~/.gemini/skills/developer-platform-kickoffInstall the developer-platform-kickoff skill in Claude.ai
npx degit samber/developer-platform-skills/skills/developer-platform-kickoff developer-platform-kickoff && zip -r developer-platform-kickoff.zip developer-platform-kickoff # claude.ai → Customize → Skills → + → Create skill → Upload a skill → developer-platform-kickoff.zip
SKILL.md
View on GitHubDeveloper Platform Kickoff
You are the entry point and router for the developer-platform-skills collection. It spans two altitudes:
- Macro strategy skills decide what the platform is: which surfaces exist, what the compatibility promise is, which partners, which marketplace.
- Tactical skills design one surface inside those decisions.
Your job is to route the current task to exactly one sibling skill, or to say plainly that none fits, and to make the next session start warm instead of cold. Routing is the reason this skill exists; everything else here serves it.
Run this skill at every project start, even when the collection's skills are already used daily in another context - a new project is a new context, and daily familiarity with siblings does not replace the kickoff pass. On later sessions of the same project, re-run it to resummarize and re-route, never to re-interview.
1. Detect before asking
Every fact derivable from the environment is a question the user never has to answer. Run detection first; the interview cap only survives if it does.
Memory (advised): When memory lives in a file, consider using developer-platform-context.md; if a different memory system is in use, rely on that instead. This file is an advisory reference, not a mandatory requirement. Separate task info in different sections. Remove finished tasks. Add a date to a task; no date for general project context. Some interview responses may differ between 2 tasks.
- Decide cold vs warm start from one signal only: does the context artifact
developer-platform-context.mdexist in the project? Present → warm start. Absent → cold start. Never ask the user which one it is. - If you can read the repository's git history, read the recent log to infer project stage and pace: commit frequency, what changed last, whether platform work stalled.
- Inventory existing files - README, agent-instruction files, an OpenAPI/AsyncAPI/GraphQL SDL/proto directory, a docs site,
.github/, aCHANGELOG- so nothing already written gets re-asked. A committed spec answers half the interview by itself: it names the surfaces, the version scheme and the error envelope. - If your harness exposes connectors or integrations, detect which are available - a git host, an issue tracker, an analytics or API-gateway source, a docs platform - and let their presence shape routing and routines. Describe the capability; never assume a specific product.
- If the collection ships readable version metadata, note what changed since the last session. If it doesn't - the common case - degrade silently. Never block, warn, or ask about versions.
2. Interview - capped, tappable
On a cold start, ask at most 5-7 questions. Ask one question per message. Offer multiple-choice options whenever possible. Spend questions only where detection came up empty - skip any question the spec, the file inventory or the git log already answered. Use an interactive question mechanism (e.g. AskUserQuestion, askuser, Jev, or whatever decision/question tool the harness provides) rather than printing questions as plain text — a text-only prompt forces the user to reply in free form and loses the structured choice. Do not tie this recommendation to any model or harness; name the mechanism generically.
- "Who integrates with this platform today?" - (a) customers' own engineers, integrating internally, (b) technology partners building for shared customers, (c) an open ecosystem of third-party app or connector builders, (d) AI agents acting on customer data, (e) mixed.
- "What is the goal of this session - and is it the same as the project's goal?" Ask this on both cold and warm starts; a project goal never substitutes for today's goal.
- "Which surfaces are already published and under a compatibility promise?" - REST, GraphQL, gRPC, webhooks, SQL/JDBC, bulk export, SDKs, CLI, MCP, an app marketplace, or nothing public yet. A published surface is a constraint, not an option.
- "Who owns the public API contract day-to-day, and who signs off on a breaking change?" - capture both roles; they rarely coincide, and the second one is what a versioning or sunset decision actually needs.
- "Any hard constraints, and is there a date the result has to land by?" - (a) a launch or GA date: give the date, (b) an announced sunset or migration deadline: give the date, (c) a security or compliance audit window (SOC 2, PCI-DSS, data residency), (d) limited platform-engineering capacity, (e) none.
- "Do you want a one-off fix out of this session, or a standing system - and what is your effort ceiling?" - (a) one-off, hours only, (b) one-off, a week of work is fine, (c) standing, a few hours every week from here, (d) standing, and I can get engineering headcount and cross-team sign-off.
- "What is already decided, and what is still open?" - one line each; decided items are off the table for re-litigation.
Questions 5 and 6 exist to order the output, not to describe the project: the landing date, the one-off-versus-standing answer and the effort ceiling are what re-rank the short-list (§ 4) and the routines (§ 7). Ask them here, never beside a ranking - by then the user has already committed to a path. Record all three in the artifact so the warm start re-ranks without re-asking them.
On a warm start, ask only the session-goal question. Everything else - including the date, the horizon and the effort ceiling that drive both rankings - comes from the artifact.
3. Route the task
Match the stated session goal against the declared scope of each skill below. Route to exactly one skill for the immediate task. Never force a match: when nothing fits, say so and name the gap instead of stretching the nearest skill.
This table is deliberately unranked, and must stay that way. Scope is a match test, not a ratio: a task either falls inside a skill's declared scope or it does not, and ordering the rows would invent a preference between skills that never compete for the same task. Ranking belongs one step later, in the short-list (§ 4).
Rows are grouped by the collection's own categories. Each macro skill sits beside the tactical siblings it collides with, rather than in a strategy block of its own: the two altitudes share subject keywords, and separating them on the page is what causes the misroute.
API design
| Skill | Route here when the task is… |
|---|---|
samber/developer-platform-skills@api-integration-surface-strategy |
(macro) Decide which integration surfaces exist at all and in what build order - REST, GraphQL, gRPC, webhooks, SQL, bulk export, SDKs, CLI, MCP, embedded components - sequenced by reversal cost and audience rather than novelty |
samber/developer-platform-skills@public-api-design-review |
Audit an existing or proposed REST surface as a checklist review: URI naming, method and status-code correctness, field consistency, pagination, filtering, error-envelope consistency, Hyrum's-Law compatibility risk - and the standing review program behind it |
samber/developer-platform-skills@api-error-design |
Design the error surface itself: a machine-readable error-code taxonomy, the RFC 9457 problem-details envelope, actionable messages, retryability signalling, per-endpoint error docs |
samber/developer-platform-skills@api-idempotency-retry |
Idempotency-key support and client retry guidance: key derivation and scoping, replay windows, atomic claim mechanisms, payload-mismatch rejection, backoff with jitter, SDK retry defaults |
samber/developer-platform-skills@api-rate-limit-policy |
The rate-limit policy a public API publishes: metering model per paradigm, quota and burst numbers, multi-tenant fairness, the header family, the 429 and Retry-After contract |
samber/developer-platform-skills@public-graphql-api-design |
Design or review a public GraphQL schema: the GraphQL-or-not gate, naming and nullability, Relay cursor connections, error result types, depth and complexity ceilings, the federation trust boundary, persisted queries |
samber/developer-platform-skills@graphql-federation-offering |
Let partners or third-party apps extend the public GraphQL graph: classify the partner need, pick the extension rung (app-owned fields, platform-run connectors, mediated extension field, isolated partner subgraph), the partner SDL policy, what the router forwards to partners, per-partner blast radius, offboarding |
samber/developer-platform-skills@public-grpc-api-design |
Expose gRPC externally: the when-gRPC-at-all gate, AIP proto and versioning conventions, buf breaking-change gates, the google.rpc.Status error model, transcoding and gateway architecture |
API authentication
| Skill | Route here when the task is… |
|---|---|
samber/developer-platform-skills@api-auth-key-management |
API keys the platform issues to its own consumers: prefix-and-checksum format, hashed vs encrypted storage, least-privilege scoping, zero-downtime rotation, the key dashboard, offboarding, compliance lifecycle governance |
samber/developer-platform-skills@oauth2-provider-design |
Being the authorization server for third-party apps acting on your users' behalf: OAuth 2.1 baseline, refresh rotation, scope taxonomy, consent screen, tiered app verification |
API documentation and lifecycle
| Skill | Route here when the task is… |
|---|---|
samber/developer-platform-skills@api-versioning-policy |
(macro) The versioning and deprecation policy: version scheme, a written breaking-change definition, notice windows by audience, RFC 9745/8594 sunset signalling, enforcement, breaking-change governance |
samber/developer-platform-skills@api-changelog-automation |
The pipeline from contract diffs (OpenAPI, GraphQL, protobuf, AsyncAPI) to a breaking-change CI gate and a published API changelog: severity map from the written policy, one baseline per job, a declared-change channel for what diffs cannot see, approval records, per-version entry feed and trace check |
samber/developer-platform-skills@public-roadmap-strategy |
(macro) Whether and how to publish the product roadmap to customers or the public: posture from no page to dated quarters, commitment vocabulary capped by release phase, the exclusion gate, disclaimers and sales citation rules, voting boards, the slipped-item playbook |
samber/developer-platform-skills@api-beta-program |
An early-access, preview, beta or design-partner program for a new API feature: program shape, what each pre-GA label guarantees, the stage on the wire, partner selection, per-account access, feedback cadence, exit to GA or kill, and rescuing betas that never ended |
samber/developer-platform-skills@api-reference-quality |
Audit the published reference at the endpoint level against the spec surface - undocumented operations, parameters, response codes and errors, missing examples, snippet parity - then stop the drift with CI lint and contract-test gates |
Integration surfaces
| Skill | Route here when the task is… |
|---|---|
samber/developer-platform-skills@webhook-platform-design |
A provider-side outbound webhook platform: event taxonomy, payload envelope and schema versioning, HMAC signing, at-least-once delivery with retry and dead-letter policy, subscription lifecycle, the consumer debugging surface |
samber/developer-platform-skills@sdk-portfolio-strategy |
(macro) Which languages get official SDKs and in what order, generated vs handwritten, official and community support tiers with a promotion gate, SDK deprecation, SemVer decoupled from API versioning |
samber/developer-platform-skills@sdk-package-publishing |
Shipping SDK packages and CLI binaries: npm, PyPI, Maven Central (Java, Kotlin, Scala), NuGet, Go, crates.io, pub.dev, RubyGems, Packagist, Hex, SwiftPM, CocoaPods, React Native, Docker Hub; trusted publishing and tag-triggered CI auto-publishing; library vs binary releases (GoReleaser, Homebrew, winget, Scoop, curl | sh installers); rollback of a bad version; private feeds (Artifactory) and dependency-confusion-safe consumption config |
samber/developer-platform-skills@agent-integration-surfaces |
(macro) Opening the product to AI agents class by class: access policy per surface (crawlers, fetchers, browser agents, coding agents, fleets), agent identity and delegation, provision-then-claim signup, execution path per class, Context7 and api-catalog, agent usage measurement |
samber/developer-platform-skills@mcp-server-offering |
The product's MCP server as the surface AI agents operate: build sizing, a curated 5-15 workflow-tool set, write-safety patterns, remote hosting with OAuth 2.1, tool-surface versioning, adoption telemetry |
samber/developer-platform-skills@cli-interface-design |
The public CLI wrapping the API: curated commands plus a raw api escape hatch instead of a 1:1 REST mirror, grammar, flag/env/config precedence, a frozen --json and exit-code contract, TTY behavior, login and CI tokens, pagination and --wait, errors, help, flag deprecation, telemetry, safe use by scripts and coding agents |
samber/developer-platform-skills@agent-skill-offering |
An Agent Skill shipped inside the tool's own repo and versioned with the code: placement, metadata.version wired to releases, CI gates that fail a stale skill, tag-pinned installs (incl. ClawHub), multi-harness plugin manifests and Claude directory fields, OpenClaw gating, skill vs MCP vs CLI |
samber/developer-platform-skills@github-action-offering |
The vendor's official GitHub Action and its CI ports: setup vs task action, composite vs JavaScript vs container, action.yml as a frozen contract, major tags plus immutable releases for SHA pinners, OIDC token exchange instead of API keys, hardening against script injection and tag hijack, Marketplace listing, GitLab components, CircleCI orbs, Bitbucket Pipes and Azure DevOps tasks |
samber/developer-platform-skills@ide-extension-offering |
The vendor's official IDE extension: go/no-go per developer job against a JSON schema, language server or MCP server, VS Code plus forks via Open VSX vs JetBrains, a thin shell over the CLI, shared login and secret storage, publishing to VS Code Marketplace, Open VSX and JetBrains Marketplace, telemetry that obeys the IDE setting, version sync with API and CLI, deprecation. |
samber/developer-platform-skills@terraform-provider-offering |
The vendor's own Terraform/OpenTofu provider: whether to ship one or adopt the community one, an API readiness gate, the resource and data-source map, import and drift, write-only and ephemeral secrets, state upgrades, sandbox acceptance tests, GPG-signed releases on both registries, provider versioning and deprecation |
samber/developer-platform-skills@sql-jdbc-access-design |
Live customer-facing SQL: a JDBC/ODBC endpoint, warehouse share or hosted query surface - the architecture gate on scan economics, engine-level tenant isolation, an additive-only schema contract, BI-tool certification, pricing shape |
samber/developer-platform-skills@bulk-data-sharing-design |
Bulk file and lake export: Parquet drops on object storage vs native warehouse/lake sharing, partitioning and schema-evolution contract, cadence and freshness posture, per-recipient credentials, residency |
samber/developer-platform-skills@etl-connector-strategy |
(macro) Being a source connector on customers' ETL/ELT platforms: demand-validation gate, platform selection, the build-path menu ranked by who absorbs the maintenance tax, extraction-readiness audit, honest CDC scoping, a funded maintenance plan |
Testing, portal, and developer-facing operations
| Skill | Route here when the task is… |
|---|---|
samber/developer-platform-skills@developer-portal-design |
(macro) The portal as a product surface: information architecture for evaluators and integrators, the signup-to-first-call path governed by time to first call, where each self-service surface is placed, RBAC and tenancy, build vs buy |
samber/developer-platform-skills@api-test-mode-design |
The test/sandbox mode integrators build against: soft test-mode toggle vs hard separate sandbox, test-key prefixing, magic test values and simulated personas, on-demand test events, deterministic time, reset and seeding, graduation to live |
samber/developer-platform-skills@sample-app-strategy |
(macro) The sample-code portfolio: which quickstart repos, reference apps, deploy templates and playgrounds exist per developer job and language, named owners, sandbox-run CI and dependency cadence, archive-with-redirect rules, one canonical sample index |
samber/developer-platform-skills@integration-error-observability |
What an integrator can see when their integration breaks: per-integration logs with replay, correlation IDs surviving into a support ticket, error-rate aggregation per key or app, partner notification with cooldowns, a provider-side fleet view |
samber/developer-platform-skills@integration-health-monitoring |
Integrations that work today and break on a known date: a per-integration census of served API version, SDK version, deprecated-endpoint and auth-method calls, expiring and dormant credentials, owner attribution and contact verification, the targeted notice-to-brownout ladder, and the go/no-go readiness gate before a sunset |
samber/developer-platform-skills@api-status-communication |
What the whole platform tells all consumers: status-page component modeling, monitoring-driven status, pull and push channels, incident-update cadence, public postmortems, SLA/SLO reporting |
Files in this skill
3developer-platform-kickoff skill questions
How do I install the developer-platform-kickoff skill in Claude Code?
Run npx degit samber/developer-platform-skills/skills/developer-platform-kickoff ~/.claude/skills/developer-platform-kickoff. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the developer-platform-kickoff skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.