Events & Activities

Events & Activities helps define an event record with an owner, date and sign-up count. A budget line is included for events that have a budget. Its workflow lists the event, records sign-ups and budget, tracks the event being run and captures feedback afterward.

The skill separates advice, review, conversion and build requests before producing artifacts. Advice receives a short recommendation and an offer of a relevant build. An explicit build request proceeds once essential missing facts are resolved. It asks one question at a time, reuses answers already supplied and stops when further answers would not change the deliverable. Unknown information remains unknown rather than receiving invented values.

Use it for an event tracker, town hall planner, team outing register or company events database. It fits growth-stage businesses organizing town halls, training, outings and celebrations with budget and attendance details.

It produces empty templates and does not book venues, send invitations or process payments. The skill does not calculate payroll, tax, leave balances or KPIs. Automation, reminders and synchronization require an integration layer. Legal, tax and HR review is required before templates drive real decisions.

Inputs cover annual event volume, internal versus external audiences, recurring versus one-off events, dates, venues, owners, budgets, capacity, open or invitation-only registration and RSVP tracking. The requested outcome can be an event list, RSVP view or budget view. Fields record event name and type, date, start and end times, venue or link, organizer, department, audience, budget, actual cost and currency. RSVP and attended counts, attendance percentage, feedback score, linked calendar entry, status, notes and event ID complete the structure. Event types cover team meetings, training, workshops, social events, offsites and reviews; statuses distinguish planned, confirmed, held, postponed and cancelled events.

Requested artifacts can include CSV, SQL DDL, JSON Schema, Notion property mappings or an Excel workbook. The formats derive from one field list: CSV and JSON retain matching display names, while SQL uses normalized identifiers. Dates retain date types, money retains currency types and cross-table references retain relation types. Select options are a starting set that can be renamed to match the business.

One SQL example is:

CREATE INDEX idx_events_activities_status ON events_activities (status);

Templates are empty by default. Example rows are produced only on request and remain obviously synthetic. Sensitive identifiers should not be repeated unnecessarily during a requested review. Machine-readable data stays separate from explanatory prose and any material validation failures. Excel-compatible CSV uses UTF-8 with a byte order mark and accompanying guidance about number, date and currency columns. An XLSX workbook is a separate requested output rather than a renamed CSV.

The Notion output routes to notion-manual-import for CSV, property mappings, import steps and verification. Manual mappings require no connection. Requested live workspace changes require actual tool access, a verified target and authorization. Imported columns may initially be Text and need their mapped property types applied. Relation links resolve after both relevant databases are imported. A static mapping alone does not establish a completed workspace change.