event-feedback

Designs and runs post-event feedback surveys for conferences, meetups, and hackathons.

1|Updated Sep 6, 2026
One-click install
npx skills add https://github.com/samber/dev-event-organizer-skills --skill event-feedback-samber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: event-feedback
Source: https://github.com/samber/dev-event-organizer-skills/tree/main/skills/event-feedback
Command: npx skills add https://github.com/samber/dev-event-organizer-skills --skill event-feedback-samber

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Post-event surveys often fail: they go out too late, run too long, ask questions nobody acts on, or collect answers that never reach the people who need them. This Skill designs the feedback instrument, picks the collection channel, sets the timing, and routes the findings so one edition's answers actually change the next. ## Core Features & Use Cases - Format-adapted question sets: Core conference and meetup questions plus a hackathon layer covering team dynamics, mentors, judging fairness, tooling, and project continuation, with role modules for attendees, speakers, and sponsors. - Channel and timing decisions: Chooses between in-room capture (40-60% response rate) and emailed surveys (10-30%), applies the 24-48 hour send window, and caps reminders at two. - Anonymity and free-text handling: Resolves conflicts like anonymous surveys with prize draws, routes code-of-conduct allegations out of the survey pipeline, and enforces publication consent for quotes. - Findings and hand-off: Groups free text into themes with counts, states response rates beside every finding, and hands results to the debrief, speaker, sponsor, and market-fit processes. - Use Case: Your hackathon ends Sunday and your old conference survey does not fit. The Skill builds a hackathon-specific instrument, captures it in-room at demo day, and schedules a separate follow-up two weeks later on project continuation. ## Quick Start Ask the assistant to design the post-event survey for your event, stating the format, audience size, which roles exist, and whether the event has already happened.

Frequently Asked Questions about event-feedback

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What questions should a post-event survey for a developer conference include?

A short core of 3-5 questions works best: overall satisfaction or likelihood to recommend, one content question, one operations question, and one bounded open question about what to change. Every question must map to a named decision, and questions without one get cut.

When should I send the feedback survey after an event?

Send within 24-48 hours of the event closing, which is strong practitioner consensus though not a measured effect. Follow with at most two reminders days later; more reminders produce fatigue rather than responses.

How is a hackathon survey different from a conference survey?

A hackathon survey adds team formation and dynamics, mentor availability, judging fairness, tooling quality, and project continuation. Continuation is measured by a separate short follow-up one to two weeks later, since asking on demo day only collects intention.

Why did my emailed event survey get almost no responses?

A rate below roughly 10% means the collection failed, not that attendees are indifferent. Common causes are sending more than 48 hours late, a long instrument (very short surveys more than double the median response rate), and skipping reminders.

Can I run a prize draw on an anonymous survey?

No. A prize draw needs an identifier attached to each response, which anonymity forbids, so choose one before fielding. If the instrument rates named judges, mentors, or speakers, keep anonymity and drop the draw.

Should speakers and sponsors get the same survey as attendees?

No. Speakers get an instrument measuring organizer performance such as pre-event communication and equipment, and sponsors get questions on lead quality, audience fit, and renewal intent. Small populations like six sponsors are treated by name, never as percentages.