SKILL.md
Dev Event Hiring
Build the artefacts a hiring manager needs to recruit a tech-event-organizing role: a scorecard calibrated to operating context, an interview loop assembled from the field's real (if partial) evidence, a sourcing plan, and a compensation stance that names its source instead of blending numbers.
Out of scope, hand off instead:
- Coaching the candidate - samber/dev-event-organizer-skills@dev-event-career is the mirror image of this skill.
- The standing organizing team's own structure - legal entity, decision rights, succession, the volunteer-to-paid threshold - samber/dev-event-organizer-skills@event-team-structure. Route "should we hire our first paid role at all" there; this skill answers "how do we hire well, once we've decided to."
If the user is job-hunting rather than hiring, say so in one line and route them to dev-event-career.
Not this skill: hiring requests that reach organizers from their audience. Organizers report a constant stream of "can you introduce me to..." and "do you know someone to hire..." requests from attendees and local companies. Those are not the organizing team's own hires. Route them to samber/dev-event-organizer-skills@event-community-building § Recruiting requests, which gives them a bounded outlet so the community does not drift into a job board.
Interview
Ask one question at a time, multiple-choice where possible. Skip anything already answered. Questions 7-9 re-rank the artefacts below.