Twelve skills for conference speakers covering rhetoric analysis, talk authoring, deck building and export, CFP submissions, publishing, illustrations, shownotes, screencast production, and vertical shorts, informed by a 113-entry Presentation Patterns taxonomy (83 observable: 64 patterns + 19 antipatterns; 30 unobservable: 21 patterns + 9 antipatterns).
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Medium
Suggest reviewing before use
Slide structure is created by the real PowerPoint app via the BuildDeck macro
(scripts/build-deck.sh), driven by a flat op sequence — never python-pptx, never
the MCP PPT server. The agent emits the ops; BuildDeck executes them. Op
vocabulary and state rules: skills/presentation-builder/references/deckops-spec.md.
Speaker notes MUST be injected as a separate step AFTER all slides are created,
never inline during slide creation. Inject them with scripts/inject-notes.sh —
see Keynote Compatibility below.
The clean deck retains only the template's layout definitions, no demo/sample
slides. BuildDeck deletes the template's demo slides before creating content,
so stripping is not a separate step.
Keynote uses a stricter OOXML parser than PowerPoint. The rules below
prevent generated .pptx files from being rejected on import.
Inject notes via the real PowerPoint app (scripts/inject-notes.sh); it writes
the required <p:notesMasterIdLst> element natively. No manual patch — the
python-pptx pass that omitted-then-patched it is retired. See
rules/deck-editing-rules.md.
The notes driver sets each note through PowerPoint's AppleScript object model,
never through run VB macro.
Connectors emit <p:cxnSp> elements that Keynote's parser may reject. For a
decorative line, emit a thin SHAPE op with a rectangle msoAutoShapeType (a
small height makes it read as a line) — never a connector.
This applies to any residual python-pptx editing of a deck (e.g. the scrim /
title apply pass). Do not create a shape through python-pptx and then delete it
with element.getparent().remove(element) in the same flow — python-pptx's
internal state diverges from the serialized XML and strict parsers (Keynote)
reject the result. If a shape is not needed, do not create it. Narrowly scoped
XML cleanup utilities that remove pre-existing elements are fine — they operate
on elements not managed by python-pptx's in-memory state.
.tessl-plugin
rules
skills
cfp-writer
references
illustrations
presentation-builder
presentation-creator
references
patterns
build
deliver
prepare
scripts
presentation-publisher
screencast-editor
screencast-recorder
shorts-producer
shownotes-publisher
vault-clarification
vault-ingress
references
scripts
vault-profile