developer-champions Skill (samber): Ambassador Program

Makes Claude design an unpaid developer champions or ambassador program, from selection criteria to renewal and exit.

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

developer-champions interviews you, then designs an unpaid, perks-only champions program in eight steps. It checks readiness, picks an intake model, writes public selection criteria, sets obligations as behaviour and perks as access, fixes a term with renewal and exit, runs a compliance pass, defines the operating rhythm and sets a cohort scorecard.

You get two artefacts: a charter with 12 answers and a public page. SKILL.md says it is not for paid creator, affiliate or revenue-share partnerships. It bundles 3 reference files and an evals file, and no scripts.

Good for

Community managers who run or plan an ambassador program
DevRel leads rewarding top community members with access, not pay
Teams whose ambassador program went quiet and need a reset

Install developer-champions

Claude Code

Copy this prompt.

Install the developer-champions 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-champions 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 an unpaid, perks-only developer champions or ambassador program end to end - readiness check, intake model, published selection criteria, behaviour-based obligations, an access-first perk ladder, fixed terms with renewal and alumni status, and a cohort scorecard. Use whenever the user mentions an ambassador or champions program, MVP-style recognition, community heroes, "how do we recognise our top community members", what perks ambassadors should get, an ambassador program that went quiet, or removing an inactive champion - even if they never say "champion". Not for paid creator, affiliate or revenue-share partnerships. For measuring the community itself use samber/developer-relations-skills@developer-community-health.

Sections in SKILL.md

Interview
Step 1 - Check readiness before designing anything
Step 2 - Pick the intake archetype
Step 3 - Write the selection criteria in public
Step 4 - Set obligations as behaviour, perks as access
Step 5 - Fix the term, then design renewal and exit
Step 6 - Run the compliance pass
Step 7 - Define the operating rhythm
Step 8 - Set the bar and measure the cohort
What gets handed back
Variants by audience
Failure modes
Reference

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,392 (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: 5 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

Questions 1-8 gate the design; an archetype is not proposed before they are answered
Read · Interview
Runs gates and reports each as pass or fail
Read · Step 1: readiness check
Four intake shapes ranked by value per unit of effort
Sourced examples from CNCF, HashiCorp, MongoDB, Elastic, Twilio and GitHub Stars are in a reference file.
Write · Step 2: intake archetype
Uses four member levels and writes selection criteria in public
Write · Step 3: public criteria
Asks for conduct, not output, and rewards with access
Write · Step 4: obligations and perks
Gives the term an end date on day one and designs alumni status
Write · Step 5: term, renewal, exit
Questions to answer before publishing; counsel where money is involved
Read · Step 6: compliance pass
Fixes the recurring beats and names an owner for each
Write · Step 7: operating rhythm
A quarterly scorecard with self-set thresholds
Write · Step 8: cohort scorecard
Two artefacts, validated section by section
The charter follows the 12-question template in references/charter-template.md.
Write · Handback: charter and public page

From the official docs

Permissions

Low risk

developer-champions 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
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

Questions

What does developer-champions do?

It makes Claude design an unpaid developer champions or ambassador program. It covers selection criteria, perks, a fixed term, renewal and exit, and a cohort scorecard.

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.

Can it design a paid ambassador or affiliate program?

No. Its description says it is not for paid creator, affiliate or revenue-share partnerships.

What if my ambassador program already went quiet?

That is a listed trigger. The description names "an ambassador program that went quiet" and removing an inactive champion.

How do I measure the community itself?

SKILL.md points to the developer-community-health skill in the same repo for that, and keeps this skill to the champions program.

Is it safe to install?

The skill bundles no scripts. What you tell Claude about your community stays 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-champions

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-champions SKILL.md · github.com
LICENSE · github.com
skills.sh listing · skills.sh