PlugWiki

developer-meetup-program skill (samber): design a recurring developer meetup

Designs a recurring developer meetup or user group: charter, format, cadence, speaker pipeline, sponsors and a health scorecard.

Installs
12.7K
on skills.sh
Stars
7
on GitHub
Files
8
besides SKILL.md
Updated
Nov 2026
last repo commit

developer-meetup-program makes your agent plan a meetup that still runs in eighteen months. It writes a one-page charter, picks a host model and format, sets a cadence, builds a speaker pipeline two editions ahead, and sets sponsor and no-show rules.

It triggers on starting a meetup, falling attendance, finding speakers, a venue or pizza sponsor, RSVPs who never show, or handing the group over. It covers independent, vendor-backed and company-staffed groups. The folder holds SKILL.md and eight reference files and bundles no scripts.

Good for

  • Developers starting a local meetup or user group
  • Organizers whose attendance is falling
  • Company DevRel staff running a vendor-backed chapter
  • Solo organizers who need co-organizers before they burn out

Install developer-meetup-program

Claude Code

  1. 1

    Copy this prompt.

    Install the developer-meetup-program 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. 2

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

The README recommends installing the whole collection because its skills reference each other, and developer-meetup-program names other skills in the collection to hand work to. The whole-collection routes add all 93 skills in the repo (counted from the git tree); the repo holds no hooks, agents, commands or MCP server files, and 14 of its skills bundle a script. Pick one route per agent.

From the project README. Source.

What's in the skill

When it loads

Designs and runs a recurring developer meetup or user group - purpose and host model, format menu, cadence, a standing speaker pipeline, in-kind venue and food sponsors with their conduct limits, no-show planning, the attendee-to-co-organizer ladder, and a health scorecard. Use whenever someone mentions starting a developer meetup or user group, dying meetup attendance, finding meetup speakers, getting a venue or pizza sponsor, how often to meet, RSVPs who never show, or handing the meetup over - even if they only say "we want to do local events". Covers independent, vendor-backed and company-staffed groups. Not for speaking at a conference - use samber/developer-relations-skills@conference-cfp-submission.

Sections in SKILL.md

  1. How to read the numbers
  2. Interview
  3. Step 1 - Write the charter before booking anything
  4. Step 2 - Host model and audience
  5. Step 3 - Format and rhythm
  6. Step 4 - Build a speaker pipeline, not a monthly panic
  7. Step 5 - Venue, food and sponsors
  8. Step 6 - Promotion and the no-show plan
  9. Step 7 - Retention, the ladder, and succession
  10. Deliverable
  11. Measurement
  12. Pass threshold
  13. Failure modes
  14. References

Key facts

Author
Samuel Berthe (samber)
License
MIT (LICENSE file, SKILL.md, plugin.json and README all say MIT)
Installs on skills.sh
12,692 (as of Nov 2, 2026)
GitHub stars
8 for the whole collection repo (Nov 2, 2026)
Last commit
Nov 1, 2026 (whole repo)
skills.sh audits
Gen Agent Trust Hub pass, Socket pass, Snyk pass
What is inside
9 files including SKILL.md: 7 reference files and evals/evals.json
Version in SKILL.md
1.0.2
Needs
SKILL.md lists nothing to install
Works in
Claude Code, Claude.ai (plugin marketplace), Codex, Cursor, Gemini CLI and other Agent Skills-compatible tools
Part of
The developer-relations-skills plugin (one plugin in marketplace.json)
Collection size
93 skills in the repo (counted from the git tree)

