developer-segmentation Skill (samber): Audience Segments

Makes Claude cut a developer audience into a few named, sized and ranked segments and pick the one to serve first.

Installs: 12.4K; on skills.sh
Stars: 7; on GitHub
Files: 6; besides SKILL.md
Updated: Nov 2026; last repo commit

developer-segmentation interviews you, then runs six steps. It picks two dimensions to cut on, brainstorms candidate cuts, sizes each segment with a confidence tier, names who uses, champions, approves and buys inside each, scores and ranks them, and writes a segment map validated section by section.

The map ends with one primary segment, one secondary and a written anti-segment. SKILL.md says the journey map is a different skill, developer-journey-map. It bundles 5 reference files and an evals file, and no scripts.

Good for

DevRel leads deciding which developer audience to serve first
Founders asking who their developers actually are
Marketers whose content reaches everyone and converts nobody

Install developer-segmentation

Claude Code

Copy this prompt.

Install the developer-segmentation skill in Claude Code. Run this command:

/plugin marketplace add samber/developer-relations-skills
/plugin install developer-relations-skills@developer-relations-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.

Install the whole set, not one skill: the README says the skills reference each other, so picking one leaves those pointers going nowhere. The repo tree holds 93 skill folders. Fourteen of them bundle .py or .sh files; developer-segmentation bundles none. The tree holds no hooks, agents or MCP config files.

From the project README. Source.

What's in the skill

When it loads

Cuts a developer audience into a few named, sized and ranked segments - the two dimensions worth cutting on, a size range with a confidence tier, the user/champion/approver/buyer split inside each, a weighted score, one primary and one secondary segment, and a written anti-segment. Use whenever someone asks who their developers actually are, which developer audience to serve first, how big a language ecosystem or persona is, whether to target hobbyists or enterprise platform teams, who signs when the developer is not the buyer, or why content reaches everyone and converts nobody - even if they only say "who is this for". Not the journey map - use samber/developer-relations-skills@developer-journey-map.

Sections in SKILL.md

Interview
Step 1 - Choose the two dimensions
Step 2 - Brainstorm candidate cuts before choosing one
Step 3 - Size each segment, with a confidence tier
Step 4 - Name the decision unit inside each segment
Step 5 - Score and rank
Step 6 - Write the map and validate it section by section
Cut the two dimensions, and the ones deliberately rejected
Segments 3-5 rows: name, definition, size + confidence, decision unit,
Primary the chosen segment, its score, why it beat the runner-up
Secondary served only by artefacts the primary already funds
Anti-segment who is not served this horizon, and why
Hypotheses segments below the evidence floor, with the test that settles each
Implications what changes now: artefacts, channels, proof, and what stops
Review re-decision date, plus the events that force an early re-read
Invocation examples

Key facts

Author: Samuel Berthe (named in SKILL.md metadata and plugin.json)
License: MIT (SKILL.md, plugin.json and the LICENSE file agree)
Version: 1.0.2 (SKILL.md metadata)
Installs on skills.sh: 12,375 (Nov 2, 2026)
GitHub stars: 7 for the whole samber/developer-relations-skills repo (Nov 2, 2026)
Last repo commit: Nov 1, 2026
What it includes: 7 files in the git tree including SKILL.md. No scripts.
Needs: SKILL.md lists nothing to install. The skill folder bundles no scripts
Part of: The developer-relations-skills plugin: 93 skill folders in the git tree
Works in: Claude Code, Claude.ai, Codex, Cursor and Gemini CLI, as the README documents

What it includes

One question at a time until product shape, funded driver and evidence are known
Read · Interview
One dimension that changes what you build, one that changes how you reach them
Read · Step 1: choose two dimensions
Brainstorms cuts and compares them before choosing one
Write · Step 2: candidate cuts
Gives each a size range and a confidence tier
SKILL.md says to use survey and registry data if Claude can browse, and first-party data only if it cannot.
Network · Step 3: size segments
Names the user, champion, approver and buyer inside each segment
Write · Step 4: decision unit
A weighted score picks one primary and one secondary
Write · Step 5: score and rank
The map has sections from Cut to Review, validated one at a time
Sections include Primary, Secondary, Anti-segment, Hypotheses and Implications.
Write · Step 6: segment map

From the official docs

Permissions

Low risk

developer-segmentation is planning instructions with no scripts, and it may save notes to devrel-context.md. Our advice: check that file before you commit it.

What it can do

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

Watch out for

It may save notes to devrel-context.md
SKILL.md tells Claude to keep task and project context in devrel-context.md when memory lives in a file, or in the memory system your tool already uses. Check the file before you commit it. github.com
It may browse the web for sizing data
SKILL.md says that if Claude can browse, it should assemble size estimates from developer-population surveys, practitioner surveys, language rankings, forge reports and registries. Browsing depends on your tool. github.com
The whole-set install adds 93 skills, 14 with scripts
The README says to install every skill. The git tree has 93 skill folders and 14 of them hold .py or .sh files. The tree holds no hooks, agents or MCP config files. github.com

Technical details

Turning on read-only	SKILL.md describes no read-only mode.
Sign-in and keys	SKILL.md names no account, key or token.
Scopes	Claude writes the plan or report in the conversation May save notes to devrel-context.md when memory lives in a file May browse the web for market-size sources if your tool allows it

Questions

What does developer-segmentation do?

It makes Claude split a developer audience into three to five named, sized and ranked segments. It ends with one primary segment, one secondary and a written anti-segment.

How do I install it?

Use the install box at the top. The README says to install every skill in the repo because the skills point to each other, so the box shows whole-set routes.

Does it search the web for market sizes?

Only if your tool lets Claude browse. SKILL.md says to assemble estimates from independent surveys and registries if it can browse, and to size from your own data and mark external figures inferred if it cannot.

Can it map the developer journey?

No. SKILL.md says the journey map is a different skill, developer-journey-map.

What if the developer is not the buyer?

That is a listed trigger. Step 4 splits each segment into user, champion, approver and buyer.

Is it safe to install?

The skill bundles no scripts. Product and customer details you share stay in your conversation, and Claude may save notes to a devrel-context.md file. The whole-set install adds 93 skills, some with scripts.

Information

updated Nov 2, 2026

Repository: samber/developer-relations-skills
Folder: skills/developer-segmentation

samber/developer-relations-skills skills.sh

Sources

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

Show all 6

README · github.com
marketplace.json · github.com
plugin.json · github.com
developer-segmentation SKILL.md · github.com
LICENSE · github.com
skills.sh listing · skills.sh