@gonzih/skills-events 1.0.0

package/README.md

@@ -0,0 +1,43 @@
+# @gonzih/skills-events
+
+Events planning skills for Claude Code.
+
+## Installation
+
+```bash
+claude mcp add npm:@gonzih/skills-events
+```
+
+## Skills
+
+### `/event-brief`
+Write a comprehensive event planning brief covering goals, audience, budget, logistics, timeline, and risks.
+
+**Usage:** `/event-brief Annual company all-hands, ~500 employees, Q3, Chicago`
+
+---
+
+### `/vendor-rfp`
+Write a vendor Request for Proposal (RFP) to solicit bids from venues, caterers, A/V companies, or other event suppliers.
+
+**Usage:** `/vendor-rfp Catering RFP for 300-person gala dinner, formal, downtown NYC`
+
+---
+
+### `/run-of-show`
+Create a detailed run-of-show (ROS) timeline — the minute-by-minute production schedule for event day execution.
+
+**Usage:** `/run-of-show Half-day product launch, keynote + 3 breakout sessions, 200 attendees`
+
+---
+
+### `/post-event-report`
+Write a post-event summary and lessons learned report documenting outcomes, budget reconciliation, attendee feedback, and recommendations.
+
+**Usage:** `/post-event-report Annual fundraising gala, 250 attendees, raised $120k vs $100k goal`
+
+---
+
+## License
+
+MIT

package/index.js

@@ -0,0 +1,2 @@
+// @gonzih/skills-events
+// Events planning skills for Claude Code

package/package.json

@@ -0,0 +1,25 @@
+{
+  "name": "@gonzih/skills-events",
+  "version": "1.0.0",
+  "description": "Events planning skills for Claude Code",
+  "main": "index.js",
+  "files": [
+    "skills/"
+  ],
+  "scripts": {
+    "test": "echo \"No tests\" && exit 0"
+  },
+  "keywords": [
+    "claude",
+    "claude-code",
+    "skills",
+    "events",
+    "event-planning"
+  ],
+  "author": "gonzih",
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/gonzih/skills-events"
+  }
+}

package/skills/event-brief.md

@@ -0,0 +1,66 @@
+---
+name: event-brief
+description: Write a comprehensive event planning brief. Use when the user needs to create a structured document covering all key aspects of an upcoming event.
+---
+
+Write a comprehensive event planning brief for the event described below. Structure the brief with the following sections:
+
+## Event Brief
+
+### Event Overview
+- Event name and type
+- Date(s), time, and duration
+- Venue/location (confirmed or proposed)
+- Expected attendance
+
+### Goals & Objectives
+- Primary goals (what success looks like)
+- Secondary objectives
+- Key performance indicators (KPIs)
+
+### Target Audience
+- Audience profile and demographics
+- Estimated attendee breakdown (e.g., VIPs, general attendees, staff)
+
+### Event Theme & Brand
+- Theme or concept
+- Tone and atmosphere
+- Branding guidelines or requirements
+
+### Program & Agenda (High-Level)
+- Key sessions, activities, or milestones
+- Keynotes or featured speakers/performers
+
+### Budget Overview
+- Total budget (if known)
+- Major cost categories (venue, catering, A/V, staffing, marketing, etc.)
+- Budget constraints or priorities
+
+### Logistics Summary
+- Venue setup and layout requirements
+- Catering and F&B needs
+- Audio/visual and technology requirements
+- Transportation and accommodation (if applicable)
+
+### Stakeholders & Responsibilities
+- Event owner / sponsor
+- Internal team leads and their roles
+- Key external vendors or partners
+
+### Timeline & Milestones
+- Planning milestones leading up to the event
+- Key decision deadlines
+
+### Risks & Contingencies
+- Top risks (weather, low registration, speaker cancellation, etc.)
+- Mitigation or contingency plans
+
+### Post-Event
+- Evaluation criteria
+- Debrief and reporting plan
+
+---
+
+Event details provided by the user:
+
+$ARGUMENTS

package/skills/post-event-report.md

