Build presentation

Skill ken-guru/skills/skills/presentation/build-presentation

Orchestrator for the installed presentation skill suite. Use when the user wants a guided end-to-end presentation workflow.From its SKILL.md

Install

npx -y skills add ken-guru/skills --skill build-presentation

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 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.

SKILL.md

3.3 KB, as published. Nobody here has run it

Build Presentation (Orchestrator)

Coordinates the Presentation Skill Suite by routing from Project Folder state to the next valid action. It does not contain phase capabilities; each Phase Skill remains independently callable.

Output voice

Apply a lightweight human-voice pass to routing explanations, decision summaries, and completion reports. Prefer concrete state and next actions, preserve the user's requested tone, and leave Project Folder paths, commands, and state names exact. Route every presentation-copy phase through its required standalone unslop pass. The pass must use any editorial preferences recorded in DISCOVERY.json.

Installation boundary

Install this Orchestrator with the complete Presentation Skill Suite. The suite distribution contract keeps each member independently usable after installation.

Startup

Confirm the Project Folder is readable.
If it exists, require PROJECT.json with projectType: "presentation".
Read the Project Folder state and named artifacts directly.
When state is ambiguous or corrupt, report the ambiguity and pause before mutation. Direct the user to inspect or repair the Project Folder.

When the Project Folder is Git-backed, load the conditional Git checkpoint protocol before invoking a Phase Skill.

Routing interface

Detect the first incomplete state in this order:

State	Condition	Next action
Nothing started	`PROJECT.json` is missing	Offer `discover-presentation`
Discovery pending	Discovery is not done	Complete or redo `discover-presentation`
Structure pending	Discovery is done and Structure is not done	Offer `structure-agenda`
Generation pending	Structure is done and required presentation outputs are incomplete	Offer `generate-slides`
Media pending	A Media Spec exists and its owned media phase is not done or skipped	Offer the matching Media Renderer
Proofread pending	Presentation and required media are complete, Proofread is pending	Offer `proofread-presentation`
Complete	Proofread is done or skipped	Report completion and offer an explicit rerun path

Use the detailed state-specific dialogue and recovery options in routing guidance only for the detected branch.

Before advancing from Discovery to Structure or Structure to Generation, verify the applicable Exit Criteria. Advance only after every condition passes and the user has chosen the next action where approval is required.

Sequential invocation

When the user chooses a next action, pass the Project Folder path to the selected Skill. Each Skill reads DISCOVERY.json and PROJECT.json and owns its own preflight, Restart Guard, writes, and completion rule.

After a successful Phase Skill invocation, apply the Git checkpoint protocol when enabled, then read state again before offering the next action. Preserve every unrelated phase record.

The supported sequence is:

discover-presentation → structure-agenda → generate-slides →
generate-images/diagrams → proofread-presentation

Media phases may be skipped or run independently when their Media Specs exist.