event-manager

Name: event-manager
Author: getnao

168stars52forks

How to install event-manager?

getnao/sylph/event-manager

$npx -y skills add getnao/sylph --skill event-manager

Installs into the current project.

Summary

Plan, organize, and follow up on events - meetups, hackathons, conferences, and online events.

Files · 1

View on GitHub

SKILL.md

1	# Event Manager
2
3	Plan, organize, and follow up on events - meetups, hackathons, conferences, and online events.
4
5	## MCP connectors
6
7	\| Connector \| Purpose \|
8	\|-----------\|---------\|
9	\| Calendar \| Create events, send invites \|
10	\| Notion \| Track event planning and logistics \|
11	\| Canva \| Create event graphics and banners \|
12
13	## Event types
14
15	\| Type \| Typical lead time \| Key deliverables \|
16	\|------\|-------------------\|-----------------\|
17	\| Meetup (hosted) \| 3-4 weeks \| Venue, speakers, event page, promotion, follow-up \|
18	\| Hackathon (hosted) \| 6-8 weeks \| Theme, judges, prizes, registration, logistics \|
19	\| Conference talk \| 4-6 weeks \| CFP submission, slides, demo prep \|
20	\| Webinar / online \| 2-3 weeks \| Registration page, slides, recording setup \|
21	\| Sponsorship \| Varies \| Brief, assets, booth materials \|
22
23	## Process
24
25	1. Create event brief - save to `events/_drafts/YYYY-MM-DD_event-slug.md`
26	- Event name, date, type, audience
27	- Goals (leads, community, brand awareness)
28	- Budget estimate
29	- Deliverables checklist
30	2. Plan logistics - venue, speakers, sponsors, registration
31	3. Create content - event page copy, social promotion, email invites
32	- Use the relevant content skills (linkedin, blog, email-writer)
33	4. Pre-event checklist - run through 1 week before
34	- Slides reviewed
35	- Demo tested
36	- Promotion sent
37	- Registration confirmed
38	5. Post-event - within 48 hours
39	- Follow-up email to attendees
40	- Content recap (blog post or LinkedIn)
41	- Update `events/_insights.md` with what worked
42	- Log leads in CRM
43
44	## Guardrails
45
46	- Never commit budget without the CAO's approval
47	- Never book venues or sign contracts - present options for the CAO to decide
48	- Drafts only for all outbound communication (invites, promotion, follow-ups)
49	- No attendee PII in public content - names only with permission
50	- Log all events in `events/_published/` after they happen
51
52	## Self-improvement
53
54	After an event is completed:
55
56	1. Move the event brief from `events/_drafts/` to `events/_published/`
57	2. Update `events/_insights.md` with what worked: attendance, engagement, lead quality, logistics that went well or poorly
58	3. If the CAO's edits to event briefs or follow-ups reveal a new pattern (e.g. "always include a networking segment", "keep talks to 20 min max"), add it to the Process section
59	4. If an event format performs well, save the brief and follow-up to `events/_examples/` as a reference template

People who liked this also viewed

6 picks

Type

event-manager

168stars52forks

View on GitHub

How to install event-manager?

getnao/sylph/event-manager

$npx -y skills add getnao/sylph --skill event-manager

Installs into the current project.

Summary

Plan, organize, and follow up on events - meetups, hackathons, conferences, and online events.

Files · 1

View on GitHub

SKILL.md

1	# Event Manager
2
3	Plan, organize, and follow up on events - meetups, hackathons, conferences, and online events.
4
5	## MCP connectors
6
7	\| Connector \| Purpose \|
8	\|-----------\|---------\|
9	\| Calendar \| Create events, send invites \|
10	\| Notion \| Track event planning and logistics \|
11	\| Canva \| Create event graphics and banners \|
12
13	## Event types
14
15	\| Type \| Typical lead time \| Key deliverables \|
16	\|------\|-------------------\|-----------------\|
17	\| Meetup (hosted) \| 3-4 weeks \| Venue, speakers, event page, promotion, follow-up \|
18	\| Hackathon (hosted) \| 6-8 weeks \| Theme, judges, prizes, registration, logistics \|
19	\| Conference talk \| 4-6 weeks \| CFP submission, slides, demo prep \|
20	\| Webinar / online \| 2-3 weeks \| Registration page, slides, recording setup \|
21	\| Sponsorship \| Varies \| Brief, assets, booth materials \|
22
23	## Process
24
25	1. Create event brief - save to `events/_drafts/YYYY-MM-DD_event-slug.md`
26	- Event name, date, type, audience
27	- Goals (leads, community, brand awareness)
28	- Budget estimate
29	- Deliverables checklist
30	2. Plan logistics - venue, speakers, sponsors, registration
31	3. Create content - event page copy, social promotion, email invites
32	- Use the relevant content skills (linkedin, blog, email-writer)
33	4. Pre-event checklist - run through 1 week before
34	- Slides reviewed
35	- Demo tested
36	- Promotion sent
37	- Registration confirmed
38	5. Post-event - within 48 hours
39	- Follow-up email to attendees
40	- Content recap (blog post or LinkedIn)
41	- Update `events/_insights.md` with what worked
42	- Log leads in CRM
43
44	## Guardrails
45
46	- Never commit budget without the CAO's approval
47	- Never book venues or sign contracts - present options for the CAO to decide
48	- Drafts only for all outbound communication (invites, promotion, follow-ups)
49	- No attendee PII in public content - names only with permission
50	- Log all events in `events/_published/` after they happen
51
52	## Self-improvement
53
54	After an event is completed:
55
56	1. Move the event brief from `events/_drafts/` to `events/_published/`
57	2. Update `events/_insights.md` with what worked: attendance, engagement, lead quality, logistics that went well or poorly
58	3. If the CAO's edits to event briefs or follow-ups reveal a new pattern (e.g. "always include a networking segment", "keep talks to 20 min max"), add it to the Process section
59	4. If an event format performs well, save the brief and follow-up to `events/_examples/` as a reference template

People who liked this also viewed

6 picks

Type