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.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./drafts/event-ops-score-and-door/SKILL.md

Event 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.csv
approve-dry-run.diff.md
host-hits.csv
door-list.csv / printable PDF if available
#event-ops checklist 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.

Repository: getaero-io/gtm-eng-skills
Path: drafts/event-ops-score-and-door/SKILL.md
Commit: a9b9731

Last updated: 6 days ago
First committed: 16 days ago

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.