Presentation story architecture
Skill samulee003/agentic-ppt-skills/skills/presentation-story-architecture
Agent skills that route a presentation from source to stage-ready through an 8-gate pipeline. Extracted from open-slide.
npx -y skills add samulee003/agentic-ppt-skills --skill presentation-story-architectureAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Turns an approved brief and supported claims into a thesis, audience journey, chapter roles, transitions, and slide-by-slide jobs for the main talk and backup. Use when the story-architecture gate is current for a presentation project or when a router asks for the story and storyboard.
SKILL.md
1.8 KB, as published. Nobody here has run it
Build the story architecture
Use when story-architecture is the current gate.
- Read repo instructions,
PRESENTATION-BRIEF.md,EVIDENCE-LEDGER.md, and the cited source files before structuring the talk. - Require one memorable thesis.
- Require an explicit audience change from where the talk starts to where it should end.
- Write
STORY.mdfromtemplates/STORY.md. - Write
STORYBOARD.mdfromtemplates/STORYBOARD.md. - Build the story from the approved brief and supported evidence claims only.
- If a chapter needs unsupported evidence, return the work to evidence instead of letting the chapter enter the story.
- Assign each chapter a role such as context, tension, proof, decision, action, or closing commitment.
- Write spoken transitions that explain why the next chapter or slide must exist.
- Separate the main-talk range from backup or Q&A material.
- Require one necessary job and one dominant message per slide. Split the slide rather than shrink text or pack distinct messages onto one page. Remove ornamental, duplicate, or “nice to have” pages.
- Keep chapter order tied to the promised audience outcome, not to the order sources were found.
- Allow SCQA but never force it.
- Use another structure when it better fits the product, audience, and evidence.
- Stop once the thesis, audience journey, chapter roles, transitions, main/backup boundaries, and slide jobs are coherent enough for story grilling or prototyping.