developer-event-sponsorship Skill (samber): Event Budget

Makes Claude plan which developer events to sponsor, at what tier, with what activation, and how to prove it paid off.

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

developer-event-sponsorship interviews you, then works through eight steps. It fixes one primary objective, qualifies each candidate event with evidence from the organizer, builds a portfolio and picks one, chooses a model and tier, helps you negotiate, designs the on-site activation, builds the measurement plan before you sign, and sets a review.

The output is a portfolio plan for the year and a one-pager per event. SKILL.md says not to use it for running your own event, getting a talk accepted, or sponsoring open-source projects. It bundles 4 reference files and an evals file, and no scripts.

Good for

DevRel leads deciding where the event budget goes
Developer marketers weighing a booth or tier quote
Founders asking whether a conference sponsorship is worth it

Install developer-event-sponsorship

Claude Code

Copy this prompt.

Install the developer-event-sponsorship 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-event-sponsorship 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

Builds a developer-event sponsorship plan - which conferences, meetups and hackathons to sponsor, at which tier, with which on-site activation, and how to prove the money worked. Use whenever a DevRel lead, developer marketer or founder mentions sponsoring a conference, booth cost, a sponsorship tier or package negotiation, splitting an event budget across events, hackathon sponsorship, or event ROI - even if they only ask "is this booth worth it". Do NOT use for organizing your own event (samber/developer-relations-skills@developer-meetup-program), getting a talk accepted (samber/developer-relations-skills@conference-cfp-submission), or sponsoring open-source projects.

Sections in SKILL.md

Interview
Step 1 - Fix one primary objective
Step 2 - Qualify every candidate event
Step 3 - Brainstorm the portfolio, then choose one
Step 4 - Choose the model and the tier
Step 5 - Negotiate
Step 6 - Design the on-site activation
Step 7 - Build the measurement plan before signing
Step 8 - Review, then renew, renegotiate or drop
Pass threshold
Invocation examples
Failure modes
Output shape
References

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.6 (SKILL.md metadata)
Installs on skills.sh: 12,385 (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: 6 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 objective, budget and staffing ceiling are known
Read · Interview
Fixes one primary mandate for the sponsorship
Write · Step 1: primary objective
Asks organizers for evidence before any pricing
The weighted scorecard is in references/event-scorecard.md.
Read · Step 2: qualify events
Sizes the envelope, brainstorms portfolios and chooses one
Write · Step 3: portfolio
Reads three contract clauses before the price
Read · Step 4: model and tier
Where packages can move: early, multi-event, multi-year and off-peak deals
Write · Step 5: negotiate
Two or three activation options with trade-offs, one recommended
Write · Step 6: on-site activation
Costs the sponsorship in full and sets the plan before signing
Write · Step 7: measurement plan
Review within two weeks, then renew, renegotiate or drop
Write · Step 8: review
A year portfolio plan table and a per-event one-pager
Write · Output: plan and one-pager

From the official docs

Permissions

Low risk

developer-event-sponsorship 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-event-sponsorship do?

It makes Claude plan a developer-event sponsorship budget. It covers which events, which tier, what to do on site, and how to measure the result.

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 tell me if a booth is worth it?

Yes, that is a listed trigger ("is this booth worth it"). SKILL.md says a single-event question gets the interview, then steps 1-2 on that event, and an answer with a threshold or a decline, never a maybe.

Can I use it to run my own meetup?

No. Its description says not to use it for organizing your own event and names developer-meetup-program for that.

Does it cover getting a talk accepted?

No. Its description names conference-cfp-submission for that.

Is it safe to install?

The skill bundles no scripts. Budget and event 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-event-sponsorship

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