Four-skill presentation system: ingest talks into a rhetoric vault, run interactive clarification, generate a speaker profile, then create new presentations that match your documented patterns. Includes an 88-entry Presentation Patterns taxonomy for scoring, brainstorming, and go-live preparation.
96
93%
Does it follow best practices?
Impact
97%
1.21xAverage score across 30 eval scenarios
Advisory
Suggest reviewing before use
A speaker has a 4-slide PowerPoint deck for their talk "The Arc of AI". The closing slide (slide 4) has a purple (#5B2C6F) background. Slide 3 contains the shownotes URL https://jbaru.ch/arc-of-ai as visible text.
The speaker wants a QR code inserted on the closing slide that:
The speaker's profile specifies shortener: "none", so no URL shortening is needed — the raw shownotes URL is encoded directly.
Using the presentation-creator skill, generate the QR code and insert it into the deck. The tracking database should be updated with the QR metadata.
Produce the following files:
deck-with-qr.pptx — The deck with the QR code inserted on the closing slide (slide 4).arc-of-ai-qr.png — The QR code PNG file (should have purple background, white foreground).tracking-database.json — Updated tracking database with a qr_codes[] entry for this talk.verification-report.md — A report documenting:
Download the base deck and vault fixtures from the project repository:
BASE="https://github.com/jbaruch/speaker-toolkit/raw/main/eval-resources/scenario-19"
mkdir -p inputs/vault
curl -L -o inputs/base-deck.pptx "$BASE/base-deck.pptx"
curl -L -o inputs/vault/speaker-profile.json "$BASE/speaker-profile.json"
curl -L -o inputs/vault/secrets.json "$BASE/secrets.json"
curl -L -o inputs/vault/tracking-database.json "$BASE/tracking-database.json"Then copy the deck to the working directory before processing:
cp inputs/base-deck.pptx deck-with-qr.pptxarc-of-aihttps://jbaru.ch/arc-of-ainone (raw URL encoded directly)#5B2C6F (solid fill, set at slide level)The QR PNG can be decoded with pyzbar or zbarimg to verify it encodes the expected URL. The quiet zone (border area) pixels should match the purple background color. The foreground modules should be white because the purple background's WCAG relative luminance (~0.065) is below 0.5.
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
scenario-15
scenario-16
scenario-17
scenario-18
scenario-19
scenario-20
scenario-21
scenario-22
scenario-23
scenario-24
scenario-25
scenario-26
scenario-27
scenario-28
scenario-29
scenario-30
rules
skills
presentation-creator
references
patterns
build
deliver
prepare
scripts
vault-clarification
vault-ingress
vault-profile