developer-champions

Designs unpaid developer champions and ambassador programs with selection criteria, perks, terms, and scorecards.

2|Updated Sep 6, 2026
One-click install
npx skills add https://github.com/samber/developer-relations-skills --skill developer-champions-samber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: developer-champions
Source: https://github.com/samber/developer-relations-skills/tree/main/skills/developer-champions
Command: npx skills add https://github.com/samber/developer-relations-skills --skill developer-champions-samber

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Champions and ambassador programs fail in two predictable ways: launching before a community exists to select from, and shipping a title with no term, renewal, or exit so the roster becomes a stale graveyard. This Skill designs the full program lifecycle end to end, including the exit, before anything launches. ## Core Features & Use Cases - Readiness gating and archetype selection: Checks candidate pool, owner hours, and feedback capacity, then ranks four intake shapes (invite-only circle, award, application cohort, points ledger) by efficiency, value, effort, and compliance cost. - Program design artifacts: Produces published selection criteria with anti-signals, behaviour-based obligations, an access-first perk ladder, dated terms with renewal and alumni status, a compliance pass covering gift limits, FTC disclosure, and NDA scope, plus a quarterly scorecard with kill criteria. - Use Case: A community manager with 1,400 active forum members, 8 hours a month, and a conference announcement in six weeks gets a ranked archetype shortlist, a first-cohort plan sized to their hours, and a charter validated section by section before any public page is written. ## Quick Start Ask the assistant to design an ambassador program for your developer community, describing your community size, available hours, and timeline.

Frequently Asked Questions about developer-champions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a developer ambassador or champions program?

Start with a readiness check: at least roughly 10 nameable qualifying candidates, a named owner with recurring hours, and an access perk to offer. Then pick an intake archetype, publish selection criteria, set behaviour-based obligations, and fix a dated term with renewal and alumni exit before launching.

What perks should developer ambassadors get?

Rank perks access-first: roadmap reviews, release briefings, and a private engineer channel beat platform, skill-building, funding, and status objects like swag. Refuse commissions, content quotas, blanket NDAs, and generic discount codes, which damage member credibility or create legal exposure.

How long should a champion or ambassador term be?

Use a dated term fixed on day one: roughly 12 months for a vendor program and 24 for a foundation-scale one, both self-set defaults. Judge renewal on the last term only, give at least a month of notice, offer pauses for life events, and make alumni a first-class status.

When should I not launch a public champions program?

Do not launch publicly with fewer than roughly 10 nameable qualifying candidates; a tiny public roster reads as a failed program permanently. Also avoid it without a code of conduct, a feedback listener on the product side, or any access perk beyond swag.

Can I pay ambassadors a referral commission or require monthly blog posts?

No. Commissions read as multi-level marketing and destroy member credibility; run paid motions as a separate contracted program. Content quotas convert recognition into unpaid work, creating both community damage and employment-classification exposure.

How do I measure whether a champions program is working?

Report a quarterly scorecard with self-set bars: at least 60% quarterly active share, 70% renewal acceptance, responses within 5 business days, and at least one product decision traceable to champion input. Write kill criteria before launch and avoid per-member revenue attribution the data cannot support.