event-attendee-email-sequences SKILL.md skillA
event-attendee-email-sequences 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-attendee-email-sequences@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/dev-event-organizer-skills
- Path
skills/event-attendee-email-sequences/SKILL.md- Versions recorded
- 2
- Latest version
- v1.0.0, committed Aug 25, 2026
- First version recorded
- Aug 25, 2026
- Size
- 31,129 bytes
- Repository stars
- 4
- License
- MIT
Design and write the attendee email arc for a technical event - the sequence, the cadence, and the actual copy. Covers the dated arc from announcement to post-event follow-up, a sourced reminder cadence with per-segment caps rather than a SaaS drip, the know-before-you-go email, role and registration-state segmentation, consent and list hygiene, and a humanizer pass before anything sends. Use whenever asked to write an event announcement email, registration confirmation, week-before or…
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 Attendee Email Sequences You design and write the emails a technical event sends its attendees. Your inputs arrive fixed from siblings: the campaign calendar and email's channel weight from `samber/dev-event-organizer-skills@event-marketing-plan`, the early-bird and price-tier cutoffs from `samber/dev-event-organizer-skills@event-ticket-pricing`, and the on-site facts from `samber/dev-event-organizer-skills@event-attendee-experience`. Your output is a dated send map plus the copy for every email on it. You never move a date to make an email land better, never set a price cutoff, and never invent what the day-of experience looks like. Your audience is the general attendee only - speakers and sponsors have their own comms, owned by `samber/dev-event-organizer-skills@event-speaker-experience` and `samber/dev-event-organizer-skills@event-sponsor-fulfillment`. **The sharpest boundary is no-shows.** A reminder sequence exists to fight them. - **You own:** the sequence's design and copy, in full. - **`samber/dev-event-organizer-skills@event-no-show-management` owns:** the no-show _problem_ itself - overbooking ratios, waitlists, paid deposits and seat-release flows. …
Read the whole file at its exact version.
How to install
mdr add samber/dev-event-organizer-skills/event-attendee-email-sequences@sha256:c25cb0724700d6ceThe 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_t7ynuk7dtwu2ag7v)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Aug 25, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-08-25 | c04431d | 31,129 B | A | view · diff |
| v1.0.0 | 2026-08-25 | d1f3b31 | 31,128 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 (31129 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_t7ynuk7dtwu2ag7v GET https://markdownregistry.com/api/v1/resolve?ref=samber/dev-event-organizer-skills/event-attendee-email-sequences GET https://markdownregistry.com/api/v1/blob/c25cb0724700d6ce8e9e1c1e5d70a0210aa680899a3f8358333cff8d740b61c6
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.