Skills

Agent Skills for Event Planning: From Guest Lists to Follow-Up Emails

Turn your event checklist into a reusable Claude skill that handles guest lists, invitations, RSVPs, and follow-ups the same way every time.

Event planners preparing a rustic venue with elegant table settings
Image: Pixabay / Pixabay Content License

Key Takeaways

  • An event-planning skill is a SKILL.md file that chains five jobs: clean the guest list, draft invitations, track RSVPs, build reminders, and write follow-ups.
  • The description field is the trigger: write it with the exact phrases you will actually type.
  • Keep data in reference files and never let the skill invent a guest, an email, or an RSVP status.
  • Install separately on claude.ai and Claude Code; skills do not sync across surfaces.
  • Test on a past event before trusting the skill with a real one.

An agent skill for event planning is a reusable set of instructions telling Claude how to run your event workflow the same way every time — from cleaning the guest list to sending invitations, tracking RSVPs, and writing follow-ups. Build it once as a SKILL.md file, install it in Claude, and a single prompt runs the whole routine.

Small businesses run events constantly: launches, open houses, client nights, workshops. Each brings the same repetitive work: a guest list in a spreadsheet, invitations sent one by one, RSVPs scattered across email and chat, and a follow-up written at midnight — or not at all. A skill does not replace your judgment — it takes the repeatable parts off your plate.

What the skill actually does

Five jobs, chained together. It cleans the guest list — flagging duplicates, missing emails, contacts without a first name — and asks what to do instead of guessing. It drafts invitations from your template, in your brand voice, with date, time, venue, and RSVP link. It tracks RSVPs and drafts a polite nudge for no-replies. It builds a day-of checklist. After the event, it drafts thank-you emails, one version for attendees and one for no-shows. No code needed: a basic skill is a folder with a Markdown file, plus the templates you already have.

Prerequisites

  • A claude.ai paid plan (Pro, Max, Team, Enterprise) with code execution enabled, or Claude Code.
  • Your guest list as a spreadsheet or CSV: first name, last name, email, company.
  • One invitation template and one follow-up email you have used before.
  • About one hour to build, then 15 minutes per event.

Step 1: Map the workflow on paper

Write down the five jobs in your own words, in order, with the decisions at each step — for example: “Remove anyone who unsubscribed last year. Never add a guest without an email address. Invite three weeks before, remind one week before, nudge two days before.” This page is the skill — SKILL.md is just a typed-up version of it. If you cannot describe a step in one sentence, it is too vague — Claude will guess.

Step 2: Create the folder and the frontmatter

Every skill is a folder containing a SKILL.md file — create one named event-planning. The file starts with YAML frontmatter with two required fields. Per Anthropic’s documentation, the name is at most 64 characters — lowercase, numbers, and hyphens only, without the words “anthropic” or “claude” — and the description is at most 1,024 characters, saying what the skill does and when to use it.

---
name: event-planning
description: Runs our event workflow: cleans guest lists, drafts invitations, tracks RSVPs, writes follow-ups. Use when the user mentions planning an event, guest lists, invitations, or event follow-up.
---

# Event Planning

## Workflow
1. Read guests.csv. Flag duplicates, missing emails, missing first names. Ask the user what to do with each.
2. Draft the invitation from templates/invitation.md with the event name, date, time, venue, and RSVP link.
3. Track RSVPs in a table: attending, declined, no reply. Draft a polite reminder for no-replies.
4. Draft two follow-ups: one for attendees, one for no-shows.

## Rules
- Never invent a guest, an email, or an RSVP status.
- Never send anything. Draft only; the user sends.
- Keep invitations under 150 words, follow-ups under 120.

The description is the trigger. Claude reads only the name and description at startup — about 100 tokens per skill, per Anthropic’s documentation — and loads the rest only when your request matches. Use the exact phrases you will type, such as “plan the launch event.”

Step 3: Write the workflow in plain language

Below the frontmatter, write the instructions as if onboarding a careful new hire — the five jobs in order, plus your rules. One rule worth stealing: “Send the thank-you within 24 hours, while the event is fresh.” Keep the file short — per Anthropic’s documentation, skill instructions load at under 5,000 tokens. New to skill structure? Our guide to creating your first Claude skill covers the same folder layout.

Step 4: Add your templates and guest list as reference files

Keep the data out of the instructions. Save your invitation and follow-up templates in the same folder, with the guest list as guests.csv. Claude loads reference files only when needed — Anthropic calls this progressive disclosure — so a long guest list costs nothing until an event runs.

Step 5: Install it where you work

Install the skill separately on each surface — custom skills do not sync. In Claude Code, copy the folder into ~/.claude/skills/ (personal) or the project’s .claude/skills/ folder (team). On claude.ai, zip the folder — the folder itself must be inside the zip — and upload it under Settings > Features, with code execution enabled. Through the Claude API, skills run sandboxed with no network access — build this one for Claude Code or claude.ai. Our price-checking skill uses the same install pattern.

Step 6: Test it on a past event

Do not debut the skill on a real event — re-run a past one with its old guest list and details, and compare the drafts with what you sent. Check: does it fire on event questions, do invitations carry the right date and venue, does it flag bad rows instead of guessing, and does the follow-up sound like your business? If it fires on the wrong tasks, the description is too broad; if it never fires, too narrow. Fix the description first.

Tips and common mistakes

  • One skill, one workflow. Do not fold catering, venue booking, and tickets into the same file. Small, focused skills beat one giant one.
  • Date every RSVP table: a status without a date is a rumor, and a stale list sends invitations to the wrong people.
  • Keep a human in the send loop. The skill drafts; you review and send. That checkpoint prevents embarrassing mistakes — a wrong date, a misspelled name.
  • Only install skills from sources you trust. Anthropic warns a skill is like installing software: its instructions can do things its description never mentions.

FAQ

Do I need to code to build an event-planning skill?

No. A basic skill is a folder with a Markdown file, your guest list, and your templates.

Will the skill send invitations by itself?

No. It drafts invitations, reminders, and follow-ups for you to review and send — keeping the send step with a human is a deliberate safety rule.

What happens if my guest list has errors?

The skill should flag duplicates, missing emails, and missing names, and ask what to do. Never let it silently fix or delete a guest.

Does this work for large events?

It works best for events of up to about 200 guests. For larger conferences, use dedicated event software; let the skill handle only the follow-ups.

Conclusion

Event planning is mostly repetition around a few decisions that matter. An agent skill captures the repetition — list cleaning, invitations, RSVPs, follow-ups — and leaves the decisions to you. Build it once from the workflow you already use, test it on a past event, and the next launch starts with a prompt.

WebGool Tech Senior AI & Small Business Editor
Verified Contributor

Keep Reading

More in Skills

Explore all

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top