Initial commit
This commit is contained in:
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