Update to AI Board Lite

{
  "description": "Turns notes, a brief or a document into a board-ready presentation. Builds the storyline first (one message per slide, headline titles), then produces a .pptx when the environment can create files, or a slide-by-slide outline to paste. Use for \"make a deck from this\", \"turn these notes into slides\", \"maak een presentatie hiervan\", \"zet dit in een powerpoint\".",
  "included_files": [],
  "name": "build-deck",
  "skill_md_contents": "---\nname: build-deck\ndescription: Turns notes, a brief or a document into a board-ready presentation. Builds the storyline first (one message per slide, headline titles), then produces a .pptx when the environment can create files, or a slide-by-slide outline to paste. Use for \"make a deck from this\", \"turn these notes into slides\", \"maak een presentatie hiervan\", \"zet dit in een powerpoint\".\n---\n\n# Build Deck\n\nExecutives do not read slides, they read slide titles. So a deck is a\nstoryline first and a file second. Every slide makes one point, and its title\nsays that point as a full sentence. \"Q3 revenue\" is a label. \"Q3 revenue grew\non two customers, not on the market\" is a title.\n\n## Ground rules\n\n- Use only the material the user provides. Every number on a slide comes from\n  that material, quoted exactly. A number you cannot source does not go on a\n  slide.\n- One message per slide. If a slide needs two titles, it is two slides.\n- No filler slides: no \"Agenda\" for fewer than eight slides, no \"Thank you\",\n  no \"Questions?\".\n- Answer in the language the user writes in, and build the deck in that\n  language unless they ask otherwise.\n\n## When to use\n\nThe user shares notes, a memo, a report, figures or a rough outline and asks\nfor a presentation: \"make a deck from this\", \"turn these notes into slides\",\n\"I need five slides for the board\", \"maak een presentatie hiervan\", \"zet dit in\neen powerpoint\".\n\n## Steps\n\n1. **Pin down three things** if they are not clear from the request: who the\n   audience is, what decision or reaction the deck should get, and how many\n   slides there is room for. Ask once, in one message. If the user wants you\n   to just go ahead, assume a board audience and at most eight slides, and say\n   so.\n2. **Write the storyline as titles only.** Open with the answer (the\n   recommendation or the main finding), then the supporting points, then the\n   ask. Read the titles in order: on their own they must tell the whole story.\n3. **Show the storyline to the user** as a numbered list of titles before\n   building anything. Adjust if they want changes.\n4. **Fill each slide** with only what proves its title: three bullets at most,\n   one chart or one table at most, the source of every number in small text at\n   the bottom.\n5. **Build the file.** If this environment can run Python with `python-pptx`\n   (or another way to write `.pptx`), create the deck: a title slide, the\n   content slides, a clean layout with plenty of white space, readable font\n   sizes (titles 28pt or larger, body 16pt or larger) and the source line on\n   every slide that carries a number. Save it only after the user agreed to the\n   storyline, and tell them where it is. If files cannot be created here,\n   deliver the full outline per slide in a form they can paste into\n   PowerPoint, Keynote or Google Slides.\n6. **End with a short checklist** of what the user still has to add or check:\n   missing numbers, a chart they need to supply, a claim that needs a source.\n\n## Output format\n\n```markdown\n## Storyline (6 slides)\n1. Move the pilot to Service: it has the volume and a willing team\n2. Service handles twice the tickets Sales does, on the same headcount\n3. The team lead has already volunteered two people\n4. Risk: data access is not settled, and nobody owns it yet\n5. Cost stays inside this year's budget frame\n6. Decision today: approve Service as the pilot department\n\n## Slide 2\n**Title:** Service handles twice the tickets Sales does, on the same headcount\n- Service: 4,180 tickets in Q2 · Sales: 2,060\n- Both teams: 11 FTE\n- Source: ticket export Q2, tab \"Totals\"\n\n## Still to do\n- Slide 5 needs the budget figure; the notes only say \"within budget\".\n```\n\n## Limits\n\n- The deck is only as good as the material. Missing numbers are flagged, never\n  filled in.\n- Visual design is clean and simple, not a brand template. If the user has a\n  template, ask for it and build on that.\n- Charts are built from the numbers provided. A chart the user only described\n  is listed under \"still to do\".\n"
}