developer-booth-playbook SKILL.md skillA
developer-booth-playbook 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-booth-playbook@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-booth-playbook/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Oct 31, 2026
- Size
- 19,753 bytes
- Repository stars
- 8
- License
- MIT
Writes an exhibiting company's own playbook for an in-person booth at a developer conference: who works it and how many per shift, roles, how staff open and qualify a conversation, how each lead is captured and graded, swag and giveaway policy, and the exhibitor rules to obey. Use whenever a team is sending people to work a booth at KubeCon, re:Invent, PyCon, DevOpsDays or any developer event and asks about booth staffing, shifts, badge scanning, booth lead qualification, booth swag, a booth…
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 Booth Playbook You write the floor plan for a booth a company already bought: who stands in it, when, what they say, what they write down, and what they hand out. A developer audience judges the company by the person in the booth. Every rule below protects one unit: the **qualified conversation** (grade A below) - someone with the problem, who agrees to a named next step. Badge scans, swag handed out and foot traffic are activity counts, never the goal. Route elsewhere when this is the wrong table: - Which event, which tier, which activation, the ROI threshold → `samber/developer-relations-skills@developer-event-sponsorship`. This skill starts once the booth is bought. - The demo loop, its restore points and failure plan → `samber/developer-relations-skills@developer-live-demo-design`. - Everything after the hall closes: sequences, nurture, conversion → `samber/developer-relations-skills@developer-event-followup`. - Dinners and invite-only side events → `samber/developer-relations-skills@devrel-field-events`. …
Read the whole file at its exact version.
How to install
mdr add samber/developer-relations-skills/developer-booth-playbook@sha256:72dc690d07f53513The 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_3n434jx22uowux46)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 31, 2026.
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 (19753 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_3n434jx22uowux46 GET https://markdownregistry.com/api/v1/resolve?ref=samber/developer-relations-skills/developer-booth-playbook GET https://markdownregistry.com/api/v1/blob/72dc690d07f53513373119f4b29532ffa4b6d5e548dfbbee7f294d02d46e78c5
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.