Loading...
Loading...
Found 2 Skills
Structure what a hackathon actually awards - cash versus non-cash medium including no monetary prize at all, total pool size inside the event budget's prizes line, how that pool splits across places and sponsor tracks, and who may legally receive a payout. Use whenever the user mentions hackathon prize amounts, cash versus hardware or credits, splitting a prize pool across tracks, prize eligibility for minors, sponsor employees or cross-border winners, or how winners actually get paid - even if they never say "prize". Names the contest-law, tax and cross-border exposure categories and routes them to counsel or a fiscal host, never stating a threshold or a form name. Do NOT use to rank the projects - use samber/dev-event-organizer-skills@hackathon-judging instead.
Run a startup pitch contest or demo day inside a technical event - the pre-event application and selection funnel, the pitch format and the time it costs, the rubric dimensions an investor judge actually scores, the conflict of interest specific to a judge who may want to invest in the company just ranked, and a prize built from introductions and committed meetings rather than cash. Use whenever the user mentions a pitch competition or demo day, opening applications for startups, picking a slate, briefing an investor jury, pitch time limits, or what the winner gets - even if they never say "pitch contest". Routes securities and contest-law questions to counsel. Do NOT use for projects built during the event - use samber/dev-event-organizer-skills@hackathon-judging instead.