youtube-writerlisted

# YouTube Writer The demo video is the highest-signal thing you can share, and it keeps working long after the hackathon: recruiters find these videos on YouTube months later. This writes the title and description so the video is findable and the description does the selling while you are not in the room. ## Gather the facts Detect first, ask second. Read the repo and any existing README or Devpost copy, then ask for what is missing: - Project name and a one-line description of what it does. - The core features (three to five), in plain user-side language. - The stack and any notable integrations. - Hackathon name and any awards (real ones only). - Links: Devpost, GitHub, live URL. - The user's socials (LinkedIn, GitHub) for the follow line. Never invent an award or statistic. ## Write the title Format: `<Project> Product Demo | <what it does>`. For example: ``` DispatchAI Product Demo | AI-powered 911 Response System ``` - Front-load the project name; keep the name and core value inside the first 50 characters (that is what shows in search). - Stay under the 100-character hard cap, and aim for about 70 or fewer. - No clickbait. Offer two or three options. ## Write the description Follow this structure exactly. This is the template, with a real example below it: 1. **Award line** (only if real): `Winner @ <Event> - <Award 1>, <Award 2>, and <Award 3>!` 2. **The hook**: one paragraph opening with "In this video, we're diving into `<Project>`, ..." that says what it