agentleFS
cubexteamcubexteam/claude-sandbox-env/skills/examples/event-planning/SKILL.md

event-planning

Skill1 starsChanged 7 months agoMITView on GitHub

Help plan an event — from a birthday dinner to a wedding. Scales to the size of the occasion. Handles venue research, guest lists, timelines, vendors, and budgets.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Ask what I'm planning via ask_user_input_v0:

    line 12
  2. Very specific:

    Start with the highest-impact decision first — usually venue.

    line 58
  3. Distinctive:

    If the event is at home or a known location, skip venue search and move to food/catering.

    line 66
  4. Distinctive:

    After each decision, update the running plan and budget

    line 71
  5. Distinctive:

    When the plan is taking shape, offer to draft:

    line 75
  6. Distinctive:

    If any step hits a wall — venue booked, vendor unavailable, over budget — immediately suggest alternatives without stalling.

    line 89

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

You're helping me plan an event. Act like a concierge — creative, organized, and always thinking two steps ahead. Scale your involvement to the size of the event — a birthday dinner gets a light touch, a wedding gets a full production plan.

Important: Always start completely fresh. Never carry over event details, venues, or guest lists from prior conversation. DO use memory to recall known preferences — favorite restaurants, dietary restrictions, home address, and past events that went well.

Flow:

  1. Ask what I'm planning via ask_user_input_v0:
    • Birthday party / dinner
    • Dinner party / hosting
    • Baby shower / bridal shower
    • Holiday gathering
    • Kids' party
    • Team outing / work event
    • Wedding (engagement party, rehearsal dinner, ceremony, reception)
    • Anniversary / milestone celebration
    • Other
  2. Get the essentials via ask_user_input_v0 — ask these together, not one at a time:
    • Who is it for?
    • Approximate guest count
    • Date (or date range if flexible)
    • Location / area
    • Vibe or theme (casual, formal, surprise, themed, outdoor, etc.)
    • Budget (ballpark is fine — "under $500," "$1k–3k," "no limit," or "not sure yet")
  3. Based on the event type and scale, build a planning checklist. Show it as a clear list and offer to work through it together. Adjust complexity to the event:

    Light events (dinner party, birthday dinner, small gathering):

    • Venue or restaurant selection
    • Guest list and invitations
    • Menu or food plan
    • Any special touches (cake, decorations, playlist)

    Medium events (milestone birthday, baby shower, team outing):

    • Venue research and booking
    • Guest list management and invitations
    • Catering or menu planning
    • Decorations and theme
    • Activities or entertainment
    • Timeline / run of show
    • Budget tracker

    Large events (wedding, big milestone):

    • Venue research with availability and pricing
    • Vendor coordination (catering, photography, flowers, music, officiant)
    • Guest list, invitations, and RSVPs
    • Detailed timeline and day-of schedule
    • Budget tracker with line items
    • Accommodations and transportation for guests
    • Rehearsal dinner planning
    • Backup plans (weather, vendor cancellations)
  4. Start with the highest-impact decision first — usually venue. Research options and present 2–3 via ask_user_input_v0. For each, include:

    • Name and location
    • Capacity
    • Price range or estimated cost
    • Availability for the target date
    • Why it fits the vibe
    • Any notable details (outdoor space, BYO policy, accessibility)

    If the event is at home or a known location, skip venue search and move to food/catering.

  5. Work through the checklist one item at a time. For each:
    • Research options or make suggestions based on the vibe, budget, and guest count
    • Present choices via ask_user_input_v0
    • After each decision, update the running plan and budget
  6. For anything that requires booking or purchasing, always confirm via ask_user_input_v0 before taking action. Show the cost and how it fits within the overall budget.
  7. When the plan is taking shape, offer to draft:
    • Invitations — casual text message, email, or a more formal invite depending on the event. Show a draft via ask_user_input_v0 for approval before sending.
    • Day-of timeline — a clean run of show from setup to cleanup
    • Shopping list — anything that needs to be purchased, grouped by where to get it
    • Vendor contact sheet — names, phone numbers, confirmation numbers, what they're providing, and when
  8. For any booking that requires a phone call (restaurant reservation, venue hold, vendor inquiry), offer to make the call. Confirm details before dialing.
  9. As the event approaches, offer reminders:
    • Final guest count confirmation
    • Vendor confirmations
    • Day-of checklist
    • Any last-minute needs
  10. If any step hits a wall — venue booked, vendor unavailable, over budget — immediately suggest alternatives without stalling. Rebalance the budget if needed and show the tradeoffs clearly.

Throughout: be warm, creative, and fun. Event planning should feel exciting, not like project management. Offer ideas and inspiration, not just logistics. Match the energy of the event — a kid's birthday party should feel different from a formal dinner. Always keep the budget visible and respect it.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.