event-speaker-experience SKILL.md skillA
event-speaker-experience from samber/dev-event-organizer-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add samber/dev-event-organizer-skills/event-speaker-experience@v1.2.1Pins v1.2.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- samber/dev-event-organizer-skills
- Path
skills/event-speaker-experience/SKILL.md- Versions recorded
- 5
- Latest version
- v1.2.1, committed Oct 25, 2026
- First version recorded
- Aug 28, 2026
- Size
- 28,159 bytes
- Repository stars
- 4
- License
- MIT
Run the speaker-side experience from the moment a speaker confirms through to the thank-you after their talk - collecting bio, headshot, A/V needs and travel details against a deadline ladder, a single named point of contact, the pre-event briefing and slide deadline, tech check and green room, documented recording consent and its per-format opt-out asymmetry, and post-event follow-up. Use whenever the user mentions what to send an accepted speaker, a green room, speaker travel or hotel, a…
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
# Event Speaker Experience
You take care of a speaker who has already said yes. Your input is the acceptance email `samber/dev-event-organizer-skills@event-talk-selection` has just sent, and specifically its closing line: "What you get: {the perks exactly as the call stated them}. What we need next: {confirmation, bio, headshot, slide deadline, travel or A/V details}." You start there.
Your output is a speaker who arrives knowing what happens when, delivers without an equipment surprise, agreed in writing to whatever was recorded, and hears from you after the event.
What this skill does not do:
- **Promise terms**: you do not decide what a speaker is promised. `samber/dev-event-organizer-skills@event-cfp-design` set the perks and left the honorarium open. You deliver whatever was promised and never invent a figure nobody confirmed.
- **Decline or waitlist messages**: not your ground - that belongs to `samber/dev-event-organizer-skills@event-talk-selection`, and those speakers never enter your scope.
- **Sourcing, inviting or selecting**: you do none of it.
…Read the whole file at its exact version.
How to install
mdr add samber/dev-event-organizer-skills/event-speaker-experience@sha256:9ac7f305be2cb362The line at the top of this page pins the label v1.2.1, 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_ixv7p46ocmaghiaz)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 28, 2026 and Oct 25, 2026, about one every 15 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.2.1 latest | 2026-10-25 | 62b088f | 28,159 B | A | view · diff |
| v1.2.0 | 2026-10-21 | 9c09581 | 28,125 B | A | view · diff |
| v1.1.0 | 2026-10-12 | 7368d8a | 29,306 B | A | view · diff |
| v1.0.0 | 2026-08-28 | 27725af | 24,995 B | A | view · diff |
| v1.0.0 | 2026-08-28 | 95c413e | 24,994 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 (28159 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/dev-event-organizer-skills · 4 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ixv7p46ocmaghiaz GET https://markdownregistry.com/api/v1/resolve?ref=samber/dev-event-organizer-skills/event-speaker-experience GET https://markdownregistry.com/api/v1/blob/9ac7f305be2cb36288257a8b521dc37baaf55ed4566427921ce91f96e55e2f69
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.