event-ops-score-and-door
DRAFT. Score Luma/RSVP lists, approve against capacity, produce host-hit shortlists and day-of door packs. Systems framing — not a marketing CSV dump. Not installed by deepline skills.
SKILL.mddrafts/event-ops-score-and-door/SKILL.md
GitHubEvent ops: score, approve, door pack (DRAFT)
Thesis
A full Luma page is demand. Pipeline starts at who gets a seat, who hosts must meet, and show/no-show writeback — not at another invite channel.
Flow
- Ingest pending/waitlist/approved export (
templates/guests.schema.csv). - Enrich missing title/company/LinkedIn (pilot ≤10 first).
- Score into hot/warm/low/skip (
references/scoring.md). - Capacity approve — dry-run diff before any Luma status changes.
- Host-hit list — top 20–40 with why + intro angle (optional dossier skill next).
- Door pack — name, company, segment, check-in box, host flags.
- Closeout — show/no-show column for CRM writeback within 24–48h.
Outputs
scored.csvapprove-dry-run.diff.mdhost-hits.csvdoor-list.csv/ printable PDF if available#event-opschecklist owner
Guardrails
- Scoring that never changes seats is a dashboard. This skill must change seats or explicitly say why not.
- No mass approve without capacity number on screen/log.