Turn your notes into a 10-slide deck

Extract the ZIP. Copy its lc-presentation-deck folder into ~/.claude/skills/ for Claude Code or ~/.codex/skills/ for Codex, then refresh the native app. Ask for the skill by name and answer its questions. The package includes the same published instructions and result checks. Native host execution is not yet verified.

For Claude web, use the connector or copy the prompt. Keep private details in your assistant.

Copy, paste into your assistant, then answer its questions. No form or account is required here.

Open in ChatGPT ↗

Already connected? Copy the public starter below and paste into Claude. Keep private details in the chat.

Needed before the promised result: Your notes or outline. You can still copy the reusable prompt and provide these in your assistant.

Saved only on this device. Copy counts contain the skill ID, never your text.

## LazyCoder conversation guide (conversation-v2)
1. Start a conversation, not a form-filling task. Read my latest request and the facts already in this chat before asking anything.
2. Ask only the missing questions needed for the requested result, in a short numbered list (at most three at a time), then WAIT for my answers. Use a native question tool if available; plain chat works too. Never ask me to replace placeholders or fill in a template.
3. Skip questions already answered. Treat unresolved {{placeholders}} and [FIELD LABELS] as missing facts, never literal input. Do not treat an illustrative example as my facts.
4. Use the authored defaults only when relevant; mention material defaults. Ask conditional questions only when their condition applies; if unsure whether it applies, ask. Optional preferences must not block a safe first draft unless the authored instructions require confirmation.
5. Do not invent tasks, dates, names, claims, permissions or missing source material. When required facts are absent, ask and wait instead of producing the final artifact. If everything needed is already supplied, proceed without re-asking.
6. My latest scope correction overrides earlier examples and scope, within the recipe safety and source rules. Resolve conflicts before acting. The authored instructions and output contract remain authoritative; this conversation guide does not grant tool, account, payment or publishing permission.
7. Keep my private answers and generated result in this assistant chat. Do not send them to LazyCoder. Generate the requested format here and check it against the output contract before handing it over.

### Questions to ask only when missing
- What should I use for “Your notes or outline”? [required] Bullets, a draft, a report or an outline. Messy is fine. Include the figures you want to use; the AI won't make any up.
- What should I use for “Who it’s for”? [optional] Who's in the room and what you want them to do after: approve, buy, sign up, change something.
- What should I use for “How long you have”? [optional] The whole slot. Say if questions are part of it, so the timing leaves room for them.
- What should I use for “Number of slides”? [optional] Main slides, title and closing included. Backup slides come on top. Authored default: 10
- What should I use for “Your name and role”? [optional] Optional. Goes on the title slide.
- What should I use for “Look and feel”? [optional] Optional. Your brand colours and font, or a mood. Authored default: clean and simple: white background, one dark blue accent, large plain type

## LazyCoder delivery guide (delivery-guide-v1)
1. Read the latest request, source material and authored requirements first. Ask only for missing facts. Check that this host can create the promised format; use only a fallback explicitly allowed by the authored recipe. If neither is available, explain the gap before starting. Do not promise a rendered film, editable deck or working file when you can only provide its script or outline.
2. Create the complete result in the authored output specification, preserving source facts and the latest agreed scope. Keep assumptions and missing information explicit. Do not silently omit required parts or leave unresolved ingredient markers. Intentional blanks in a reusable template are different from unanswered recipe inputs.
3. Check the actual result against every authored check, including source facts, counts, dates and required sections. Where tools allow it, inspect the actual saved file and compare it with the answer. Record which checks ran, which failed and which still need human or destination review. A filename, render, successful command or preview alone does not prove the promise was met.
4. Hand over the complete editable file, or the complete copyable fallback explicitly allowed by this recipe. Say which delivery you used and any unresolved limitations. Do not report a file as attached, imported, sent or published unless that action actually succeeded. Keep private inputs and output in this assistant; never send them to LazyCoder.
Use existing authorization for ordinary work. Before any additional paid generation, external write or publishing step, check that the current request authorizes that exact action and cost. If it does not, finish the useful authorized draft and ask at that boundary. Never silently retry or replace an ambiguous paid job.
The authored recipe and latest safe scope remain authoritative. This guide grants no new tools, permissions, provider access or claim of successful execution.

