Communitygithub.com

report-presentation

Turn a technical report, thesis or project into a talk and slide deck, review and polish existing slides or a talk script, and prepare rehearsal, delivery and Q&A - including thesis defenses, project status talks, conference talks and 3-10 minute short statements. Builds decks in asciidoctor-reveal.js (AsciiDoc) or LaTeX Beamer with PlantUML diagrams and speaker notes, and checks them with a deck statistics script. Use this whenever someone asks to make slides, a deck, a presentation or a talk from a report or results, to review, critique or improve slides or speaker notes, to fit a talk into N minutes, to plan a defense or a status update, or to prepare for questions after a talk.

What is report-presentation?

report-presentation is a Claude Code agent skill that turn a technical report, thesis or project into a talk and slide deck, review and polish existing slides or a talk script, and prepare rehearsal, delivery and Q&A - including thesis defenses, project status talks, conference talks and 3-10 minute short statements. Builds decks in asciidoctor-reveal.js (AsciiDoc) or LaTeX Beamer with PlantUML diagrams and speaker notes, and checks them with a deck statistics script. Use this whenever someone asks to make slides, a deck, a presentation or a talk from a report or results, to review, critique or improve slides or speaker notes, to fit a talk into N minutes, to plan a defense or a status update, or to prepare for questions after a talk.

Works with~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/larsw/report-writing-skills/tree/HEAD/skills/report-presentation

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

Technical presentations

A talk is a new creation, not the report read aloud. A report reaches the head; a talk also reaches the gut. Readers choose their pace and distance (30–40 cm); a listener sees each slide for seconds, from 10 m away, while also listening. Months of work cannot fit into 20 minutes: the talk offers a well-chosen "peek through the keyhole" that each listener can follow and remember.

Method follows H. Hering (with K.-G. Heyne), How to Write Technical and Scientific Reports (3rd ed., Springer 2025), Ch. 5.

Decide which job this is:

  • Create a talk/deck from a report or material → sections 1–5
  • Review an existing deck or script → section 6
  • Rehearse, deliver, answer questions → references/delivery.md
  • Short statement (3–10 min, often unprepared slides) → references/delivery.md, "Short statement"

1. Framework and target (write it down first)

Fill in the framework sheet from references/talk-planning.md with the user, from what they gave you; ask only for what changes the talk:

  • topic and talk title (shorter and more memorable than the report title, still accurate)
  • audience: who, prior knowledge, interests, expectations, who decides
  • occasion and exact time slot without and with discussion
  • type: lecture (inform), technical presentation (inform and influence), persuasive presentation, occasional speech
  • targets with weights, e.g. 70 % inform about results, 20 % show competence, 10 % ease and humour; and the purpose behind them (grade, funding, decision, follow-up project)
  • room, media, remote/hybrid setup; previous and next speakers
  • confidentiality: clear disclosures with the supervisor, boss or customer (and marketing in companies) before external talks

2. Select material

Keep only what is essential, meaningful and representative for this audience and target. Put the rest in a reserve (backup slides, "can" notes) for spare time and questions. Drop every excursion that is interesting mainly to the author.

3. Create the talk structure

Distance yourself from the report's chapters; take the audience's position. Build a few short, memorable items with a dramaturgy:

  • Open with something that creates tension (a question, a problem with concrete consequences, a striking example); close by answering it.
  • Time split about 20 % introduction / 70 % main part / 10 % conclusion for a 20-minute talk (4/14/2 min). For 60 minutes, intro and conclusion grow less than proportionally (8/48/4).
  • Main part for a mixed audience (third-rule), interleaved, not in strict blocks: well-known examples and overview (≈1/3) → new insight at a level most can follow (≈1/6) → expert details (≈1/3), returning to the general level often → aggregation, conclusions, evaluation everyone understands (≈1/6). Nobody should leave thinking "I knew all that" or "that was too complicated".
  • Introduction: contact, target of the talk, course (structure slide), demarcation (what you will not cover).
  • Conclusion: the key results again, a short outlook, nothing new, a clear end.

Record it in the structure design plot (template in references/talk-planning.md) with minutes per part. A 135-page report can become one opening question, one main item with three sub-items, and a conclusion.

4. Slides

Read references/slide-design.md before writing slides. The essentials:

  • "The fewer, the better." 5–7 elements per slide; keywords, not sentences (the final summary slide may use short statements).
  • Each heading states the slide's message in spoken language ("Integrated suction removes 90 % of the fumes"), and maps clearly to the current structure item.
  • Visualize instead of writing; redesign report figures for projection: fewer elements, thicker lines, much larger labels. Never paste a report or journal figure unchanged.
  • Text no smaller than about 1/30 of the slide height (≈ 18 pt on a classic slide); sans-serif; two font sizes per slide at most; colour sparingly and always with a meaning; black on white is most legible; coloured text needs 1.5× the size.
  • No clutter repeated on every slide: no talk title, name, date, "Slide x of y" counter, long footers. A small slide number is fine.
  • Three framework slides: title slide; structure slide with content keywords (not "Introduction / Main part / Summary / Thank you"); final slide that invites discussion (key image, contact data). "Thank you" and "Questions?" are said, not shown.
  • Keep the audience oriented: show the structure again at transitions with the current item highlighted.
  • Animation only for step-by-step builds of lists or processes; never decorative motion or sound.
  • Mark skippable slides (reserve) in advance.

