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
All analysis output, rhetoric summary updates, tracking DB entries, and profile data MUST be written in English regardless of the talk's delivery language. For non-English talks:
"English text" (оригинальный текст).
Example: "That's the whole point" (В этом весь смысл) — NOT
"В этом весь смысл" (That's the whole point)[ru] "получается что") — do NOT merge into the main English signature listdelivery_language in the tracking DBIf the pattern taxonomy exists (skills/presentation-creator/references/patterns/_index.md)
but any talks with status "processed" or "processed_partial" have no
pattern_observations (or pattern_observations.pattern_ids is empty), mark them
"needs-reprocessing" with reprocess_reason: "pattern_scoring_added". Report:
"N talks need reprocessing for pattern scoring."
Scan observations against the pattern taxonomy index at
skills/presentation-creator/references/patterns/_index.md (path relative to tile root).
Skip patterns marked observable: false — these are pre-event logistics and physical
stage behaviors that cannot be detected from transcripts or slides. For each observable
pattern/antipattern, determine if the talk exhibits it (strong/moderate/weak confidence),
record evidence, and compute per-talk pattern score:
count(patterns) − count(antipatterns). Return in the pattern_observations field.
When the analysis identifies co-presenters, delivery language, or other structured
metadata, populate the corresponding DB fields (co_presenter, delivery_language,
etc.) — do NOT leave structured data buried only in rhetoric_notes free text.
Backfill empty structured_data from earlier runs using rhetoric_notes.
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