Event planner
- When to use it
- Seated dinners and event days that hold together: a table plan where every guest has one seat and every together, keep-apart and access request holds, and a run of show where no room or person is booked twice and every changeover has the time it needs, each checked by a script and drawn before anyone prints it.
- Covers
- Plan an event (2)
- Where you decide
- No gated loop of its own; the skills run one at a time.
- Size
- 7 skills · 0 loops
npx skilldrop-cli install --pack event-planner
Installs 7 skills, including core.
Other ways to install
The pack's loops too, each as an invokable skill:
npx skilldrop-cli install --loop --pack event-planner
In Claude Code, as a plugin (after /plugin marketplace add sananthanarayan/skilldrop):
/plugin install event-planner@skilldrop
Into Cursor, Kiro or another IDE:
npx skilldrop-cli install --pack event-planner --ide cursor
Start here: Get a checked seating plan from a guest list and a few requests
Paste this into your agent:
Seat these 36 wedding guests at four tables of 10 (the head table seats 6). Keep each household together, keep Dan and Priya apart, and Grandma Rose uses a wheelchair, so she needs table 1, which is step-free. Here's the list: <paste it>.
- Before you start
- The guest list with households and requests, or the day's sessions with rooms and times
- Python 3 on the machine, which the checking and drawing scripts run on
- How to tell it worked
- seating-plan replies with a table of who sits where, names any request it couldn't meet and why, lists dietary needs per table, and saves a drawing of the room with names at each table, after a check that every guest has one seat and every request holds.
- If nothing happens
- If seating-plan does not activate, ask for it by name ("use seating-plan"). If a request can't be met, say which one may give, and ask again.
A typical session
When: You're running a seated dinner or a day of sessions, and want a plan that won't fall apart on the day.
You bring:
- the guest list, with households, access needs and dietary needs
- the tables: how many, seats each, which are step-free
- who must sit together and who must be kept apart
- the day's sessions, rooms, speakers and venue hours
-
- You
- Give it the sessions, rooms, speakers and the venue's hours.
- You get
- A running order with every changeover and break, checked so no room or person is booked twice, and a timeline per room.
- You decide
- Accept the moves it proposes for any clash, or name what may give.
-
- You
- Give it the guest list, the tables and the requests.
- You get
- A table-by-table plan with every request held or named, the caterer's list per table, and a drawing of the room.
- You decide
- Print the place cards, or ask for another arrangement.
You end with: A running order the crew can work from and a seating plan the venue can set, both checked.
Compare Event planner with another pack
Skills in this pack (2)
- run-of-show Turn an event's agenda into a timed run of show — every session, speaker, changeover and break with its start, end, room and who's needed — and check it with a script for two things in one room at once, a speaker booked in two places, changeovers shorter than the turnaround and anything outside venue hours, drawn as a timeline per room. Use when an organiser asks for "a run of show", "a running order", "the minute-by-minute for the day", "check the agenda for clashes", or has sessions, speakers and rooms for a conference, launch, festival or wedding day. standard
- seating-plan Seat guests at tables for a wedding, gala, conference dinner or awards night, and check the chart with a script — every guest seated once, no table over capacity, people who must sit together together, people who must be kept apart apart, wheelchair users at accessible places — drawn as a room plan with names at each table. Use when an organiser asks to "make the seating plan", "who sits where", "seat these 120 guests", "check my table plan", or has a guest list with groups and keep-apart requests. standard
Included from core (5)
- brief-intake Turn raw mess — a Slack thread, meeting transcript, Jira ticket, half-written Notion page, email chain, or paragraph of free-form context — into a structured brief that the downstream skill (adr-generator, design-doc, runbook-generator, exec-summary, slide-outliner) can consume without further intake. Use whenever the user has unstructured source material and is about to invoke another skilldrop skill, or when a draft is missing the load-bearing context the next step will need. standard
- context-graph Map the decisions behind a codebase from its ADRs, RFCs and design records — each record's status and date, what supersedes or amends what, which records cite which, the files and folders each decision governs, and with git the commits that implemented it and the commits that changed each decision's code since it was made, and who made them — then answer "why is it like this?" from the record and check the record is still true. Finds supersessions only one side records, current decisions pointing at code that is gone, code that has drifted from its decision, two current decisions governing the same path, and references to records that don't exist. Use when the user asks "why do we use X", "which decisions govern this file or service", "is this ADR still current", "has the code drifted since we decided this", "are our ADRs out of date", "what was decided before I change this", wants a map of the architecture decisions, or is onboarding onto a codebase's history. standard
- council-review Convene a council of distinct senior-engineer personas (Architect, Security, Operator/SRE, Pragmatist, User-Advocate, plus optional bench seats) to deliberate a decision, design, or code change — each takes an independent stance, the genuine disagreements are surfaced as named cruxes, and a Chair issues a reconciled verdict that records dissents and states what would change the decision. The "Claude Council." Use when a choice has real tradeoffs and one reviewer's voice isn't enough: architecture decisions, risky changes before merge, RFC/design scrutiny, "should we adopt X?", rewrite-vs-refactor, or a pre-mortem. heavy
- doc-critique Review an existing document — ADR, design doc, runbook, exec summary, tech-comparison matrix, deck outline, decision log — and produce a structured critique against the same quality bars the skilldrop generators enforce. Categorizes findings by severity (blocker / major / minor / nit), points to the exact section/line, and suggests a concrete fix for each. Use when the user wants a second-pair-of-eyes review before sharing a doc, or has been handed someone else's artifact and wants to know what to push back on. heavy
- output-hygiene Review agent-written text before it ships and strip the machine artifacts it carries — invisible Unicode, non-breaking spaces, homoglyphs, harness-added provenance trailers, trailing chat closers — then flag the prose tells a script cannot catch, each quoted with a rewrite. Use when the user wants to clean up AI-generated output, asks to remove a Claude watermark, attribution footer, or "Generated with" line, wants a draft that does not read as machine-written, or needs a pre-ship hygiene pass on a document, commit message, or pasted chat answer. light