Agent skill
event-ops-score-and-door
DRAFT.
Filed under ABM and paid.
From getaero-io/gtm-eng-skills · 21 skill entries · 60 · pushed 2026-09-21
What it does when it runs
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.
Automated analysis of the skill and the 2 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/getaero-io/gtm-eng-skills.git /tmp/gtm-eng-skills git -C /tmp/gtm-eng-skills sparse-checkout set "drafts/event-ops-score-and-door" mkdir -p ~/.claude/skills/event-ops-score-and-door cp -R "/tmp/gtm-eng-skills/drafts/event-ops-score-and-door/." ~/.claude/skills/event-ops-score-and-door/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
Or take the whole library
This repo ships a .claude-plugin manifest, so Claude Code can install all 21 skills at once. Plugin skills are invoked as /<plugin>:<skill>, so they never collide with your own.
/plugin marketplace add getaero-io/gtm-eng-skills /plugin
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from getaero-io/gtm-eng-skills/blob/ce24f7d2f73830ad3690ff2e6c57c375d818e6fc/drafts/event-ops-score-and-door/SKILL.md, which is licensed MIT (repository). 151 words, 5 headings.
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.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.
Files bundled with it
These load only when the skill asks for them, so they cost nothing until it runs.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- conversion-ops by ericosiu · 3,558
- seo-ops by ericosiu · 3,558
- event-hosting by shawnpang · 331
- fullenrich-event-attendees by Othmane-Khadri · 310
- trigger-event-detection by louisblythe · 159
- suede-ops-architecture by JasonColapietro · 124
- suede-ops-assessment by JasonColapietro · 124
- event-prep by markster · 64
Need help setting it up?
This page tells you what event-ops-score-and-door does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.