5. Build the deck (asciidoctor-reveal.js or Beamer)

Use the format the user works in: asciidoctor-reveal.js for AsciiDoc projects, LaTeX Beamer when the report is in LaTeX or a PDF deck is required (ask if unclear).

  • reveal.js: references/revealjs-asciidoc.md: one == section per slide, [.notes] speaker notes on every content slide, [%step] for builds, PlantUML diagrams with slide-sized fonts, a custom CSS with the highlight class for structure slides.
  • Beamer: references/beamer.md: one frame per slide with a message title, \note{…} speaker notes, overlays for builds, \AtBeginSection + \tableofcontents[currentsection] for the structure slide, navigation symbols and repeated footlines switched off.

In both formats, write the speaker notes as keywords, not full text, tagged MUST / SHOULD / CAN (what must be said, what can be cut when short of time, what is reserve) and with a "done by mm:ss" checkpoint at each structure item.

Then check it:

python3 scripts/deck_stats.py deck.adoc --minutes 20      # this skill's directory
python3 scripts/deck_stats.py talk.tex --minutes 20       # Beamer: frames, \frametitle, \note, backup after \appendix

It lists per slide the visible words, elements and notes, estimates speaking time from the notes (130 words/min by default), and flags overloaded slides, sentences on slides, missing headings, "Thank you"/"Questions?" slides, generic agenda items and slides without notes. Adjust until the planned time is below the slot (live talks run longer than notes suggest) and every flag is either fixed or a deliberate choice (a short, dense expert slide can be intentional).

Deliver: the deck file (and custom CSS), the framework sheet and structure design plot, the timing table, and a list of reserve slides. Recommend a full, timed trial run with a listener (see references/delivery.md).

6. Reviewing an existing deck or script

  1. Get the framework: audience, slot, target. Without it, slide feedback is guesswork.
  2. Run deck_stats.py (AsciiDoc or Beamer decks) or extract the slide text (.pptx/PDF) and count the same things by reading.
  3. Check the talk as a whole: is it a new creation or the report's ToC on slides? Opening tension and answered question? 20/70/10 time split? Third-rule mix (too superficial for experts or too much jargon for the rest)? Theory first and examples late (a frequent fault)? Intermediate summaries? Reserve material? Clear finish?
  4. Check each slide against references/slide-design.md.
  5. Report by severity (critical: does not fit the slot, wrong audience level, no message; major: overloaded or unreadable slides, report figures unchanged, missing structure orientation; minor: style details). For each slide finding give the slide number/title and a concrete rewrite (new headline, cut list, redesigned figure description). For a scoring-style evaluation of a delivered talk, use the review form in references/delivery.md.

Individual skills in this repo

This repo contains 4 individual skills — each has its own dedicated page.

report-copyedit

Copyedit and line-edit technical and scientific writing (reports, theses, lab reports, papers, specifications, design docs, technical documentation) for clarity, precision, consistent terminology and correct notation, without changing the technical content. Use this whenever someone asks to copyedit, proofread, line-edit, tighten, simplify, polish the language of, improve the readability or flow of, or "fix the English in" a technical text, AsciiDoc, LaTeX or Markdown file; to make terms, units, abbreviations, hyphenation or capitalization consistent; or to build a style sheet from an existing draft. For a whole-document pre-submission review (structure, figures, references, checklist) use report-review instead.

report-drafting

Draft the content of technical and scientific reports - introduction, state of the art, methods/test setup, results, discussion, summary/conclusions, abstract, appendices - together with their figures, tables, PlantUML diagrams, charts, formulas, computations and citations, in AsciiDoc, LaTeX or plain prose. Use this whenever someone asks to write, draft, expand, or turn notes, data, measurements, code or bullet points into a section of a report, thesis, lab report, design report, project report or technical documentation; to create or improve a figure, diagram, chart, caption, table or evaluation/decision matrix for one; to set up equations or a load calculation; or to add citations and a reference list - even if they just say "write up these results".

report-outline

Plan a technical or scientific report before and while drafting it - analyze the assignment, write and test title variants, condense the core message into one sentence, grow a 4-point then 10-point then detailed outline, pick a structure pattern for the report type (lab/test report, design report, project report, thesis, manual, research paper), and set up a style sheet and an AsciiDoc or LaTeX skeleton. Use this whenever someone is starting or reorganizing a report, thesis, lab report, design report, project report or technical documentation and asks for an outline, structure, table of contents, chapter plan, section order, working title or title ideas, or asks "how should I organize this?" - and also to check an existing outline or ToC for logic (lone subsections, unequal siblings, vague headings).

report-review

Review a technical or scientific report, thesis, lab report, design report or technical document as a whole before submission or release - structure and logic, completeness, clarity for a reader without project knowledge, figures and tables, citations and reference list, formulas and notation, terminology consistency, cross-references, open TODO markers and output quality - using a mechanical AsciiDoc/LaTeX linter plus a checklist, and produce a prioritized findings report with concrete fixes. Use this whenever someone asks to review, check, audit, assess, give feedback on, "look over", or do a final/pre-submission/QA pass on a report or thesis (AsciiDoc, LaTeX, Markdown, PDF or Word), asks "is this ready to hand in?", or wants supervisor-style feedback on a draft chapter.

Related Skills