Agent skill
luma-event-campaign
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. Use when running a Luma-centered GTM event campaign: pull/export guests, enrich and score, draft invites and social, stage email+LI sequences paused for approval, and wire registration sync. Not installed by deepline skills.
Automated analysis of the skill and the 6 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/luma-event-campaign" mkdir -p ~/.claude/skills/luma-event-campaign cp -R "/tmp/gtm-eng-skills/drafts/luma-event-campaign/." ~/.claude/skills/luma-event-campaign/
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/luma-event-campaign/SKILL.md, which is licensed MIT (repository). 478 words, 14 headings.
Luma event campaign (DRAFT)
When to use
You have (or are creating) a Luma event and need a repeatable campaign system: guest acquisition → enrichment → messaging → staged outreach → registration hygiene. Not for one-off "write me an invite tweet."
Non-negotiables
- Keep outbound campaigns paused until a human approves sends.
- Pilot enrich on ≤10 rows before full waterfall.
- No invented speaker bios, titles, or company facts.
- Templates use placeholders (
{{event_name}},{{city}},{{speaker_1}}). - Prefer systems language: skills, plays, webhooks, score → approve → door — not "blast the list."
Inputs
| Input | Required | Notes |
|---|---|---|
| Luma event URL or export CSV | yes | At least name, email, status |
| ICP / TAL sheet (domains) | no | Boosts scoring |
| Brand voice notes | no | Else use templates/voice.md |
| Sequencer (Lemlist/Instantly/etc.) | no | Stage paused campaign only |
Standard flow
1. Frame the system
Say out loud (or in the run log):
- Source of truth for guests (Luma)
- Enrich + score path
- Messaging artifacts (invite email, LI DM, social)
- Outreach object (paused)
- Inbound sync (registration webhook — see
luma-inbound-webhook-enrich)
2. Guest list hygiene
- Export or API-pull guests.
- Normalize emails; drop empties; flag duplicates.
- Map ticket/status: pending / approved / waitlist / checked_in.
- Write
guests.normalized.csv.
3. Enrich + score (pilot first)
- Run a 10-row pilot enrich (email validation + LinkedIn URL + title/company).
- Score segments:
hot/warm/low/skipusing ICP + TAL + seniority. - Full run only after pilot lookback.
- Write
guests.scored.csv.
4. Messaging pack
Use templates in templates/:
invite-email.md— HubSpot or transactional invitelinkedin-dm.md— short DM, no hype wordssocial-announcement.md— X/LinkedIn announcementspeaker-bio.md— only from verified sources
Fill placeholders; human-edit before publish.
5. Stage outreach (paused)
- Create/update sequencer campaign from
hot+warmonly. - Import with enrichment fields needed for personalization.
- Leave campaign paused; paste the campaign URL in the run report.
- Never auto-send from this skill.
6. Registration sync
Hand off to luma-inbound-webhook-enrich for standing registration → enrich → CRM.
7. Day-of handoff
Hand off scored list to event-ops-score-and-door and optional event-host-prep-dossiers.
Output checklist
-
guests.normalized.csv -
guests.scored.csv(with segment) - Messaging pack under
out/copy/ - Paused campaign link
- Credit / provider notes for enrich pilot + full run
- Explicit "human approve before send" line in the report
Guardrails
- Do not dunk on other tools; frame hybrid stacks honestly.
- Strip unsafe emails after validation; do not import fails into sequences.
- Anonymize any shared examples before committing to git.
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.
- luma-event-attendees by edupegoretti · 0
- campaign-copywriting by growthenginenowoslawski · 718
- campaign-strategy by growthenginenowoslawski · 718
- smartlead-campaign-upload-public by growthenginenowoslawski · 718
- campaign-postmortem by zapier · 339
- mega-campaign-generator by zapier · 339
- event-hosting by shawnpang · 331
- campaign-dashboard by Othmane-Khadri · 310
Need help setting it up?
This page tells you what luma-event-campaign 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.