sdk-portfolio-strategy Skill (samber): Which SDK Languages to Ship

Makes Claude decide which language SDKs your API should have, how to build them, how to support them and when to retire them.

Installs: 9.6K; on skills.sh
Stars: 9; on GitHub
Files: 4; besides SKILL.md
Updated: Nov 2026; last repo commit

sdk-portfolio-strategy makes Claude plan a public API's language SDK portfolio. It covers which languages get official SDKs and in what order, generated or handwritten builds, official and community support tiers, versioning, and how to retire an SDK.

It starts when you mention client libraries, SDKs, which languages to support first, an SDK generator such as Stainless, Fern or OpenAPI Generator, community SDKs or sunsetting an SDK. Claude asks 9 interview questions, one per message, offers 2 to 3 candidate portfolios, then drafts 7 sections and checks each with you. The skill bundles no scripts.

Good for

API teams launching and choosing their first SDK languages
Teams with handwritten SDKs deciding on tiers and promotion rules
Maintainers building the case to retire a low-use SDK

Install sdk-portfolio-strategy

Claude Code

Copy this prompt.

Install the sdk-portfolio-strategy skill in Claude Code. Run this command:

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

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

Pick one route, not both, or you get every skill twice. The README asks you to install the whole set, not just sdk-portfolio-strategy, because the skills reference each other and a lone skill leaves those hand-offs with nowhere to go. The plugin adds all 61 skills in the repo (counted from the repo tree). Its manifests list no hooks, agents or MCP servers.

From the project README. Source.

What's in the skill

When it loads

Decide a public API's language-SDK portfolio - which languages get official SDKs and in what order, generated vs handwritten build model, official and community support tiers with a promotion gate, SDK deprecation and end-of-life, and decoupling SDK SemVer from API versioning and release cadence. Use whenever the user mentions client libraries, SDKs, which languages to support first, an SDK generator (Stainless, Fern, OpenAPI Generator), community SDKs, or sunsetting an SDK - even if they never say "SDK portfolio". Portfolio strategy only, not single-SDK ergonomics or registry publishing. Do NOT use for whether to offer SDKs as a surface at all - use samber/developer-platform-skills@api-integration-surface-strategy instead.

Sections in SKILL.md

Interview
Developer vertical split
Brainstorm candidate portfolios
Workflow
1. Confirm the surface decision
2. Map the audience to a language order
3. Set support tiers and the promotion gate
4. Choose the build model
5. Decouple the three versioning policies
6. Write the deprecation and EOL playbook
7. Publish the community policy
Failure modes
Measurement
Invocation examples
References

Key facts

Author: Samuel Berthe
License: MIT
Version: 1.0.3
Installs on skills.sh: 9,561 (Nov 2, 2026)
GitHub stars: 9 (Nov 2, 2026)
skills.sh audits: Gen Agent Trust Hub pass; Socket pass; Snyk pass (Nov 2, 2026)
Last repo commit: Nov 1, 2026
What installs: 5 files including SKILL.md: evals/evals.json and 3 reference files. It bundles no scripts.
Needs: The other skills in the repo; the README says to install the whole set
Works in: Claude Code, Claude.ai, Codex, Cursor, Gemini CLI, and other agents through the skills CLI

What it includes

Asks 9 interview questions, one per message, before proposing anything.
Try: “We're launching our public API next quarter - which language SDKs should we build first, and should we generate them?”
Opening questions
Offers 2 to 3 portfolio shapes with trade-offs and lets you pick or blend.
Brainstorm candidate portfolios
Checks that SDKs were chosen as an integration surface before planning.
Confirm the surface decision
Ranks each language: official SDK, community tier or spec-driven self-service.
Map the audience to a language order
Defines what official means; two tiers, official and community, is the default.
Set support tiers and the promotion gate
Picks one build model: handwritten, OpenAPI Generator or commercial codegen.
Choose the build model
Writes separate policies for SDK version, API version and runtime support window.
Decouple the versioning policies
Builds the case with usage and revenue data before announcing an SDK's end of life.
Write the deprecation and EOL playbook
Decides how community SDKs are listed and what is not guaranteed.
Publish the community policy
Advises saving decisions to developer-platform-context.md when memory is a file.
Write · Remember decisions (optional)

From the official docs

Permissions

Low risk

This skill is written advice that bundles no scripts. The one thing it may write is a decisions file, so check what Claude saves.

What it can do

Read your data
Create and change things
Delete things
Read-only mode

Watch out for

It may save decisions to a file
SKILL.md advises using developer-platform-context.md when memory lives in a file, and calls it an advisory reference. Check or delete that file if you do not want decisions kept. github.com
The plugin route adds all 61 skills
The README asks you to install every skill in the repo, and the repo has 61. The plugin manifests list no hooks, agents or MCP servers, and the repo tree holds none. github.com
Folder holds Markdown and one JSON file
This skill's folder has 5 files: SKILL.md, evals/evals.json and 3 reference files. It has no .py, .sh or .js file. github.com

Security advisories

No published security advisories as of Nov 2, 2026.

Technical details

Turning on read-only	No read-only setting is documented. Decline the memory-file suggestion if you want no files written.
Scopes	Asks you opening questions and works from your answers and anything you share, such as specs or docs May save settled decisions to a file named developer-platform-context.md if your memory lives in a file

Questions

How do I install sdk-portfolio-strategy?

Use the install box above. The README asks you to install all 61 skills in the repo, not just this one, because the skills point to each other. In Claude Code that is the plugin route, and elsewhere the skills CLI or the client's own route installs the set.

Does sdk-portfolio-strategy work in Claude.ai, Codex or Cursor?

The README documents installs for Claude.ai, Claude Code, Codex, Cursor and Gemini CLI. It also lists the skills CLI, which it calls universal for Agent Skills-compatible tools. The Claude.ai route adds the whole repo as a plugin marketplace.

Does it need an API key or any setup?

SKILL.md sets no environment variable and the folder bundles no scripts. It does ask for details of your own API or product in its opening questions.

Is sdk-portfolio-strategy safe to use?

The folder holds Markdown and one JSON file, and no scripts. SKILL.md does suggest saving settled decisions to developer-platform-context.md when your memory lives in a file, so check what Claude writes. Our advice: treat the design it produces as a draft for your team to review before you publish it.

sdk-portfolio-strategy vs api-integration-surface-strategy?

api-integration-surface-strategy decides whether to offer SDKs at all. This skill starts after that decision and plans which languages, tiers and build model to use. SKILL.md stops and sends you back if the surface decision has not been made.

Does it generate or publish my SDKs?

It plans the portfolio. SKILL.md says it covers portfolio strategy only, and sends registry publishing to sdk-package-publishing. Single-SDK ergonomics are outside its scope.

Information

updated Nov 2, 2026

Repository: samber/developer-platform-skills
Folder: skills/sdk-portfolio-strategy

samber/developer-platform-skills skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 6

README · github.com
sdk-portfolio-strategy SKILL.md · github.com
sdk-portfolio-strategy folder · github.com
api-integration-surface-strategy SKILL.md · github.com
marketplace.json · github.com
plugin.json · github.com