devrel-strategy skill (samber): design a developer relations program from the top

Builds a DevRel charter: the funded driver, two goals, pillar mix, audience, build-or-buy calls, staffing order and refused list.

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

devrel-strategy designs a developer relations program from the top and returns one artefact: a DevRel charter of one to two pages. After an interview of up to fourteen questions, Claude names the business driver that funds the program, picks two primary goals and one secondary, ranks program shapes, decides build or buy for each bet and sequences staffing. The charter has twelve short headings, including a written list of what the program refuses to do. It produces decisions, not the talks, posts, docs or events themselves.

Good for

DevRel leads and first hires defining what the program is for
Founders deciding whether to fund DevRel at all
Managers who must justify the program to an executive

Install devrel-strategy

Claude Code

Copy this prompt.

Install the devrel-strategy 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 (the kickoff skill's text says 65). Fourteen of them bundle .py or .sh files; devrel-strategy 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

Designs a company's developer relations program from the top - the business driver that funds it, the two goals it is allowed to serve, the pillar mix (advocacy, marketing, enablement, community) for its stage, audience priority, build-vs-buy per bet, staffing sequence, and a written refused list. Use whenever someone asks whether to start doing DevRel, what a new devrel program should do first, why devrel work is busy but not landing, how to justify the program to an exec, which pillar deserves the next investment, who to hire next, or whether to outsource content, events or community - even if they never say "strategy". Not the first-90-days plan - use samber/developer-relations-skills@developer-relations-kickoff. Not metrics, org chart or budget math.

Sections in SKILL.md

Invocation
Interview
Sourced figures, self-set baselines
Step 1 - Establish the position before proposing anything
Step 2 - Name the funded driver, then pick at most two goals
Step 3 - Brainstorm program shapes, then rank them
Step 4 - Set audience priority
Step 5 - Decide build versus buy per bet
Step 6 - Sequence the staffing
Step 7 - Write the charter and validate it section by section
Position CORE summary, lifecycle stage, what changed since last time
Driver the funded reason, in the funder's words, and its owner
Goals 2 primary + 1 secondary, each pinned to a journey step
Audience primary path and segment; who is not served yet
Pillar mix where effort goes, and which pillar is deliberately starved
Bets 3-5 bets: goal served, owner, signal, review date

Key facts

Author: Samuel Berthe (named in SKILL.md metadata and the plugin manifest)
License: MIT (LICENSE file, SKILL.md and plugin.json agree)
Installs on skills.sh: 12,827 (Nov 2, 2026)
GitHub stars: 8 for the whole samber/developer-relations-skills repo (Nov 2, 2026)
Last repo commit: Nov 1, 2026
Audits on skills.sh: Gen Agent Trust Hub: pass, Socket: pass, Snyk: pass
What it includes: 5 files in the git tree: SKILL.md, 3 reference files and evals/evals.json. No scripts.
Part of: The developer-relations-skills plugin: 93 skill folders in the git tree
Works in: Claude Code and Claude.ai plugin marketplaces, Codex, Cursor and Gemini CLI, as the README documents

What it includes

Up to 14 questions; 12 to 14 (date, one-off or compounding, effort) reorder menus
Covers product, buyer, funding driver, stage, who does DevRel work today, what exists, what was tried, off-limits and budget owner.
Read · Interview
Maps community, organization, relationships and ecosystem
Done before anything is proposed.
Read · Step 1: position
Names one funded driver and at most two primary goals plus one secondary
Seven drivers: developer adoption, sales enablement, developer enablement, product input, ecosystem and partnerships, contributor community, employer brand.
Write · Step 2: driver and goals
Builds 2-3 whole-program candidates and ranks the survivors
Shapes the answers rule out are deleted from the candidate set, not ranked last.
Write · Step 3: program shapes
Individual-developer adoption versus company adoption
Decides what to invest in first.
Write · Step 4: audience priority
Keeps judgment and voice in-house; rents volume, not credibility
Applied per bet.
Write · Step 5: build versus buy
Seed, grow and scale stages with a trigger for each next hire
Scaling adds leverage before headcount.
Write · Step 6: staffing sequence
Twelve headings, validated section by section
Position, driver, goals, audience, pillar mix, bets, build versus buy, staffing, refused, open questions, exec narrative and review.
Write · Step 7: the charter

From the official docs

Permissions

Low risk

devrel-strategy is interview and 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 DevRel definitions
SKILL.md says to check the Developer Relations Foundation site (dev-rel.org) for canonical definitions if the agent can browse. Browsing depends on your tool's setup. 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. This skill bundles no scripts and 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 a charter in the conversation Company, budget and team details you share go into the conversation Writes devrel-context.md when memory lives in a file

Questions

What does devrel-strategy do?

It designs a company's developer relations program from the top. The result is a one-to-two page charter naming the funded driver, the goals, the pillar mix, the audience, the bets, the staffing order and what the program will not do.

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. The box shows the whole-set routes the README documents.

Can it tell me if we should do DevRel at all?

Yes, that is one of its listed triggers. SKILL.md gives "Should we even be doing DevRel, and what would we do first?" as an example and starts at the interview however narrow the question sounds.

How is it different from devrel-budget-allocation?

devrel-strategy decides what the program is for. devrel-budget-allocation splits money and hours across the pillars the strategy names, and stops if no funded driver and goal exist.

Does it write my talks, posts or events?

No. SKILL.md says it produces the decisions, never the talks, posts, docs or events themselves.

Is it safe to install?

The skill bundles no scripts. What you tell Claude about your company goes into your conversation. The whole-set install adds 93 skills, some of which bundle scripts; the permissions section has the count.

Information

updated Nov 2, 2026

Repository: samber/developer-relations-skills
Folder: skills/devrel-strategy

samber/developer-relations-skills skills.sh

Sources

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

Show all 4

devrel-strategy SKILL.md · github.com
README · github.com
LICENSE · github.com
devrel-budget-allocation file · github.com