agentleFS
samulee003samulee003/agentic-ppt-skills/skills/presentation-stage-grill/SKILL.md

presentation-stage-grill

Skill0 starsChanged 24 days agoMITView on GitHub

Tests a live prototype or deck as a talk by grilling actual renders, current notes, timing, transitions, and audience challenges, then produces a speaker script. Use when the stage-grill gate is current for a presentation project or when a router asks for speakability, trimming, audience-risk review, and `SPEAKER-SCRIPT.md`.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 5 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use when stage-grill is the current gate.

    line 8
  2. Very specific:

    Read repo instructions, PRESENTATION-BRIEF.md, STORY.md, STORYBOARD.md, GRILL-LOG.md, current speaker notes, and actual page renders before …

    line 10
  3. Distinctive:

    Always explore the files instead of asking the user for discoverable facts.

    line 11
  4. Very specific:

    When the user refers to the page they're currently viewing without naming it, resolve it through the engine's "current page" mechanism (e.g.

    line 15
  5. Distinctive:

    Use actual renders and current speaker notes, not outline-only summaries.

    line 16
  6. Distinctive:

    Strict 1:1 Note Parity: Every slide must have exactly one corresponding speaker note matching its dominant message.

    line 20
  7. Distinctive:

    Behavioral Scaffolding (Kirkpatrick Level 3 Transfer): Ensure actionable tools include verbal rehearsal opportunities and take-home …

    line 22
  8. Distinctive:

    Constructive Context Framing ("Not starting from zero"): When presenting local policy or regional case studies, clearly separate what the …

    line 24
  9. Very specific:

    Run node .agents/skills/make-presentation/scripts/unslop-check.mjs <work-root>/SPEAKER-SCRIPT.md <slide-folder> and rewrite flagged notes …

    line 26
  10. Very specific:

    Write only consequential decisions to GRILL-LOG.md from ../presentation-product-grill/templates/GRILL-LOG.md.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Grill the talk on stage

Use when stage-grill is the current gate.

  • Read repo instructions, PRESENTATION-BRIEF.md, STORY.md, STORYBOARD.md, GRILL-LOG.md, current speaker notes, and actual page renders before judging the talk.
  • Always explore the files instead of asking the user for discoverable facts.
  • Grill in rounds per ../make-presentation/references/grilling-rounds.md when consequential stage decisions are unresolved: ask the whole frontier in one round.
  • Include a recommended answer with each question, worded so "yes" accepts it.
  • Use references/autonomous-stage.md for the autonomous fallback when the user is unavailable (headless run) or the remaining stage decisions are resolvable from the deck and upstream artifacts — apply references/stage-questions.md yourself, resolve each finding with a concrete change and confidence level, and flag any low-confidence load-bearing edit for later human review instead of silently rewriting it.
  • When the user refers to the page they're currently viewing without naming it, resolve it through the engine's "current page" mechanism (e.g. current-slide for open-slide) before judging.
  • Use actual renders and current speaker notes, not outline-only summaries.
  • Apply references/stage-questions.md to representative prototype pages first, then to the full deck when available.
  • Enforce presenter-language constraints, timed trimming, and existing-versus-remaining distinction.
  • Speakability & Spoken-First Phrasing: Speaker notes must be written in natural, fluent spoken phrasing that the presenter can deliver aloud comfortably without stumbling (no dense academic paper sentences).
  • Strict 1:1 Note Parity: Every slide must have exactly one corresponding speaker note matching its dominant message.
  • Adult Attention Management & Active Learning Resets: In presentations longer than 30 minutes, verify that the delivery incorporates structured attention reset switches (e.g. audience polling/temperature checks, buzz-pair sharing, dialogue choral rehearsal, silent reflection) to combat the natural 15–20 minute adult attention decay.
  • Behavioral Scaffolding (Kirkpatrick Level 3 Transfer): Ensure actionable tools include verbal rehearsal opportunities and take-home scaffolds (checklists, pocket cards) so knowledge bridges into daily behavioral change.
  • Language Purity: For international presentations (e.g. English summit), confirm 100% target language consistency across all notes and visible cues with zero stray translation leftovers.
  • Constructive Context Framing ("Not starting from zero"): When presenting local policy or regional case studies, clearly separate what the community/system has already established from the next challenge, avoiding nihilistic or accusatory framing.
  • Separate what the audience can see immediately from what only works after narration.
  • Run node .agents/skills/make-presentation/scripts/unslop-check.mjs <work-root>/SPEAKER-SCRIPT.md <slide-folder> and rewrite flagged notes using ../make-presentation/references/unslop-copy.md. Spoken phrasing still comes first.
  • Sort audience-challenge and trimming findings into Act on, Consider, Noted, or Dismissed using ../make-presentation/references/review-buckets.md.
  • Produce SPEAKER-SCRIPT.md from templates/SPEAKER-SCRIPT.md with approved wording, timing, likely audience challenge, and Q&A risk.
  • Return pages for revision when density, wording, transition logic, or defensibility breaks the live talk.
  • Return passed only when the talk is readable, speakable, timed, defensible, and audience-appropriate.

Write only consequential decisions to GRILL-LOG.md from ../presentation-product-grill/templates/GRILL-LOG.md.

  • Append new decisions without deleting or rewriting entries from other grill phases or earlier runs.
  • Preserve existing decisions when revisiting the stage-grill gate.
  • Log only changes that materially affect wording, timing, page order, trims, likely objections, or presenter language.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.