@@ -0,0 +1,154 @@
+---
+name: post-event-report
+description: Write a post-event summary and lessons learned report. Use when the user needs to document event outcomes, measure success against goals, and capture insights for future planning.
+---
+
+Write a comprehensive post-event report for the event described below. The report should document outcomes, measure success, and capture actionable lessons learned for future events.
+
+## Post-Event Report
+
+### Executive Summary
+A 2–3 paragraph summary of the event: what it was, how it went overall, and the top 3 takeaways.
+
+---
+
+### Event Overview
+
+| Field | Details |
+|-------|---------|
+| Event name | |
+| Date(s) | |
+| Venue / location | |
+| Event type | |
+| Total attendees | |
+| Staff / volunteers | |
+| Report prepared by | |
+| Report date | |
+
+---
+
+### Goals & Results
+
+For each goal stated in the original event brief, assess whether it was met.
+
+| Goal / KPI | Target | Actual | Status |
+|------------|--------|--------|--------|
+| Attendance | | | Met / Partially Met / Not Met |
+| Attendee satisfaction score | | | |
+| Sponsor/partner objectives | | | |
+| Revenue / fundraising target | | | |
+| [Other KPI] | | | |
+
+---
+
+### Attendance & Registration
+
+- Total registered:
+- Total attended (check-ins):
+- No-show rate:
+- Walk-ins:
+- Breakdown by ticket type / audience segment:
+
+---
+
+### Budget Summary
+
+| Category | Budgeted | Actual | Variance |
+|----------|----------|--------|----------|
+| Venue | | | |
+| Catering / F&B | | | |
+| A/V & production | | | |
+| Staffing | | | |
+| Marketing & promotion | | | |
+| Speakers / entertainment | | | |
+| Miscellaneous | | | |
+| **Total** | | | |
+
+Notes on significant variances:
+
+---
+
+### Attendee Feedback Summary
+
+- Survey response rate:
+- Overall satisfaction (e.g., avg score out of 5 or NPS):
+- Top positive themes:
+  1.
+  2.
+  3.
+- Top areas for improvement:
+  1.
+  2.
+  3.
+- Notable verbatim comments:
+
+---
+
+### Vendor & Partner Performance
+
+| Vendor / Partner | Service | Performance Rating (1–5) | Notes |
+|------------------|---------|--------------------------|-------|
+| | Venue | | |
+| | Catering | | |
+| | A/V | | |
+| | [Other] | | |
+
+Vendors recommended for future use:
+Vendors not recommended / to be replaced:
+
+---
+
+### What Worked Well
+
+1.
+2.
+3.
+
+---
+
+### Challenges & Issues
+
+Document any issues that arose during planning or execution.
+
+| Issue | Impact | How It Was Resolved |
+|-------|--------|---------------------|
+| | | |
+| | | |
+
+---
+
+### Lessons Learned & Recommendations
+
+Actionable insights for the next event:
+
+1. **[Area]:** [What to do differently and why]
+2. **[Area]:** [What to repeat and why]
+3. **[Area]:** [Specific process or vendor change recommended]
+
+---
+
+### Next Steps & Follow-Up Actions
+
+| Action | Owner | Due Date |
+|--------|-------|----------|
+| Send thank-you notes to speakers/sponsors | | |
+| Share post-event survey results with stakeholders | | |
+| Finalize and reconcile budget | | |
+| Archive event assets (photos, recordings, materials) | | |
+| Schedule debrief meeting with team | | |
+| Begin planning for next event | | |
+
+---
+
+### Appendices (list as applicable)
+- Appendix A: Attendee satisfaction survey results
+- Appendix B: Final budget reconciliation
+- Appendix C: Run-of-show (actual vs. planned)
+- Appendix D: Media / press coverage summary
+- Appendix E: Photos and video highlights
+
+---
+
+Event details provided by the user:
+
+$ARGUMENTS

package/skills/run-of-show.md

