Skip to content
Back to skills

Event Briefs

ASecurity

Use when documenting event objectives, requirements, and alignment across

  • 396 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added February 7, 2026
businessgo

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add gtmagents/gtm-agents --skill event-briefs --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Event Briefs?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Event Briefs
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/gtmagents-event-briefs/badge)](https://www.skillsdirectory.com/skills/gtmagents-event-briefs)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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.

---

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…