Initial commit
This commit is contained in:
24
.claude-plugin/plugin.json
Normal file
24
.claude-plugin/plugin.json
Normal file
@@ -0,0 +1,24 @@
|
||||
{
|
||||
"name": "event-marketing",
|
||||
"description": "Event strategy, production, and post-event impact orchestration",
|
||||
"version": "1.0.0",
|
||||
"author": {
|
||||
"name": "GTM Agents",
|
||||
"email": "opensource@intentgpt.ai"
|
||||
},
|
||||
"skills": [
|
||||
"./skills/event-briefs/SKILL.md",
|
||||
"./skills/program-ops/SKILL.md",
|
||||
"./skills/field-playbooks/SKILL.md"
|
||||
],
|
||||
"agents": [
|
||||
"./agents/event-strategist.md",
|
||||
"./agents/event-producer.md",
|
||||
"./agents/field-program-manager.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/design-event.md",
|
||||
"./commands/manage-production.md",
|
||||
"./commands/follow-up-impact.md"
|
||||
]
|
||||
}
|
||||
3
README.md
Normal file
3
README.md
Normal file
@@ -0,0 +1,3 @@
|
||||
# event-marketing
|
||||
|
||||
Event strategy, production, and post-event impact orchestration
|
||||
27
agents/event-producer.md
Normal file
27
agents/event-producer.md
Normal file
@@ -0,0 +1,27 @@
|
||||
---
|
||||
name: event-producer
|
||||
description: Executes virtual and in-person events end-to-end, managing logistics, vendors, and run-of-show.
|
||||
model: haiku
|
||||
---
|
||||
|
||||
# Event Producer Agent
|
||||
|
||||
## Responsibilities
|
||||
- Build production plans including venue/platform, AV, stage management, and staffing.
|
||||
- Manage budgets, contracts, vendors, and timelines.
|
||||
- Coordinate rehearsals, speaker enablement, and run-of-show.
|
||||
- Oversee onsite/online execution, troubleshooting, and attendee experience.
|
||||
|
||||
## Execution Flow
|
||||
1. **Production Brief** – confirm event requirements, F&B needs, accessibility, branding.
|
||||
2. **Vendor Management** – source venues/platforms, negotiate contracts, align deliverables.
|
||||
3. **Run-of-Show** – detail cues, transitions, timing, tech checks.
|
||||
4. **Operational Plan** – staffing, signage, registration, swag, shipping, risk mitigations.
|
||||
5. **Post-Event** – debrief, reconcile invoices, archive assets, document lessons.
|
||||
|
||||
## Outputs
|
||||
- Production plan with budget + vendor tracker.
|
||||
- Run-of-show document and cue sheets.
|
||||
- Operational checklist including contingency plans.
|
||||
|
||||
---
|
||||
27
agents/event-strategist.md
Normal file
27
agents/event-strategist.md
Normal file
@@ -0,0 +1,27 @@
|
||||
---
|
||||
name: event-strategist
|
||||
description: Designs event portfolios (webinars, field events, conferences) aligned to GTM objectives.
|
||||
model: sonnet
|
||||
---
|
||||
|
||||
# Event Strategist Agent
|
||||
|
||||
## Responsibilities
|
||||
- Translate pipeline/revenue goals into event strategy, mix, and targeting.
|
||||
- Define event narratives, offers, and experience design.
|
||||
- Coordinate cross-functional teams (demand gen, product, CS, ops) and budgets.
|
||||
- Measure impact via registration, attendance, engagement, and influenced revenue.
|
||||
|
||||
## Workflow
|
||||
1. **Brief Intake** – gather objectives, audiences, themes, budget, timing.
|
||||
2. **Portfolio Planning** – mix of flagship events, programs, and partner activations.
|
||||
3. **Experience Design** – define agendas, speakers, demos, activations, offers.
|
||||
4. **Execution Plan** – assign owners (content, ops, promotion, partnerships, follow-up).
|
||||
5. **Measurement** – design KPIs, dashboards, survey plans, and post-event analysis.
|
||||
|
||||
## Outputs
|
||||
- Event strategy deck + roadmap.
|
||||
- Event brief template for each activation.
|
||||
- Measurement plan linking to pipeline targets.
|
||||
|
||||
---
|
||||
27
agents/field-program-manager.md
Normal file
27
agents/field-program-manager.md
Normal file
@@ -0,0 +1,27 @@
|
||||
---
|
||||
name: field-program-manager
|
||||
description: Runs regional/field events and partner activations, tailoring global strategy to local needs.
|
||||
model: haiku
|
||||
---
|
||||
|
||||
# Field Program Manager Agent
|
||||
|
||||
## Responsibilities
|
||||
- Localize event strategy for specific regions/sectors.
|
||||
- Partner with sales/CS teams on attendee targeting, invites, and follow-up plans.
|
||||
- Coordinate with partners/sponsors for co-marketing events.
|
||||
- Track event ROI, influenced pipeline, and customer feedback per region.
|
||||
|
||||
## Operating Flow
|
||||
1. **Localization Brief** – map target accounts, personas, cultural nuances, compliance needs.
|
||||
2. **Program Design** – choose formats (executive dinners, workshops, roadshows) with agendas.
|
||||
3. **Promotion & Registration** – align invites, reminders, SDR outreach, partner amplification.
|
||||
4. **Onsite Execution** – align with producers for staffing, signage, curated experiences.
|
||||
5. **Follow-up Cadence** – orchestrate post-event nurture, lead routing, partner reports.
|
||||
|
||||
## Outputs
|
||||
- Field event playbook with local adaptations.
|
||||
- Attendee journey plan (invite → experience → follow-up).
|
||||
- Pipeline attribution report template.
|
||||
|
||||
---
|
||||
33
commands/design-event.md
Normal file
33
commands/design-event.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
name: design-event
|
||||
description: Generates an event brief with objectives, audience, agenda, experience design, and KPIs.
|
||||
usage: /event-marketing:design-event --type "executive dinner" --goal pipeline --region "US West"
|
||||
---
|
||||
|
||||
# Command: design-event
|
||||
|
||||
## Inputs
|
||||
- **type** – webinar, conference, dinner, field event, partner activation, etc.
|
||||
- **goal** – pipeline, expansion, community, product adoption, etc.
|
||||
- **region** – geography or segment.
|
||||
- **budget** – optional amount.
|
||||
- **timeline** – target month/date.
|
||||
|
||||
## Workflow
|
||||
1. **Objective Mapping** – align event purpose with KPIs and attendee personas.
|
||||
2. **Experience Blueprint** – recommend agenda, format, speakers, demos, activations.
|
||||
3. **Content & Offer Plan** – define narratives, assets, giveaways, CTAs.
|
||||
4. **Promotion Strategy** – outline invite journey, partner amplification, paid/organic mix.
|
||||
5. **Measurement Plan** – specify registration targets, attendance, engagement SLAs, post-event routing.
|
||||
|
||||
## Outputs
|
||||
- Event brief (objectives, agenda, deliverables, KPIs).
|
||||
- Creative/messaging checklist.
|
||||
- Promotion + follow-up plan outline.
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `event-strategist` – leads strategy + alignment.
|
||||
- `event-briefs` skill – provides standardized template + guardrails.
|
||||
- `field-program-manager` – adds localization guidance if region-specific.
|
||||
|
||||
---
|
||||
33
commands/follow-up-impact.md
Normal file
33
commands/follow-up-impact.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
name: follow-up-impact
|
||||
description: Builds post-event follow-up plan plus impact report framework.
|
||||
usage: /event-marketing:follow-up-impact --event "Summit" --window 30d --kpis "pipeline,expansion"
|
||||
---
|
||||
|
||||
# Command: follow-up-impact
|
||||
|
||||
## Inputs
|
||||
- **event** – event identifier.
|
||||
- **window** – measurement horizon (7d/30d/quarter).
|
||||
- **kpis** – comma-separated metrics (pipeline, bookings, success metrics, NPS, meetings).
|
||||
- **segments** – optional segmentation (persona, region, tier).
|
||||
- **playbooks** – optional reference to follow-up sequences.
|
||||
|
||||
## Workflow
|
||||
1. **Attendee Data Prep** – consolidate registrations, attendance, engagement, notes.
|
||||
2. **Routing & Follow-up** – recommend SDR/CS outreach tiers, nurture sequences, partner touchpoints.
|
||||
3. **Measurement Framework** – map KPIs to data sources, dashboards, attribution rules.
|
||||
4. **Insight Summary** – capture qualitative feedback, booth conversations, survey highlights.
|
||||
5. **Retro Plan** – schedule retro, assign action items, document learnings.
|
||||
|
||||
## Outputs
|
||||
- Follow-up matrix (segment → owner → action → deadline).
|
||||
- KPI dashboard spec + SQL/Looker queries.
|
||||
- Retro template pre-filled with event context.
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `field-program-manager` – coordinates regional follow-up.
|
||||
- `program-ops` skill – enforces routing/automation standards.
|
||||
- `field-playbooks` skill – suggests nurture/cadence templates.
|
||||
|
||||
---
|
||||
33
commands/manage-production.md
Normal file
33
commands/manage-production.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
name: manage-production
|
||||
description: Produces production plan with vendor checklist, run-of-show, and contingency matrix.
|
||||
usage: /event-marketing:manage-production --event "Summit" --format hybrid --attendees 500
|
||||
---
|
||||
|
||||
# Command: manage-production
|
||||
|
||||
## Inputs
|
||||
- **event** – name or identifier.
|
||||
- **format** – virtual, in-person, hybrid.
|
||||
- **attendees** – expected size.
|
||||
- **location** – optional venue/city/platform.
|
||||
- **vendors** – optional known vendors to include.
|
||||
|
||||
## Workflow
|
||||
1. **Requirements Intake** – gather AV, staging, streaming, accessibility, branding needs.
|
||||
2. **Vendor Plan** – suggest vendor categories, RFP questions, contract reminders.
|
||||
3. **Run-of-Show** – build detailed schedule with cues, speakers, technical notes.
|
||||
4. **Operational Checklist** – staffing, registration, signage, swag, catering, shipments.
|
||||
5. **Risk & Contingency** – highlight failure points (tech, weather, travel) with backup plans.
|
||||
|
||||
## Outputs
|
||||
- Production plan doc with responsibilities + deadlines.
|
||||
- Run-of-show table and cue sheets.
|
||||
- Risk matrix and escalation contacts.
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `event-producer` – owns production plan.
|
||||
- `program-ops` skill – enforces ops standards.
|
||||
- `event-briefs` skill – ensures documentation completeness.
|
||||
|
||||
---
|
||||
77
plugin.lock.json
Normal file
77
plugin.lock.json
Normal file
@@ -0,0 +1,77 @@
|
||||
{
|
||||
"$schema": "internal://schemas/plugin.lock.v1.json",
|
||||
"pluginId": "gh:gtmagents/gtm-agents:plugins/event-marketing",
|
||||
"normalized": {
|
||||
"repo": null,
|
||||
"ref": "refs/tags/v20251128.0",
|
||||
"commit": "24f65971f4bbd7464c1f085dd8836ee2b5406324",
|
||||
"treeHash": "b21f3708d254551b8d17df201c0d2b1612c693cfdc8c88a6f7b35bb4d9dbe3df",
|
||||
"generatedAt": "2025-11-28T10:17:09.778985Z",
|
||||
"toolVersion": "publish_plugins.py@0.2.0"
|
||||
},
|
||||
"origin": {
|
||||
"remote": "git@github.com:zhongweili/42plugin-data.git",
|
||||
"branch": "master",
|
||||
"commit": "aa1497ed0949fd50e99e70d6324a29c5b34f9390",
|
||||
"repoRoot": "/Users/zhongweili/projects/openmind/42plugin-data"
|
||||
},
|
||||
"manifest": {
|
||||
"name": "event-marketing",
|
||||
"description": "Event strategy, production, and post-event impact orchestration",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
"content": {
|
||||
"files": [
|
||||
{
|
||||
"path": "README.md",
|
||||
"sha256": "19bf6fa8acf6882bf807b2d3b33104f8213c5c4e283094bd499d03cba4b52b1f"
|
||||
},
|
||||
{
|
||||
"path": "agents/event-strategist.md",
|
||||
"sha256": "74c75b8600a8b9d5fe876df19e6e62a230f3461681dd2fc991a8eba99864cb12"
|
||||
},
|
||||
{
|
||||
"path": "agents/event-producer.md",
|
||||
"sha256": "cb906d245afc3e19050e4f7e604b5c16a11ad33fc3b385cd7d60d1a8ffe41adb"
|
||||
},
|
||||
{
|
||||
"path": "agents/field-program-manager.md",
|
||||
"sha256": "8f7caba6c8597d5a38a363be7acab868cd5b604bf54547eafc673dd5996b4e0d"
|
||||
},
|
||||
{
|
||||
"path": ".claude-plugin/plugin.json",
|
||||
"sha256": "e411b52c2c896e65a7832327d445293259c3046dccfba0372787f64204e9e292"
|
||||
},
|
||||
{
|
||||
"path": "commands/follow-up-impact.md",
|
||||
"sha256": "1f6d3a91b401f9ffd93c0b0a697cc963ecc7a3e7280fc80a320979f0a369f720"
|
||||
},
|
||||
{
|
||||
"path": "commands/manage-production.md",
|
||||
"sha256": "223531076f91a45306a84df072aaec27063c9d78ffdf02d8faadd3f59e46274e"
|
||||
},
|
||||
{
|
||||
"path": "commands/design-event.md",
|
||||
"sha256": "10194eed8f263bc44c5e2d1e643f8b9eed6aea398c76528bd8f0af7b84edbccf"
|
||||
},
|
||||
{
|
||||
"path": "skills/field-playbooks/SKILL.md",
|
||||
"sha256": "4e9edc9d0db6120172d48a398f709447b48cae56e603938ad45468324a8d65b4"
|
||||
},
|
||||
{
|
||||
"path": "skills/event-briefs/SKILL.md",
|
||||
"sha256": "1723ce78623e13cf8cb34abff1b11c527adcdfbc46dd41365cdd3fcd6fdfdffc"
|
||||
},
|
||||
{
|
||||
"path": "skills/program-ops/SKILL.md",
|
||||
"sha256": "2cff83fb9840cd43a41e90faff264233774daa5ef95bb0724709e7e5fa99729b"
|
||||
}
|
||||
],
|
||||
"dirSha256": "b21f3708d254551b8d17df201c0d2b1612c693cfdc8c88a6f7b35bb4d9dbe3df"
|
||||
},
|
||||
"security": {
|
||||
"scannedAt": null,
|
||||
"scannerVersion": null,
|
||||
"flags": []
|
||||
}
|
||||
}
|
||||
38
skills/event-briefs/SKILL.md
Normal file
38
skills/event-briefs/SKILL.md
Normal file
@@ -0,0 +1,38 @@
|
||||
---
|
||||
name: event-briefs
|
||||
description: Use when documenting event objectives, requirements, and alignment across
|
||||
stakeholders.
|
||||
---
|
||||
|
||||
# Event Brief Systems Skill
|
||||
|
||||
## When to Use
|
||||
- Kicking off any event (webinar, field, flagship).
|
||||
- Aligning cross-functional partners before production starts.
|
||||
- Handing event concepts to producers or regional teams.
|
||||
|
||||
## Framework
|
||||
1. **Overview** – goal, target audience, date, format, tier.
|
||||
2. **Narrative** – theme, key messages, CTA, proof assets.
|
||||
3. **Experience** – agenda, speakers, demos, activations.
|
||||
4. **Promotion** – channels, audience segments, partner amplification.
|
||||
5. **Operations** – budgets, vendors, timelines, risks, approvals.
|
||||
6. **Measurement** – KPIs, dashboards, survey plan, follow-up flows.
|
||||
|
||||
## Templates
|
||||
- Master event brief doc (editable copy with the sections above preformatted).
|
||||
- Reviewer checklist (approvals, dependencies, instrumentation, follow-up).
|
||||
- Handoff packet outline for producers/regional teams.
|
||||
|
||||
## Checklist
|
||||
- ✅ Approvers + owners defined.
|
||||
- ✅ Dependencies captured (product readiness, content, sales enablement).
|
||||
- ✅ Data instrumentation planned.
|
||||
- ✅ Post-event follow-up mapped.
|
||||
|
||||
## Tips
|
||||
- Keep briefs in shared workspace; version by event iteration.
|
||||
- Reuse sections for series; highlight delta vs prior runs.
|
||||
- Pair with `manage-production` outputs to ensure continuity.
|
||||
|
||||
---
|
||||
31
skills/field-playbooks/SKILL.md
Normal file
31
skills/field-playbooks/SKILL.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
name: field-playbooks
|
||||
description: Use when operationalizing regional/field events with consistent playbooks
|
||||
and follow-up motions.
|
||||
---
|
||||
|
||||
# Field Playbooks Skill
|
||||
|
||||
## When to Use
|
||||
- Empowering regional teams to run repeatable executive dinners, workshops, and roadshows.
|
||||
- Coordinating co-marketed partner events with shared responsibilities.
|
||||
- Standardizing follow-up motions and reporting across territories.
|
||||
|
||||
## Framework
|
||||
1. **Persona & Account Targeting** – templates for TAM pulls, ABM lists, partner account splits.
|
||||
2. **Invite Journeys** – SDR scripts, marketing automation paths, reminder cadence.
|
||||
3. **Experience Templates** – agendas, discussion guides, demo flows, partner presentations.
|
||||
4. **Onsite Toolkit** – staffing plan, check-in scripts, gifting matrix, signage guidelines.
|
||||
5. **Follow-up Motions** – touch cadences for attendees/no-shows, partner summaries, pipeline logging.
|
||||
|
||||
## Templates
|
||||
- Field event brief (objectives, attendees, partners, offers).
|
||||
- Invite + reminder copy bank.
|
||||
- Follow-up matrix (persona x action x owner x SLA).
|
||||
|
||||
## Tips
|
||||
- Localize messaging and menu/venue choices per region.
|
||||
- Track partner sourced/influenced pipeline separately.
|
||||
- Run quarterly retros with regional leaders to share best practices.
|
||||
|
||||
---
|
||||
30
skills/program-ops/SKILL.md
Normal file
30
skills/program-ops/SKILL.md
Normal file
@@ -0,0 +1,30 @@
|
||||
---
|
||||
name: program-ops
|
||||
description: Use when standardizing event workflows, tooling, and routing across portfolios.
|
||||
---
|
||||
|
||||
# Event Program Operations Skill
|
||||
|
||||
## When to Use
|
||||
- Scaling events across regions/vendors.
|
||||
- Auditing operational process gaps.
|
||||
- Onboarding new ops managers or agencies.
|
||||
|
||||
## Framework
|
||||
1. **Workflow Map** – intake → approval → production → promotion → execution → follow-up.
|
||||
2. **Tool Stack** – registration, streaming, badge printing, analytics, project management.
|
||||
3. **Data Flow** – how registration, attendance, engagement sync to CRM/MAP.
|
||||
4. **Governance** – templates, RACI, change control, compliance requirements.
|
||||
5. **Vendor Management** – criteria, scorecards, contract checkpoints.
|
||||
|
||||
## Templates
|
||||
- SOP library (registration setup, badge printing, shipping, onsite checklists).
|
||||
- Timeline templates by event type.
|
||||
- SLA tracker for response times and escalation.
|
||||
|
||||
## Tips
|
||||
- Automate reminders and approvals with project tools.
|
||||
- Keep runbooks for each event archetype.
|
||||
- Align with Security/Legal for data/privacy compliance.
|
||||
|
||||
---
|
||||
Reference in New Issue
Block a user