Menu

Individual skill

company-event-ops

0upvotes

Run a company event — the launch party, the customer day, the team celebration — as the operation it is: the goal that shapes every choice, the budget with its forgotten lines, the vendor and venue coordination, the run-of-show with owners, and the day-of roles that keep hosts hosting. Use when asked plan the company event, organize our customer day/holiday party/launch event, what am I forgetting for this event, or be the run-of-show for Thursday. Produces the goal-shaped plan, the budget with the forgotten lines, the run-of-show, and the day-of role card.

skills/company-event-ops/SKILL.md

Read pinned source

Source commit e0009a385c480fb0b5687e7412df67c7c64f7cee

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 12, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,542
Repository last updated
Nov 11, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Company Event Ops Skill

Company events are [wedding-logistics-planner](../wedding-logistics-planner/SKILL.md) mechanics pointed at a business goal — and the goal is the part that usually goes unstated, which is why so many events are pleasant and pointless. "What is this event *for*" (celebrate the team? deepen customer relationships? mark the launch loudly?) shapes every downstream choice: venue, format, guest list, budget, and what success means Friday morning. Below the goal, it's operations: the budget with its routinely-forgotten lines (AV, service fees, the buffer), vendors coordinated on one sheet, the run-of-show with a named owner per segment, and the day-of rule that saves every event: *the hosts host; the runners run* — decided in advance, or the CEO spends the customer day moving chairs.

## What This Skill Produces

- **The goal-shaped plan** — the event's purpose stated, and the format/venue/guest choices that follow from it
- **The budget** — the real lines including the forgotten ones (AV, service charges + gratuities, signage, the 10% buffer)
- **The run-of-show** — the event in segments: time, what happens, who owns it, what could go wrong
- **The day-of role card** — hosts, runners, the decision-holder, vendor point — names against jobs, the [workshop-designer](../workshop-designer/SKILL.md) capture-role logic applied to events

## Required Inputs

Ask for these if not provided:
Back to top