@@ -0,0 +1,84 @@
+---
+name: run-of-show
+description: Create a detailed run-of-show timeline for an event. Use when the user needs a minute-by-minute or segment-by-segment production schedule for event day execution.
+---
+
+Create a detailed run-of-show (ROS) document for the event described below. The run-of-show should serve as the master production timeline used by all staff, vendors, and stakeholders on event day.
+
+## Run of Show — [Event Name]
+
+**Event Date:** [Date]
+**Event Location:** [Venue, Room/Space]
+**Document Version:** 1.0
+**Prepared by:** [Name/Team]
+**Last Updated:** [Date]
+
+---
+
+### Key Contacts
+
+| Role | Name | Cell/Radio |
+|------|------|------------|
+| Event Director / Lead | | |
+| On-Site Coordinator | | |
+| A/V Lead | | |
+| Catering Lead | | |
+| Security Lead | | |
+| [Other key vendor/staff] | | |
+
+---
+
+### Pre-Event Day Checklist
+- [ ] Venue walkthrough complete
+- [ ] All vendor confirmations received
+- [ ] ROS distributed to all team leads
+- [ ] Contingency plans briefed
+
+---
+
+### Day-of Timeline
+
+Use the following format for each row. Be specific — include responsible party, cues, and notes.
+
+| Time | Duration | Activity / Segment | Owner / Cue | Notes / Details |
+|------|----------|--------------------|-------------|-----------------|
+| [Time] | [X min] | Venue opens / Load-in begins | Venue staff | Dock access required |
+| [Time] | [X min] | A/V setup and sound check | A/V team | — |
+| [Time] | [X min] | Catering setup | Catering team | — |
+| [Time] | [X min] | Staff briefing | Event lead | All staff on-site |
+| [Time] | [X min] | Doors open to attendees | Registration team | Badge check at entry |
+| [Time] | [X min] | Welcome remarks | [Speaker name] | Mic: handheld; Slides: deck A |
+| [Time] | [X min] | [Session / Activity] | [Owner] | [Notes] |
+| [Time] | [X min] | Break | — | Catering to refresh stations |
+| [Time] | [X min] | [Session / Activity] | [Owner] | [Notes] |
+| [Time] | [X min] | Closing remarks | [Speaker name] | — |
+| [Time] | [X min] | Doors close / Attendee departure | Staff | Direct to exits |
+| [Time] | [X min] | Vendor breakdown / Load-out | All vendors | — |
+| [Time] | — | Venue handback complete | Event lead | Final walkthrough |
+
+*(Expand as needed with all segments, transitions, and technical cues.)*
+
+---
+
+### A/V & Technical Cues
+
+| Time | Cue | Description | Triggered By |
+|------|-----|-------------|--------------|
+| | House lights to 50% | Pre-show atmosphere | A/V op |
+| | Welcome video playback | :60 sec opener | A/V op on MC cue |
+| | Microphone handoff | [Speaker A] → [Speaker B] | Stage manager |
+
+---
+
+### Contingency Notes
+- If a speaker is delayed: [action]
+- If A/V fails: [backup plan]
+- If catering is late: [action]
+- Medical emergency: [procedure / contact]
+- Evacuation: [route / assembly point]
+
+---
+
+Event details provided by the user:
+
+$ARGUMENTS

package/skills/vendor-rfp.md

@@ -0,0 +1,77 @@
+---
+name: vendor-rfp
+description: Write a vendor request for proposal (RFP) for an event. Use when the user needs to solicit bids or proposals from vendors such as venues, caterers, A/V companies, or other event suppliers.
+---
+
+Write a professional vendor Request for Proposal (RFP) for the event described below. Structure the document as follows:
+
+## Request for Proposal (RFP)
+
+### Introduction & Background
+- Issuing organization name and brief description
+- Event name, type, and purpose
+- RFP issue date
+- Proposal due date and submission instructions
+
+### Event Overview
+- Event date(s) and duration
+- Venue/location (if known)
+- Expected number of attendees
+- Event format (in-person / hybrid / virtual)
+
+### Scope of Services Required
+Detail the specific services being requested. Tailor this section to the vendor type (e.g., venue, catering, A/V, décor, transportation, photography, etc.). Include:
+- Core deliverables
+- Setup and breakdown requirements
+- Staffing expectations
+- Equipment or materials to be provided
+
+### Proposal Requirements
+Vendors must submit the following in their proposal:
+1. Company overview and relevant experience
+2. References (minimum 3, with contact information)
+3. Detailed service description and approach
+4. Itemized pricing and payment terms
+5. Availability confirmation for the event date(s)
+6. Certificate of insurance (general liability, minimum $X)
+7. Sample contract or standard terms and conditions
+8. Any value-added services or creative enhancements offered
+
+### Evaluation Criteria
+Proposals will be evaluated on:
+- Relevant experience and references
+- Quality and completeness of proposal
+- Pricing and value
+- Flexibility and responsiveness
+- Sustainability or diversity credentials (if applicable)
+
+### Budget
+- Estimated budget range: [Provide if known, or state "budget available upon request"]
+- Payment schedule expectations
+
+### Timeline
+| Milestone | Date |
+|-----------|------|
+| RFP issued | |
+| Deadline for vendor questions | |
+| Proposal submission deadline | |
+| Vendor selection / notification | |
+| Contract execution | |
+| Event date | |
+
+### Submission Instructions
+- Submit proposals to: [Name, email, address]
+- Format: [PDF, online portal, etc.]
+- Questions: Direct all questions to [contact] by [date]
+
+### Terms & Conditions
+- This RFP does not constitute a binding commitment to award a contract.
+- [Issuing org] reserves the right to reject any or all proposals.
+- All proposals become the property of [issuing org].
+- Confidentiality requirements (if any).
+
+---
+
+Event and vendor details provided by the user:
+
+$ARGUMENTS