Skip to content
Skills Library
Documents & office · Writing

technical-presentations

/technical-presentations

Use when planning, building, refactoring, or reviewing technical talks or training decks: story arc, claim titles, visual evidence, code slides, checkpoints. On demand only.

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
7
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when planning, building, refactoring, or reviewing technical talks or training decks: story arc, claim titles, visual evidence, code slides, checkpoints. On demand only.

Original author description

Use when planning, building, refactoring, or reviewing technical talks or training decks: story arc, claim titles, visual evidence, code slides, checkpoints. On demand only.

How it works

  1. Hard rules
  2. First: retrieve
  3. Card index
Original SKILL.md headings · 57 lines, 564 words
SKILL.md preview
---
name: technical-presentations
description: >-
  Use when planning, building, refactoring, or reviewing technical talks or
  training decks: story arc, claim titles, visual evidence, code slides,
  checkpoints. On demand only.
license: MIT
---

# Technical presentations

Judgement cards for decks that teach or explain technical work. Mechanics
(pptx editing, rendering, upload) belong to the host's slide tools; this skill
owns pedagogy and design. Load ONE card file below, not all.

## Hard rules

1. **Never modify the owner's source files.** Every new version goes in a
   new file: copy, then edit the copy.
2. **Never remove content from an existing deck.** In the owner's own files,
   only add or update: hide unwanted slides (Google Slides: Slide ›
   Skip slide; pptx `show="0"`) and move unwanted text verbatim into the
   speaker notes. In a new copy, a slide that has a replacement may be
   deleted only when its text is kept verbatim in the replacement's speaker
   notes; no replacement means hide.
3. **Editable output.** Real text boxes, native charts and shapes, web or
   Google fonts only; never text baked into an image.
4. **Brand hook.** Use the project's brand palette file if present (for
   example `palette.md`, `brand.md`, or a theme file the owner names); check
   its pairs against card 9. No palette file: neutral theme plus one accent.
   Never invent brand colours.
5. No learner or audience personal data on slides, notes, or recordings;
   aggregate it.

## First: retrieve

1. `python3 .chaos-engine/tool.py retrieve --store mempalace "<deck> slides decision feedback"`:
   prior owner rules, feedback, rejected styles.
2. `python3 .chaos-engine/tool.py retrieve --store graphify "<topic> code examples"`:
   the real code and names the slides must match.
3. Record `retrieve: used` or `skipped(<reason>)`.

## Card index

| # | Card | Rule | File |
| --- | --- | --- | --- |
| 1 | Audience and outcome | One audience, one "by the end you can" per section. | [plan](references/plan.md#1-audience-and-outcome) |
| 2 | Story arc | ABT per section; alternate what is / what could be. | [plan](references/plan.md#2-story-arc) |
| 3 | Storyboard | Layout per slide first, then copy to fit. | [plan](references/plan.md#3-storyboard) |
| 4 | One idea | One idea per slide; passes the 3-second glance test. | [slide](references/slide.md#4-one-idea) |
| 5 | Assertion-evidence | Claim title (sentence, ≤2 lines) over visual evidence. | [slide](references/slide.md#5-assertion-evidence) |
| 6 | Multimedia | Mayer: coherence, signaling, redundancy, contiguity; Appear/Fade builds only. | [slide](references/slide.md#6-multimedia-principles) |
| 6a | Media treatment | Screenshots untinted and framed; diagrams redrawn natively; decor duotoned; logos greyscale. | [slide](references/slide.md#6a-media-treatment) |
| 7 | Code slides | ≤8 lines, ≥24 pt mono, highlight active line, reveal by copies. | [technical](references/technical.md#7-code-slides) |
| 8 | Data slides | One message per chart; takeaway in the title. | [technical](references/technical.md#8-data-slides) |
| 9 | Type and contrast | WCAG 4.5:1 text, 3:1 large text and marks; never colour alone. | [technical](references/technical.md#9-type-and-contrast) |
| 10 | Retrieval checks | Recall at start; checkpoint every 7-10 slides; interaction every 5-7. | [teach](references/teach.md#10-retrieval-checks) |
| 11 | Worked examples | Worked, then faded, then solo. | [teach](references/teach.md#11-worked-examples) |
| 12 | Voice and demos | Humour tied to the point; demos rehearsed with a reset. | [teach](references/teach.md#12-voice-and-demos) |
| 13 | Refactor a deck | New file; replace with notes, or hide. | [review](references/review.md#13-refactor-a-deck) |
| 14 | Review | Reject the anti-pattern list; render and look. | [review](references/review.md#14-review) |
| 15 | Gotchas | Skipped slides still export to PDF; check glyphs in a real Google upload; Drive replace changes the id. | [review](references/review.md#15-gotchas) |

Evidence behind the cards: [sources](references/sources.md).
Files in this package (7)
  • SKILL.md 4 KB
  • references/plan.md 1 KB
  • references/review.md 2 KB
  • references/slide.md 3 KB
  • references/sources.md 3 KB
  • references/teach.md 1 KB
  • references/technical.md 2 KB

Versions

The database has no other skills named technical-presentations.

Database snapshot: 13.11.2026 · package version 235af7888715 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 91scientific-slides
    Build slide decks and presentations for research talks. Use this for making PowerPoint slides, conference presentations, seminar talks, research presentations, thesis defense slides, or any scientific talk. Provides slide structure, design templates, timing guidance, and visual…
  • 100skill-deck
    Generate slide deck presentations from briefs — use when you need slides, pitch decks, or visual summaries
  • 91scientific-slides
    [EXPERIMENTAL] Build slide decks and presentations for research talks using Nano Banana Pro AI. Generates stunning PDF presentations with AI-generated slides. Use for conference presentations, seminar talks, thesis defense slides, or any scientific talk. Provides slide…
  • 90Presentations
    Read, create or edit PowerPoint or Google Slides decks. Use for presentation, slide deck, PowerPoint, PPT, PPTX, or Google Slides requests.
  • 100google-slides
    Read and write Google Slides presentations - get text, find presentations, create presentations, add slides, replace text, and manage slide content. Use when user asks to: read a presentation, create slides, find slides, add a slide, replace text in a presentation, or manage…
  • 90Presentations
    Generate interactive HTML presentations with Reveal.js. USE WHEN user wants to create pitch decks, slide presentations, or interactive HTML slides.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.