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
First-time setup for the PowerPoint-native deck-editing tooling
(RunDeckOps.bas + run-deck-ops.sh; see rules/deck-editing-rules.md).
macOS + Microsoft PowerPoint only.
Steps 1–4 are manual GUI actions only the user can perform; the agent presents each and the user acts, then the agent proceeds. The Step 5 smoke test verifies the whole setup end-to-end before any real edit — so the agent does not pause to confirm each manual step, it confirms once via the smoke test. Steps 1–4 run once per machine. Step 6 is the recurring per-build flow — read it before every real deck build.
Every path below is absolute. {speaker_toolkit_root} is resolved in
SKILL.md; {vault_root} is config.vault_root from the tracking database.
Expand both before showing a command or a path to the user — they cannot resolve
a placeholder, and Step 3 in particular hands them a path to type.
Never assume this is a first run, and never assume it isn't:
"{python_path}" "{speaker_toolkit_root}/skills/presentation-creator/scripts/deckops-doctor.py" \
--vault-root "{vault_root}"It touches no deck, no template, no macro container, and never launches
PowerPoint. It does restore missing drivers into the plugin's own scripts
directory — the same install-restore the .sh wrappers do, and what keeps a
fresh install from reading as driver drift. That restore runs under --offline
too, and never overwrites an existing driver.
It prints a JSON report whose status says what to do — next_step carries the
same thing as one sentence:
status | What it means | Go to |
|---|---|---|
ok | Set up and current | Step 6 |
setup_required | No macro container on this machine | Step 1 |
macro_unreachable | Container not open, macros off, or the module was NEVER imported | Steps 1–3 |
powerpoint_not_running | Set up; PowerPoint just isn't open | Step 6 |
macro_stale | The macro answered with an old stamp — setup is done, it needs a re-import | Step 3 (Updating) |
macro_stale_inferred | The open container may hold a module with no version macro or still need file approval | Step 3. Check Step 1 if no file-approval prompt appears. |
driver_drift | Shipped drivers don't match their mirrors | Read drivers.problems; it names the fix |
probe_failed | The probe could not run, so the state is UNKNOWN | Read live.detail — usually denied Automation consent (Step 4) |
probe_missing | The probe driver or osascript is absent | Reinstall the plugin |
unsupported_platform | Not macOS | No deck build is possible here |
Exit code separates a diagnosis from a non-diagnosis: 0 when a verdict was
reached (setup_required included — that is a finding, not a script failure),
1 when the probe could not run and the state is unknown.
Pass --offline to skip the live PowerPoint probe; you then get setup_required
versus everything-else, and no reading on whether the macro is current. A
container open from a path other than the canonical one still counts as set up —
container.canonical_mismatch reports the difference, and next_step names the
file the user actually has open rather than sending them to create a second one.
Heads-up for installed plugins: tessl install ships only .md/.py/.json/.sh/.txt
and STRIPS .bas/.applescript, so RunDeckOps.bas and the .applescript
drivers aren't on disk after install. The doctor and the .sh wrappers restore
them automatically from their committed .txt mirrors; a dev checkout already
has them. Nothing here requires a manual restore.
Check PowerPoint → Settings → Security & Privacy for Disable all macros with notification. If PowerPoint suppresses notifications, the user can select this setting to have PowerPoint ask before running macros. If managed Office policy prevents per-file approval, stop and report the restriction. Proceed to Step 2. Microsoft's macro settings for Mac
DeckOps.pptmThe macro must live in a macro-enabled file, never in a real deck. The container goes at ONE canonical path, reused across every talk — the doctor and every error message look for it there:
{vault_root}/.deckops/DeckOps.pptmCreate the directory yourself first, so the Save dialog has somewhere to land:
mkdir -p "{vault_root}/.deckops"Then ask the user to:
DeckOps.pptm and save it to the path above.
In the Save dialog, ⇧⌘G opens "Go to Folder" — paste the expanded directory
there. A dot-directory does not appear in the file list; ⇧⌘. toggles hidden
files if they need to see it.Gotcha to warn about up front: if PowerPoint ever shows "Visual Basic macros
will be removed if you save the file in this format", the user is saving a
.pptx — tell them to click Cancel and save as .pptm instead. A real
deck must never carry the macro.
First, put the .bas somewhere the user can actually reach it. On an
installed plugin the module lives under a hidden .tessl/ directory, which
PowerPoint's Import panel does not show — so export a copy next to the container:
"{python_path}" "{speaker_toolkit_root}/skills/presentation-creator/scripts/sync-deck-drivers.py" \
export --to "{vault_root}/.deckops"It prints the exported path as JSON ({"exported": "..."}). Materializes the
.bas from its mirror first if the install stripped it, and refreshes a stale
earlier export. Give the user that exact absolute path.
Then ask the user to open the VBA editor (Tools → Macro → Visual Basic Editor,
or ⌥F11), select DeckOps.pptm's project in the left pane, then
File → Import File… and choose the exported RunDeckOps.bas. In that panel
⇧⌘G opens "Go to Folder" and ⇧⌘. toggles hidden files — the .deckops directory
starts with a dot, so one of the two is needed. Save DeckOps.pptm (⌘S).
If PowerPoint needs to reopen the file to prompt, close it and reopen the same verified DeckOps file. The user approves macros only for the file they created and populated with the installed toolkit's module. Leave PowerPoint's macro notification setting in effect for other presentations. If the approval prompt is absent, check Step 1 and reopen the file.
Updating the macro later. A plugin update ships a new macro; the copy already
imported into DeckOps.pptm keeps running the OLD code, silently, because nothing
can read VBA source back out of a saved .pptm. Two statuses cover this, and they
are not interchangeable:
macro_stale — the macro ANSWERED with an old stamp. Macros are provably on,
so the re-import below is the whole fix. Until then, any deck wrapper handed
non-ASCII text stops before touching a deck and names this step; ASCII text keeps
working.macro_stale_inferred — the open container READS as holding a module with no
version macro, which is what a container imported before the stamp existed looks
like. Disabled macros silence the probe identically, so this one is an inference:
re-import the module. If the probe still fails, check approval for that file.
Check Step 1 if PowerPoint does not offer approval.How the two are classified is
skills/presentation-creator/scripts/deckops-doctor.py's inspect_container /
verdict.
The re-import, for either: re-run the export command above, then in the VBA
editor right-click the DeckOps module → Remove (No to export) →
Import File… the refreshed .bas → save. Re-run Step 0 to confirm ok.
The first time a script drives PowerPoint, macOS shows an Automation consent
prompt. Tell the user it is GUI-only — it cannot be approved headless — so they
should run the first invocation themselves (or be at the machine to click
OK): System Settings → Privacy & Security → Automation → allow the terminal
to control PowerPoint. After consent is granted once, the agent may run
run-deck-ops.sh itself.
Given the history of lost work with other tools, always test before touching a real deck. One script does the whole thing — it copies the template to a uniquely-named base, builds the shipped 3-slide op sequence (layout 0 and a free text box only, so it runs against any template), and prints where the output landed:
bash "{speaker_toolkit_root}/skills/presentation-creator/scripts/deckops-smoke-test.sh" \
"{template_pptx_path}"{template_pptx_path} is infrastructure.template_pptx_path from the speaker
profile; the template is read-only. An optional second argument sets the output
directory. It prints {"ok":true,"output":"<path>","slides":3,"base":"<path>"}
and exits non-zero when no deck was produced. DeckOps.pptm must be open
(Step 6).
It passes when all four hold:
{"ok":true,...}. Its verify-deck-text.py step
confirms that the arrow, bolt and rocket on slide 2 arrived intact, which also
proves DecodeBridgeText runs in this PowerPoint.Anything else: re-run Step 0 and follow next_step. Only after a clean pass run
the real edit. Delete the throwaway files.
Run this after any change to inject-notes.applescript, against a copy of the
smoke-test output. Every path below is absolute: {check_dir} is a new,
empty directory inside PowerPoint's container, for example the expanded
$HOME/Library/Containers/com.microsoft.Powerpoint/Data/notes-check.
Copy the smoke-test output to {check_dir}/notes-check-base.pptx.
Save this Unicode sentinel map, with notes for slides 1 and 3 and none for
slide 2, as {check_dir}/notes.json:
{"0": "PORT → Factories ⚡ “quoted” — café 日本", "2": "second note"}Record shasum -a 256 "{check_dir}/notes-check-base.pptx", then run:
bash "{speaker_toolkit_root}/skills/presentation-creator/scripts/inject-notes.sh" \
"{check_dir}/notes-check-base.pptx" "{check_dir}/notes-check-out.pptx" \
"{check_dir}/notes.json"It passes when all five hold:
Notes applied: 2.second note, and slide 2's are unchanged.Then check the failure paths. Run each case on its own fresh copy of the smoke-test output, so no earlier case's open presentation or output can affect it, and start each with only the presentations you had open before the check. Cases A, C and D must exit non-zero and must not create their own output file; case B and case E must succeed.
Case A — note past the deck.
Copy the smoke-test output to {check_dir}/case-a-base.pptx.
Save {"9": "x"} as {check_dir}/case-a.json.
Run:
bash "{speaker_toolkit_root}/skills/presentation-creator/scripts/inject-notes.sh" \
"{check_dir}/case-a-base.pptx" "{check_dir}/case-a-out.pptx" \
"{check_dir}/case-a.json"It passes when it fails before PowerPoint is touched, with notes for 0-based slide 9 target slide 10, but the deck has 3 slides, and
{check_dir}/case-a-out.pptx does not exist.
Case B — base already open. PowerPoint opens a run-unique copy, so an open base no longer blocks the run.
Copy the smoke-test output to {check_dir}/case-b-base.pptx and open it in
PowerPoint.
Run:
bash "{speaker_toolkit_root}/skills/presentation-creator/scripts/inject-notes.sh" \
"{check_dir}/case-b-base.pptx" "{check_dir}/case-b-out.pptx" \
"{check_dir}/notes.json"It passes when it exits 0 and writes {check_dir}/case-b-out.pptx with the
sentinel notes, case-b-base.pptx is still open in PowerPoint with no notes
added, and no other presentation is left open. Then close case-b-base.pptx
without saving.
Case C — marker write fails after the copy opens.
Copy the smoke-test output to {check_dir}/case-c-base.pptx. Confirm no
presentation named case-c-base.pptx is open.
Run the driver directly with a marker path in a folder that does not exist:
osascript "{speaker_toolkit_root}/skills/presentation-creator/scripts/inject-notes.applescript" \
"{check_dir}/case-c-base.pptx" "{check_dir}/case-c-out.pptx" \
case-c-base.pptx case-c-out.pptx \
"{check_dir}/missing/opened" "{check_dir}/case-c-stage" "note" "" "note"It passes when it exits non-zero with inject-notes failed at [open]: this run opened case-c-base.pptx but could not record that, the close-without-saving
repair and osascript's original File Manager error (-43, folder not found),
case-c-base.pptx is open in PowerPoint, and {check_dir}/case-c-out.pptx
does not exist. Then close case-c-base.pptx without saving.
Case D — stage write fails.
Copy the smoke-test output to {check_dir}/case-d-base.pptx. Confirm no
presentation named case-d-base.pptx is open.
Run the driver directly with a stage path in a folder that does not exist:
osascript "{speaker_toolkit_root}/skills/presentation-creator/scripts/inject-notes.applescript" \
"{check_dir}/case-d-base.pptx" "{check_dir}/case-d-out.pptx" \
case-d-base.pptx case-d-out.pptx \
"{check_dir}/case-d-opened" "{check_dir}/missing/stage" "note"It passes when it exits non-zero with inject-notes failed at [open]: could not record that stage at {check_dir}/missing/stage, the free-space-or-writable
repair and the shell's original status (1), no presentation named
case-d-base.pptx is open, and {check_dir}/case-d-out.pptx does not exist.
Case E — two runs with one output name at once.
Copy the smoke-test output to {check_dir}/case-e-base.pptx, and create
the folders {check_dir}/e1 and {check_dir}/e2.
Start both runs together:
S="{speaker_toolkit_root}/skills/presentation-creator/scripts"
bash "$S/inject-notes.sh" "{check_dir}/case-e-base.pptx" "{check_dir}/e1/deck.pptx" "{check_dir}/notes.json" &
bash "$S/inject-notes.sh" "{check_dir}/case-e-base.pptx" "{check_dir}/e2/deck.pptx" "{check_dir}/notes.json" &
waitIt passes when both exit 0, both e1/deck.pptx and e2/deck.pptx carry the
sentinel notes, and no presentation from either run is left open.
Steps 1–4 are one-time per machine; this is what happens on EVERY real deck build:
DeckOps.pptm first and keep it open for the entire build. Every macro
pass (BuildDeck, ExpandBuilds, backgrounds, QR) drives a macro that lives in
this file; the scripts call it in the running PowerPoint instance. The
speaker-notes pass runs no macro: it writes through PowerPoint's AppleScript
object model.
If DeckOps.pptm is closed (or PowerPoint quits) mid-build, the next pass fails
with a macro-not-found error — reopen it and re-run that pass.ok. It is the cheap way to
catch a closed container or a stale import before a 40-slide build half-finishes.ExpandBuilds → speaker notes → backgrounds → QR.
ExpandBuilds renumbers later slides, so it runs before the by-index passes
(see rules/deck-editing-rules.md).Use only the build's approved base deck, template, assets, import decks, and
output destination. The shell copies those inputs to a per-run directory in
PowerPoint's container. The macro reads the copies and saves its output
there. The wrapper writes the result to the approved destination using the
shell's existing access. Staging supports Google Drive's File Provider,
where PowerPoint's SaveCopyAs can fail when creating a new file.
container-stage.sh owns the per-run folder under
~/Library/Containers/com.microsoft.Powerpoint/Data/.deckops-stage/.
Its EXIT trap cleans up temporary files, including after a failed run.
Register additional cleanup through container_stage_on_exit <function>.
When PowerPoint's container is absent, the wrappers may use the original inputs and a local output folder. If an authorized file needs a PowerPoint file-access prompt, let the user grant access to that file or provide an accessible copy. Stop the affected pass if access is denied. File staging uses the shell's existing permissions and requires no change to macOS privacy settings.
.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