smithery/gtmagents

event-briefs

Use when documenting event objectives, requirements, and alignment across stakeholders.

Installation

$ npx skills add smithery/gtmagents --skill event-briefs

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/gtmagents · top by installs.

npx skills add smithery/gtmagents

Browse all from smithery/gtmagents

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,376 B
  • docs SUMMARY.md 107 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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.