demo-script

Generate timed, rehearsable hackathon demo scripts with pitch structure and submission checklists.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/vinodkrishna221/Q-Trace --skill demo-script-vinodkrishna221
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: demo-script
Source: https://github.com/vinodkrishna221/Q-Trace/tree/main/.agents/skills/demo-script
Command: npx skills add https://github.com/vinodkrishna221/Q-Trace --skill demo-script-vinodkrishna221

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Hackathon teams often improvise their final demo, running over time, fumbling failures on stage, and missing submission requirements. This Skill produces a timed, beat-by-beat demo script with fallback lines and a submission checklist so the presentation is rehearsed and resilient. ## Core Features & Use Cases - Timed Beat Structure: Breaks a 3-minute demo into open, wow moments, core loop, credibility, and close segments with per-beat click actions, spoken lines, and fallback recovery steps. - High-Scoring Beat Guidance: Engineers in judge-hands-on moments, personal-stake lines, and pre-empted weakness framing based on patterns from winning demos. - Submission Checklist: Produces a T-2h checklist covering title, screenshots, backup video, spine paragraph, stack diagram, and sponsor-tech naming. - Use Case: A team whose walking skeleton just works invokes this Skill during /ship to draft docs/DEMO-SCRIPT.md, rehearse it twice out loud, and finish 20 seconds under the time limit. ## Quick Start Ask the AI to draft a timed 3-minute demo script with per-beat clicks, spoken lines, and fallbacks for your hackathon project, plus the submission checklist.

Frequently Asked Questions about demo-script

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

FAQPage Schema
How do I structure a 3-minute hackathon demo?

Structure a 3-minute demo as: 20-second problem open, an early wow moment, a 90-second core user journey of 4-6 beats, 20 seconds of technical credibility with real numbers, and a 30-second close with impact and the ask. Trim the script to finish 20 seconds under the limit.

How to write a demo script for a hackathon pitch?

Write each beat with the exact click action, a verbatim spoken line of at most two sentences, the screen state, and a fallback line for failures. Script against seeded data and known-good feature flags, then rehearse out loud twice with timing.

What should a hackathon submission checklist include?

Include a retellable title phrase, three screenshots or a hero GIF, a 60-90 second backup video, a spine paragraph, three realistic bullets, a stack diagram, team and repo links, and explicit sponsor technology names for prize searches.

When should I record the backup demo video?

Script the backup video at T-4 hours and record it at T-3 hours before the deadline. Rendering and upload always overrun, and many platforms require the video, so a T-1 hour recording plan risks missing the submission.

What makes hackathon judges score a demo higher?

High-scoring demos hand judges the product directly, include one genuine personal-stake sentence, and pre-empt the obvious weakness before Q&A raises it. Place the first wow moment within the first 40 seconds since judges decide quickly.