What it includes

  • Asks twelve questions one at a time; questions 1 to 7 gate the design.

    If the answer to the organizer count is "just me", SKILL.md says a solo group is one job change from dead and to recruit a second organizer within three editions.

    Interview

  • Writes a one-page charter with one primary outcome.

    Covers who the room is for, a typical evening, frequency, who decides and what the group refuses to do.

    Step 1 - Charter

  • Names the host model and whether the room attends on work time.

    Independent vendor-neutral group, vendor-backed volunteer chapter, or company-staffed series.

    Step 2 - Host model and audience

  • Ranks five formats and fixes a recurring slot.

    Anchor plus lightning, study group, two-talk classic, open space, hands-on workshop. Cadence uses CNCF thresholds, such as more than 90 days between events marking a chapter inactive.

    Step 3 - Format and rhythm

  • Builds a standing call for proposals and a board of speakers two editions ahead.

    Asks for the title, takeaway and slides in advance to avoid a talk that turns out to be a pitch.

    Step 4 - Speaker pipeline

  • Sets sponsor stage-time limits and two absolute rules.

    Never a speaking slot for money and never the attendee list. The first rule is quoted from DevOpsDays: "no speaker spots can be bought by sponsors: not ever - period."

    Step 5 - Venue, food and sponsors

  • Plans on roughly 30% no-shows, overbooks, waitlists and counts heads at the door.

    The 30% figure is CNCF's planning number; SKILL.md says to calibrate on your own door count after three editions.

    Step 6 - Promotion and no-show plan

  • Moves people from attendee to regular, lightning speaker, volunteer and co-organizer.

    Also sets shared account ownership and a written run-of-show for succession.

    Step 7 - Retention, ladder and succession

  • Produces a charter, a three-edition plan, a speaker board, a log and a scorecard.

    A six-item pass threshold decides whether the program is healthy.

    Try: “we want to start a Rust meetup in Lyon”

    Deliverables

From the official docs

Permissions

Low risk

The agent can save notes about your company or project to a file called devrel-context.md, so check that file before you commit or share the folder.

What it can do

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

Watch out for

  • Sponsor and venue contacts may be saved to memory

    SKILL.md says to store the venue and sponsor contacts with the charter and edition log when persistent memory is available. Our advice: check what was saved before you commit or share the folder. github.com

  • It may keep notes in devrel-context.md

    SKILL.md tells the agent to store a few details about the current task or project, and to use a file called devrel-context.md when its memory lives in a file. Our advice: open that file before you commit or share the folder. github.com

  • The plugin route installs the whole collection

    The README's plugin and extension routes add every skill in the repo; its git tree holds 93. The repo has no hooks, agents, commands or MCP server files, and 14 of its skills bundle a script. Our advice: use the skills CLI command for this skill if you want only it. github.com

Security advisories

No published security advisories as of Nov 2, 2026.

Technical details
Turning on read-onlySKILL.md describes no read-only mode.
Scopes

  • May store the charter, venue and sponsor contacts and edition log in devrel-context.md when its memory lives in a file

Questions

How do I install developer-meetup-program?

The README says to install every skill in the collection, because its skills reference each other. In Claude Code that is the plugin route in the install box above, which adds all 93 skills in the repo. The skills CLI can add just this one. Our advice: pick one route per agent.

What do I get at the end?

Five deliverables: a program charter, an edition plan three editions deep, a speaker pipeline board, an edition log skeleton and a scorecard baseline. SKILL.md marks anything beyond edition three as provisional.

Which meetup format does it recommend?

For a new or rebuilding group, anchor plus lightning: one 25-minute speaker plus 5-minute slots. SKILL.md ranks it first on both efficiency and value because it needs one confirmed speaker and turns lightning speakers into later anchors. The ranking is labelled its own judgement, not a sourced finding.

How many no-shows should I plan for?

About 30%. SKILL.md gives that as CNCF's published planning figure and calls the 40 to 50% often repeated for free evening events folklore. It tells you to replace it with your own measured rate after three editions.

developer-meetup-program vs conference-cfp-submission?

Use this skill to run a recurring local group and conference-cfp-submission to get a talk accepted at someone else's event. SKILL.md says "Not for speaking at a conference", and the README describes the other skill as turning a talk idea into a submission-ready proposal.

Does developer-meetup-program need an API key, and where does it work?

SKILL.md names no API key, account or environment variable. The README documents installs for Claude Code, Claude.ai (add the repo as a plugin marketplace), Codex, Cursor, Gemini CLI and any Agent Skills-compatible tool through the skills CLI. The install box has the steps for each.

Is developer-meetup-program safe to install?

It is instructions plus seven reference files, and the folder bundles no scripts. SKILL.md says to store the charter, the venue and sponsor contacts and the edition log in memory if available, with devrel-context.md as the file when memory is a file. Our advice: do not put attendee emails or private sponsor contacts in a folder you commit to a public repo.

Information

updated Nov 2, 2026

Repository
samber/developer-relations-skills
Folder
skills/developer-meetup-program

samber/developer-relations-skillsskills.sh

Sources

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

Show all 2
  1. developer-relations-skills README · github.com
  2. developer-meetup-program SKILL.md · github.com

Updated Nov 2, 2026.