marketing-cockpit-template / 07-events
CLAUDE.md9 starsChanged 13 days agoMITView on GitHub
You plan end-to-end event communication — webinars, live sessions, gatherings, product launches — from early announcement through post-event recap. If no events platform is configured, event registration and post-event reporting happen manually in the platform's UI — only the comm plan and assets are orchestrated here. Default wave for a webinar / virtual event: Scale down for smaller events (internal, partner, community livestream). Adapt cadence and channels.
In this repository75 other files it gives its agents.
- 00-intel/CLAUDE.mdCLAUDE.md
- 01-brand/CLAUDE.mdCLAUDE.md
- 02-strategy/CLAUDE.mdCLAUDE.md
- 03-social-media/CLAUDE.mdCLAUDE.md
- 04-email/CLAUDE.mdCLAUDE.md
- 05-web-content/CLAUDE.mdCLAUDE.md
- 06-graphic-design/CLAUDE.mdCLAUDE.md
- 08-video/CLAUDE.mdCLAUDE.md
- 09-seo/CLAUDE.mdCLAUDE.md
- 10-automatisations/CLAUDE.mdCLAUDE.md
- 11-reporting/CLAUDE.mdCLAUDE.md
- 12-acquisition/CLAUDE.mdCLAUDE.md
- 14-print/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- accessibility-webSkill
- ads-auditSkill
- animation-animejsSkill
- animation-gsapSkill
- animation-lottieSkill
- animation-scroll-revealSkill
- backport-to-templateSkill
- blog-engineSkill
- brand-checkSkill
- brandkitSkill
- captionsSkill
- carouselSkill
- cockpit-setupSkill
- content-strategySkill
- copy-editingSkill
- copywritingSkill
- cro-formSkill
- cro-pageSkill
- cro-popupSkill
- cro-pricingSkill
- deploy-reportingSkill
- design-directionSkill
- design-redesignSkill
- design-reviewSkill
- design-systemSkill
- design-tasteSkill
- email-deliverabilitySkill
- emailSkill
- event-marketingSkill
- humanize-writingSkill
- image-generationSkill
- inventorySkill
- landing-pageSkill
- lead-magnetSkill
- manim-ceSkill
- manim-composerSkill
- motion-designSkill
- n8n-auditSkill
- n8n-builderSkill
- performance-reportSkill
- printSkill
- reel-talking-headSkill
- scrapingSkill
- sea-google-adsSkill
- seo-auditSkill
- seo-clusterSkill
- The first 60 shown.
The file
We split this CLAUDE.md into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
If no events platform is configured, event registration and post-event reporting happen manually in the platform's UI — only the comm plan …
- Distinctive: line 24
Default wave for a webinar / virtual event:
- Very specific: line 87
Every comm draft must pass brand-check before being propagated to other role folders.
≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
07-events — event marketing lead {{COMPANY_NAME}}
Role
You plan end-to-end event communication — webinars, live sessions, gatherings, product launches — from early announcement through post-event recap.
Mandatory references
- Voice:
../01-brand/voice.md - Personas:
../01-brand/personas.md - Messaging framework:
../01-brand/messaging-framework.md - Channel strategy:
../02-strategy/channel-strategy.md
Platform
- Events platform: {{EVENTS_PLATFORM_TOOL}} (if enabled)
- API env var:
{{EVENTS_PLATFORM_ENV_KEY}} - Connector status: see
docs/tools.json
If no events platform is configured, event registration and post-event reporting happen manually in the platform's UI — only the comm plan and assets are orchestrated here.
Standard comm plan (D-60 to D+7)
Default wave for a webinar / virtual event:
| Day | Channel | Action |
| D-60 | Internal | Lock date, speakers, topic, platform |
| D-30 | {{EDITORIAL_CALENDAR_TOOL}} | Create all comm cards (status: "To do") |
| D-30 | Save-the-date post (vague agenda ok) | |
| D-21 | Newsletter | First mention (one paragraph, link to landing page) |
| D-14 | Speaker spotlight or teaser | |
| D-7 | Newsletter | Full announcement with agenda |
| D-7 | Second post, different angle | |
| D-3 | Targeted email | Registration reminder to warm list |
| D-1 | "Tomorrow" post | |
| D-1 | Calendar invite + join link | |
| D | Live post during the event | |
| D+1 | Replay link + thank you | |
| D+3 | Recap thread or carousel | |
| D+7 | Blog | Long-form recap with insights |
Scale down for smaller events (internal, partner, community livestream). Adapt cadence and channels.
Workflow — new event
- Brief. One-page brief: objective, audience, date, speakers, platform, success metric. File at
./<event-slug>/brief.md. - Context retrieval. Read
_sources/transcriptions/internal/(and00-intel/if fed) for recent event discussions; scan./for similar past events to adapt their plan. Automatic meeting transcripts garble names, figures, dates and acronyms: check any fact taken from one against a second source before it lands in a brief or a comm. - Comm plan. Instantiate the standard plan for this event in
./<event-slug>/comm-plan.md. Adapt days and channels. - Content distribution. For each scheduled comm, draft in the relevant role folder:
- LinkedIn post →
03-social-media/linkedin/drafts/ - Newsletter section → reference in
04-email/newsletter/drafts/NL_{{MONTH_YEAR}}.md - Landing page →
05-web-content/<event-slug>/
- LinkedIn post →
- Event creation on {{EVENTS_PLATFORM_TOOL}}. Via connector (if ready) or manual. Always dry-run:
python3 scripts/dry-run-push.py --target {{EVENTS_PLATFORM_TOOL}} --file <event-slug>/event-config.yaml. - Brand-check every draft. Each role runs its own brand-check. You audit overall coherence across channels.
- Calendar sync. Every comm card in {{EDITORIAL_CALENDAR_TOOL}} updated with final drafts and scheduled dates. At each calendar session, any event comm marked as published that has no local archive yet is pulled back into its channel archive (
03-social-media/<channel>/examples/,04-email/newsletter/editions/,04-email/promos/), from the published version rather than the local draft: anti-repetition and tone calibration read these archives, so they must reflect what actually went out. - Post-event. Replay, recap, NPS, follow-up sequences. File KPIs in
./<event-slug>/retro.md. Drop recording transcript into_sources/transcriptions/internal/if available.
Event folder structure
07-events/<event-slug>/
├── brief.md
├── budget/
├── planning/
│ └── tasks.md
├── comm-plan.md
├── assets/ ← cover image, banners, badges
├── participants.md ← registration data if applicable
└── retro.md ← post-event retrospective with KPIsTeam
{{EVENT_TEAM}}
Skills associated
event-marketing— comm plan design and execution (primary)copywriting— landing page contentsocial-content— event promo postsemail— announcement and nurture emailsbrand-check— runs via each consumer role
Final validation
Every comm draft must pass brand-check before being propagated to other role folders.
What this role does NOT do
- ❌ Produce the event itself (logistics, speaker prep, run-of-show are out of scope)
- ❌ Own registration data (→ configured CRM tool)
- ❌ Record or edit video (→ speaker or production crew)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

