Make it easy with AI

Event Planning Skills Kit / Setup guide

Event Planning Skills Kit — Installation Guide

This pack includes 10 ready-to-use Claude Skills for planning and running events:

  1. event-run-of-show-builder — turn an outline into a minute-by-minute timeline
  2. vendor-outreach-email-writer — inquiry emails to venues/vendors
  3. sponsor-outreach-email-writer — pitch emails to potential event sponsors
  4. guest-communication-writer — invites, reminders, and logistics emails to attendees
  5. event-invitation-copy-writer — invitation and save-the-date copy
  6. event-budget-tracker-template — a categorized budget tracker with estimated vs. actual
  7. event-risk-contingency-planner — identify likely risks and backup plans
  8. speaker-briefing-document-builder — a briefing doc covering logistics, expectations, and AV needs
  9. day-of-checklist-builder — setup/execution/teardown checklist for event day
  10. post-event-survey-builder — a structured post-event feedback survey

What is a Claude Skill?

A Claude Skill is an instructions file (SKILL.md) that teaches Claude how to perform a specific task following your format and rules. When you ask Claude something that matches a skill's description, it automatically applies those instructions.

Installing — Claude Code (on your computer / terminal)

A) User-level (works in every project)

  1. Create the skills folder if it doesn't exist yet:
    mkdir -p ~/.claude/skills
    
  2. Copy each skill's folder into ~/.claude/skills/, so the final path looks like:
    ~/.claude/skills/event-run-of-show-builder/SKILL.md
    ~/.claude/skills/vendor-outreach-email-writer/SKILL.md
    ~/.claude/skills/sponsor-outreach-email-writer/SKILL.md
    ~/.claude/skills/guest-communication-writer/SKILL.md
    ~/.claude/skills/event-invitation-copy-writer/SKILL.md
    ~/.claude/skills/event-budget-tracker-template/SKILL.md
    ~/.claude/skills/event-risk-contingency-planner/SKILL.md
    ~/.claude/skills/speaker-briefing-document-builder/SKILL.md
    ~/.claude/skills/day-of-checklist-builder/SKILL.md
    ~/.claude/skills/post-event-survey-builder/SKILL.md
    
  3. Start (or restart) Claude Code — the skills will be available automatically in any project.

B) Single-project level

Copy the same folders into <your-project>/.claude/skills/ instead, if you only want them in one project.

Using with claude.ai / Claude Desktop

  1. Open Settings.
  2. Find the Capabilities or Skills section.
  3. Upload each skill's SKILL.md file (or its whole folder).
  4. The skill triggers automatically when you ask something matching its description.

Using with ChatGPT

ChatGPT doesn't have a "Skills" system, but each SKILL.md file works just as well as ChatGPT instructions — the part below the --- frontmatter is plain instruction text.

As a Custom GPT (ChatGPT Plus/Team — stays saved for reuse):

  1. Go to Explore GPTs → Create → Configure.
  2. Give it a name (e.g., "Run of Show Builder") and a short description.
  3. Open the skill's SKILL.md file, copy everything below the --- frontmatter block, and paste it into the Instructions field.
  4. Save. Reopen this GPT any time you need that skill.

Without Custom GPT access (works on any ChatGPT plan): Paste the same instructions (below the frontmatter) at the start of a new chat, then ask your question. You'll need to re-paste it each time you start a new chat.

How to check it's working

After installing, ask Claude something that clearly matches one skill, for example:

"Build a run of show for a 3-hour evening event: welcome/mingling, dinner, awards, closing remarks, starting at 6pm."

If the skill triggered correctly, the answer will follow the event-run-of-show-builder structure (a timeline table with buffer time flagged).

Common issues

  • The skill doesn't trigger — check that the SKILL.md file is inside a folder, not dropped directly into .claude/skills/.
  • Changes aren't showing up — restart your Claude Code session after editing a file.
  • Missing details show as [fill in] — that's intentional; these skills never invent vendor names, budgets, or event details you didn't provide.