developer-event-followup SKILL.md skillA
developer-event-followup from samber/developer-relations-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add samber/developer-relations-skills/developer-event-followup@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- samber/developer-relations-skills
- Path
skills/developer-event-followup/SKILL.md- Versions recorded
- 2
- Latest version
- v1.0.0, committed Oct 31, 2026
- First version recorded
- Oct 31, 2026
- Size
- 23,803 bytes
- Repository stars
- 8
- License
- MIT
Plans what a company does after an in-person developer event it exhibited at, spoke at, sponsored or ran a workshop at: sorting badge scans, booth notes, raffle entries, rosters and hackathon submissions, deciding who may be emailed and for what, writing the messages, routing contacts to product, community or sales, and measuring the cohort. Use whenever someone asks what to do with conference leads or badge scans, how to follow up after a hackathon or workshop, whether they can email the…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Developer Event Follow-up You turn the people a company met at a developer event into users, community members and, when they asked for it, sales conversations, without turning them into spam recipients. A badge scan records presence, not intent. Every rule below protects two things: the promise staff made aloud when they took someone's details, and the reputation the company brings to the next edition. On Hacker News, developers name "people who scanned my badge at a conference" as a spam source their filters miss; a follow-up that ignores what was discussed costs more trust than silence. Route elsewhere when this is the wrong table: - Staffing the booth, grading conversations, the consent line said at capture → `samber/developer-relations-skills@developer-booth-playbook`. That skill hands its graded log here. - Which event to buy, the cost-per-conversation threshold and the renew/drop verdict → `samber/developer-relations-skills@developer-event-sponsorship`. This skill supplies the outcome data that verdict reads. - Webinar registrants and the webinar's sales handoff → `samber/developer-relations-skills@devrel-webinar-program`. …
Read the whole file at its exact version.
How to install
mdr add samber/developer-relations-skills/developer-event-followup@sha256:ca533261eabe6e65The line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_de54yf5tbduuydqc)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Oct 31, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-10-31 | 734f50a | 23,803 B | A | view · diff |
| v1.0.0 | 2026-10-31 | 0257e24 | 23,807 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (23803 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
samber/developer-relations-skills · 8 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_de54yf5tbduuydqc GET https://markdownregistry.com/api/v1/resolve?ref=samber/developer-relations-skills/developer-event-followup GET https://markdownregistry.com/api/v1/blob/ca533261eabe6e657ac30ca53c83cd06a55f0a467b6bfb01eb52b8027c5dbd18
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.