Planning, promoting, and executing developer events from meetups to conferences
Plans and executes developer events from meetups to conferences with timelines, promotion strategies, and failure recovery. Triggers when you need to organize any developer event type with specific goals and attendance targets.
/plugin marketplace add pluginagentmarketplace/custom-plugin-devrel-engineer/plugin install devrel-engineer-plugin@pluginagentmarketplace-devrel-engineerThis skill inherits all available tools. When active, it can use any tool Claude has access to.
assets/event-checklist.yamlreferences/EVENT_GUIDE.mdscripts/event_planner.pyPlan and execute successful developer events that create lasting impact.
parameters:
required:
- event_type: enum[meetup, webinar, workshop, hackathon, conference]
- event_goal: string
optional:
- format: enum[in_person, virtual, hybrid]
- target_attendance: integer
- budget: float
output:
event_plan:
overview: object
timeline: array[Milestone]
budget: object
run_of_show: array[Session]
| Type | Size | Duration | Lead Time |
|---|---|---|---|
| Meetup | 20-100 | 2-3 hours | 4-6 weeks |
| Workshop | 10-50 | Half/full day | 6-8 weeks |
| Webinar | 50-500 | 1 hour | 2-4 weeks |
| Hackathon | 50-500 | 24-48 hours | 8-12 weeks |
| Conference | 200-2000 | 1-3 days | 3-6 months |
□ Define goals and success metrics
□ Set budget
□ Book venue (if in-person)
□ Recruit speakers
□ Create event branding
□ Open registration
□ Launch promotion
□ Finalize agenda
□ Confirm sponsors
□ Plan logistics
□ Speaker prep calls
□ Finalize catering/A/V
□ Send attendee reminders
□ Prepare materials
□ Test technology
□ Venue walkthrough
□ Test all equipment
□ Brief volunteers
□ Prepare swag bags
□ Final speaker check
Email → Social → Partners → Community → Press
↓ ↓ ↓ ↓ ↓
List Posts Co-promo Members PR
Sequence Campaign Shares Announce Outreach
| Activity | Timing |
|---|---|
| Thank you emails | Same day |
| Feedback survey | 1-3 days |
| Photo gallery | 1 week |
| Recording publish | 1 week |
| ROI report | 2-4 weeks |
retry_patterns:
low_registrations:
strategy: "Boost promotion, add incentive"
trigger: "<50% target at T-2 weeks"
speaker_cancellation:
strategy: "Activate backup speaker"
fallback: "Panel discussion"
technical_issues:
strategy: "Switch to backup equipment"
| Failure Mode | Detection | Recovery |
|---|---|---|
| Low registrations | <50% at T-2w | Boost promo |
| Low show rate | <60% attendance | Better reminders |
| Speaker no-show | Day-of absence | Backup speaker |
| A/V failure | Tech issues | Backup equipment |
□ Goals and metrics defined?
□ Budget approved?
□ Venue/platform confirmed?
□ Speakers confirmed?
□ Registration working?
□ Promotion calendar active?
□ A/V tested?
□ Backup plans documented?
test_event_management:
unit_tests:
- test_registration_flow:
assert: "Confirmation email received"
integration_tests:
- test_day_of_flow:
assert: "All sessions on time"
| Metric | Target |
|---|---|
| Reg to attendance | >60% |
| NPS score | >40 |
| Content engagement | >50% |
metrics:
- registrations: integer
- attendees: integer
- show_rate: float
- nps_score: float
See assets/ for event checklists and templates.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.