hackathon-pitch-coach

Plans hackathon scope, golden demo paths, and judge-ready pitches from briefs and rubrics.

1|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/tanveerriaz/Skillz --skill hackathon-pitch-coach-tanveerriaz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hackathon-pitch-coach
Source: https://github.com/tanveerriaz/Skillz/tree/main/skills/hackathon-pitch-coach
Command: npx skills add https://github.com/tanveerriaz/Skillz --skill hackathon-pitch-coach-tanveerriaz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Hackathon teams often waste limited time building too many features without a clear story, then fail to demonstrate the one capability judges care about. This Skill turns a challenge brief, time limit, and judging rubric into a focused problem, a reliable demo path, and a credible pitch. ## Core Features & Use Cases - Problem and Scope Selection: Converts a brief, target user, and evidence into a one-sentence product promise with a clearly identified critical dependency. - Golden Demo Design: Defines a short, repeatable demo path with must-have, stretch, and cut features, plus a tested fallback ladder for live failures. - Timeboxed Planning and Pitch Structure: Allocates remaining time across setup, reliability, polish, rehearsal, and submission, and maps pitch emphasis to rubric weights. - Use Case: A team with 90 minutes and a broad wellbeing theme uses the Skill to narrow to one user moment, prove the recommendation engine end to end, map it to the rubric, and reserve the final 15 minutes for rehearsal and submission. ## Quick Start Use the hackathon-pitch-coach skill to turn our hackathon brief, team size, and 24-hour time limit into a scoped build plan, golden demo path, and three-minute pitch outline.

Frequently Asked Questions about hackathon-pitch-coach

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

FAQPage Schema
How do I choose what to build at a hackathon?▼

Choose a problem by identifying a specific user, situation, current workaround, and supporting evidence, then define a one-sentence promise. Rank candidate features by rubric value, demo value, effort, and failure risk, keeping only the critical capability plus one or two supporting features.

How do I structure a hackathon pitch for judges?▼

Structure the pitch as human problem, one-sentence promise, live golden-path demonstration, technical differentiation, then impact and next steps. Weight speaking time toward the dimensions with the highest rubric value and clearly state what is real versus simulated.

What should I do if my hackathon demo fails live?▼

Follow a fallback ladder: retry once with a known-good input, switch to a controlled local fixture, show a recording of the successful path, and use screenshots only as a last resort. Always tell judges when a fixture or recording is being used.

How do I plan time during a short hackathon?▼

Allocate percentages of remaining time: roughly 10% setup, 25% first end-to-end path, 30% core reliability, 15% polish, 10% pitch assets, and 10% rehearsal and freeze. Move the first end-to-end demo earlier when integrations are uncertain.

When should I not use hackathon pitch coaching?▼

Do not use it as a general product strategy or full production project-planning tool. It is scoped to short, judged events where the goal is proving one promise convincingly, not building a complete product.