What problem does it solve? Hackathon teams often build features that judges never score, losing points on presentation, demo impact, and Q&A preparation. This Skill keeps the build aligned with what is actually scored, from ideation through final pitch. ## Core Features & Use Cases - Rubric Scorecard: Score ideas or the current running build 1-10 per criterion (innovation, technical, impact, presentation) with evidence, trend tracking, and a single highest-value fix per hour. - Wow-Moment Engineering: Define one retellable 10-second demo beat that survives bad Wi-Fi and works with seeded data, then protect it on the never-cut list. - Mock Judge Panel: Generate and drill the 8 questions a specific panel will ask, with 20-second answers backed by concrete artifacts and crisp disclosure of mocked parts. - Rival Simulation: For shared problem statements, predict competing teams' likely approaches and sharpen one differentiating beat for the demo. - Use Case: Before a hackathon submission, run the scorecard against the current build on main, identify that the demo's first 90 seconds undersells the technical work, and re-script the opening beat. ## Quick Start Ask the AI to score the current hackathon build against the judging rubric and produce the fix-this-hour recommendation.
