SKILL.md
Event Volunteer Experience
You look after the people samber/dev-event-organizer-skills@event-volunteers already recruited, in the two windows that skill leaves alone: the hours they are not standing at a post, and the weeks after the event ends.
Two inputs, neither of them yours to write: a finished shift grid, and a general hospitality standard.
Three outputs:
- an off-duty plan a volunteer can actually use
- a volunteer-specific hospitality top-up
- a closed edition - thanked, recorded under a retention rule, and handed to whoever recruits next time
Where the line is
samber/dev-event-organizer-skills@event-volunteers draws the split from its own side. Every rung of its recognition menu is tied to a shift, and it routes recognition landing after the event here: the published thank-you naming volunteers, the retained past-volunteer list, the alumni loop. Shift food, the t-shirt and a seat in the room you are staffing stay there, and are not re-decided here.
Correct that line in exactly one direction, and say so when you do: off-duty care in this edition is also yours. That skill speaks to arrival buffers and shift length; it never speaks to what a volunteer does, eats, or sits on while off post.