## Authored skill instructions
## 1. Outcome
Turn the notes below into a finished presentation: a deck of exactly the number of main slides asked for (part 2 covers a blank or too-small number), with speaker notes, timed to the talk length, delivered as a .pptx file where you can make files, and always as slide-by-slide text in the reply, in the sections set out in part 6. Done means: the slide count is exact, every slide has a point-making title, at most 3 bullets, a specific visual and spoken notes, the slide times add up exactly to the speaking time, the last slide states the ask, and every fact or figure comes from the notes or is marked as missing.

## 2. Context
Notes:
"""
[PASTE YOUR NOTES OR OUTLINE HERE]
"""

Audience and what the speaker wants from them: [WHO IT'S FOR AND WHAT YOU WANT FROM THEM]
Time available: [HOW LONG YOU HAVE]
Number of main slides: 10
Presenter: [YOUR NAME AND ROLE]
Look and feel: clean and simple: white background, one dark blue accent, large plain type

Who it's for: the speaker, who will present it, and the audience named above, who should leave knowing the main message and what they are being asked to do.

Blank fill-ins: a value above that still reads as a capitalised placeholder in square brackets (such as [YOUR NAME AND ROLE]) was left blank. Brackets inside the notes are part of the notes.
- Notes that say "see attached": use the attached file as the notes.
- No notes: reply only "No notes came through. Paste or attach your notes or outline and send again." Never invent a talk.
- No audience: assume "colleagues new to the topic, who should agree with the main message", and say "Audience assumed, please confirm" in the brief.
- No time: assume 1 minute per main slide with no Q&A, and say "Time assumed: <n> minutes" in the brief.
- Number of slides blank or not a number: use 10, and say "10 slides used (no number given)" in the brief.
- Number of slides under 4: use 4, and say "You asked for <n>; a deck needs at least 4 (title, problem, answer, ask), so it has 4" in the brief.
- "The slide count used" below means the number you settled on here.
- No presenter: leave the name off the title slide.

## 3. What to pull out
- The main message: the one sentence the audience should remember.
- The ask: what the audience should do, decide or believe after the talk. Take it from the audience line, or from the notes if it isn't there.
- The evidence in the notes: figures, results, examples, quotes and dates, each with its source if the notes give one.
- Problems, risks and objections the notes mention or the audience is likely to raise.
- Detail that is useful but would crowd the main flow: it goes to backup slides.

Edge cases:
- Thin notes (a topic or a few lines): build the arc from them and use only general, well-known reasoning in the wording. Never add a figure, name, date, quote or result; where a slide needs one, put "Needs: <what evidence>" on the slide and list it in section 6.
- Figures that conflict in the notes: put neither on the slide as fact; write "Notes give <x> and <y>, check" in the speaker notes and list it in section 6.
- Long notes: keep what supports the main message and the ask; move the rest to backup slides. Never drop the ask.
- More slides than the time allows (under 30 seconds each): keep the requested count, give each slide its share, and say "Tight: <n> seconds a slide" in the brief.
- Q&A: if the time available says it includes questions, reserve that time and plan the slides for the rest. If it doesn't mention questions, all of it is speaking time.
- Notes in another language: write the deck in the language of the notes, unless the audience line asks for another.

## 4. Steps
1. Read all the notes. Write the main message and the ask in one sentence each.
2. Work out the speaking time: time available minus any Q&A time.
3. Plan the arc across the main slides. Slide 1 is the title slide; its title is the hook, with the presenter's name under it if given. The hook is a striking fact or figure from the notes, or a question to the audience; never an invented story, example or anecdote. Then the problem or context; then the evidence; then the answer or plan; the last slide is the ask. Give each main slide one point.
4. Give each slide a time, in steps of 15 seconds, so the times add up exactly to the speaking time. If the speaking time isn't a whole number of 15-second steps, round it to the nearest 15 seconds and say "Timed to <m:ss> (rounded from <m:ss>)" in the brief. Give the hook, the evidence and the ask more time than transitions where the steps allow; the exact sum always wins.
5. Write each slide: its title, its bullets, its visual and its speaker notes, sized to its time.
6. Write the backup slides, likely questions, and what is missing.
7. Build the .pptx if you can make files (part 8), then run the self-check.

## 5. Rules
- Titles: one full sentence that states the slide's point, at most 12 words ("Returns fell 18% after the size guide went live", not "Results"). Slide 1's title is the hook and may be a question.
- Bullets: at most 3 per slide, at most 10 words each, about 30 words on the slide in all. The title slide and the closing slide may have fewer.
- Visual: name the type and what it shows ("bar chart: returns per month, Jan–Jun, with the launch marked"), never just "add an image". Use only data from the notes; if the visual needs data the notes lack, say "Needs: <data>".
- Speaker notes: what the speaker says, in short spoken sentences, at about 130 words per minute of that slide's time (within 15%). If the speaking time is over 20 minutes, write talking points instead, about one per 45 seconds of the slide's time (4–8 per slide), and say so in the brief.
- Each slide's notes end with a one-line bridge to the next slide (except the last).
- Facts: use only the notes. Never invent a figure, source, customer, quote, name or date. Round figures only as the notes allow.
- Times: write as m:ss, such as 1:30.
- Tone: confident and plain, suited to the audience; spell out the notes' shorthand and abbreviations.

## 6. Output
Use these sections in this order. Write "None" under any that is empty.
1. **Brief**: audience, the ask, the main message, total time, speaking time, Q&A time, and any assumption or "Tight" note from part 2 or 3.
2. **Slides**: for each main slide, in order:
   - "Slide <n> of <the slide count used> · <time> · ends at <running clock>"
   - Title
   - Bullets (at most 3)
   - Visual
   - Speaker notes
3. **Timing**: one line, "Speaking time <m:ss> (the last slide ends at <m:ss>) · Q&A <m:ss>", with "Q&A none" if none was reserved. The per-slide times are in the slide headers only.
4. **Backup slides**: up to 4, each with a title, bullets and visual, for detail moved out of the main flow or for likely questions. Not counted in the slide count or the timing.
5. **Likely questions**: 3–6 questions this audience is likely to ask, each with a 1–2 sentence answer from the notes, or "Answer not in your notes" with what would answer it.
6. **To fill before you present**: every "Needs:" marker and every conflict, by slide number, saying what is missing.
7. **The file**: if you made the .pptx, its name and the download link, and that the speaker notes are in the notes pane. If you can't make files, write "No file made here. Copy each slide's title and bullets into your slide app, and its speaker notes into the notes box under the slide." and nothing else in this section. Never say a file was made, or give a link, unless you actually created the file in this reply; if unsure, use the no-file line.

The .pptx, when you can make files: 16:9; one slide per main slide in order, then the backup slides after a divider slide titled "Backup"; the title in the title box; bullets in the body at 24 pt or larger, titles at 32 pt or larger; the visual drawn simply where you can (a chart from the notes' own figures, a simple diagram) or otherwise a clearly labelled box saying "Visual: <description>"; the speaker notes in each slide's notes pane; colours and fonts from the look and feel above, used the same on every slide; no images fetched from the web. Name the file after the talk, such as pilot-proposal.pptx.

## 7. Self-check
Before replying, check each of these and fix any failure:
- There are exactly the slide count used, numbered in order, plus backups that are not counted, and every header shows that count.
- Every title is one full sentence that states a point (slide 1: the hook), at most 12 words.
- No slide has more than 3 bullets or more than 10 words in a bullet.
- Every slide has a specific visual and speaker notes.
- The slide times add up exactly to the speaking time, and the last "ends at" equals it.
- Each slide's notes are within 15% of 130 words per minute of its time (or are talking points, about one per 45 seconds, when speaking time is over 20 minutes).
- Slide 1 is the title slide with the hook as its title, taken from the notes or a question, not an invented story; the last slide states the ask from the brief.
- Every figure, name, date and quote is in the notes; everything else is a "Needs:" marker listed in section 6.
- A file is mentioned only if you actually created it, and then it has the same slides, notes and order as the reply.
Then reply with the output only, ending with one line: "Checked: <n> slides, <m:ss> speaking time, <n> to fill."

## 8. Setup
Works as one paste in any chat app. Where the app can run code or create files, it builds a real .pptx with your speaker notes in the notes pane; where it can't, you get the full deck as text to copy into PowerPoint, Keynote or Google Slides. If your notes are a file, attach it and write "see attached" in the notes block.

Paste the result after your assistant creates it. This optional check stays in this tab and is not sent to LazyCoder.