event-planning skill
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.
Is the event-planning skill safe?
Clean: nothing in its files matched our rules. We read 2 files in the folder on 2026-09-28.
No findings.
Install the event-planning skill
A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.
git clone --depth 1 https://github.com/Razshy/Wiggle.git /tmp/Wiggle mkdir -p ~/.claude/skills cp -r /tmp/Wiggle/mnt-skills/examples/event-planning ~/.claude/skills/event-planning
In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub
The instructions your agent would load
SKILL.md as published, without the frontmatter. Read it on GitHub
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:
- Ask what I'm planning via askuserinput_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
- Get the essentials via askuserinput_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")
- 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)
- Start with the highest-impact decision first — usually venue. Research options and present 2–3 via askuserinput_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.
- 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 askuserinput_v0
- After each decision, update the running plan and budget
- For anything that requires booking or purchasing, always confirm via askuserinput_v0 before taking action. Show the cost and how it fits within the overall budget.
- 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 askuserinput_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
- For any booking that requires a phone call (restaurant reservation, venue hold, vendor inquiry), offer to make the call. Confirm details before dialing.
- As the event approaches, offer reminders:
- Final guest count confirmation
- Vendor confirmations
- Day-of checklist
- Any last-minute needs
- 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.
More skills from Razshy/Wiggle
- Aalgorithmic-artCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
- Abenepass-reimbursementSubmit expense reimbursements through Benepass (app.getbenepass.com). For users whose employer uses Benepass as their benefits platform. Handles login, benefit selection, form filling, receipt upload, and submission. Requires browser/computer-use capabilities.
- Abrand-guidelinesApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
- Abuilt-in-browserRead this skill before the first step that uses the built-in browser, the browser pane inside the Claude desktop app (also called the in-app browser, the browser pane, Claude's browser, or \"your own browser\"), whose tools are named mcp__Claude_Browser__* when the session runs in the desktop app and mcp__remote-devices__Claude_Browser__* when a cloud session is linked to the person's computer; before those tools are turned on there may be a single enable__mcp__remote-devices__Claude_Browser tool instead. It covers the pane's persistent sign-ins, tabs and preview_start, reading pages as text, site approvals, what the pane cannot open, and what to do when it cannot be reached. It is not for Claude in Chrome (mcp__claude-in-chrome__* tools), which has its own skill, and it does not decide which browser to use.
- Acall-to-bookMake a phone call to book an appointment or reservation. Checks calendar first, gets explicit consent before dialing, discloses AI identity on the call, and adds the booking to calendar when done.
- Acancel-unsubscribeCancel a subscription or unsubscribe from a service. Works from a description, a pasted charge line, a URL, or a photo/screenshot. Can also audit a full statement for recurring charges and cancel several at once. Finds the right contact method and handles the cancellation — including phone calls.
- Acanvas-designCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
- Achrome-browserRead this skill before the first step that uses Claude in Chrome, the browser extension whose tools are named mcp__claude-in-chrome__* (also called Chrome, the browser extension, or the external browser) and which acts in the person's real Chrome with their own sign-ins; before those tools are turned on there may be a single enable__mcp__claude-in-chrome tool instead. It covers loading the tools in one ToolSearch call, checking the person's open tabs and working in a new tab, site permissions, GIF recordings, console logs, dialogs to avoid, and when to stop and ask. It is not for the built-in browser (mcp__Claude_Browser__* or mcp__remote-devices__Claude_Browser__* tools), which has its own skill, and it does not decide which browser to use.
- Acomputer-useRead this skill before the first step of any request to do something in an app on the person's own computer (Notes, Finder, System Settings, any desktop app), to look at their screen, or for \"computer use\". Computer use (desktop control) lets Claude take screenshots of the person's desktop and control it with clicks, typing and scrolling through the Claude desktop app; its tools are named mcp__computer-use__* when the session runs in the desktop app and mcp__remote-devices__computer_* when a cloud session is linked to the person's computer; before a conversation is linked there may be no such tools, only an enable__mcp__remote-devices__Claude_Browser tool, which links it. It covers getting linked, picking the right tool, the access flow, and what to do when computer use is off or out of reach. It is not for websites, which go through Claude in Chrome or the built-in browser and their own skills.
- Adeep-researchUse this skill when the user's prompt requires (1) researching a topic across multiple sources, comparing options or alternatives, analyzing trends or history, understanding markets or industries, or reviewing literature or studies and (2) synthesizing that research into a comprehensive, narrative report. If you're planning to search the web or internal knowledge bases, consider using this skill. This skill coordinates research subagents, so use it only when you have a tool for spawning subagents (the Agent or Task tool); otherwise, research the question directly.
- Adoc-coauthoringGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
- AdocxUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx) or Word templates (.dotx). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file (to download, email or print), use this skill. However, if they ask for a document, page, report, memo, or notes WITHOUT naming a file format and the session offers a dedicated document or page skill or connector, use that instead. Do NOT use for PDFs, spreadsheets, Google Docs, or coding unrelated to document generation.