demo-presenter

Transform repository evidence into narrated AutoQEC demo presentations.

3|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/qualit527/qec-ai-decoder --skill demo-presenter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: demo-presenter
Source: https://github.com/qualit527/qec-ai-decoder/tree/main/.claude/skills/demo-presenter
Command: npx skills add https://github.com/qualit527/qec-ai-decoder --skill demo-presenter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openai, and includes scripts (resource) components.

What problem does it solve?

Create accurate, evidence-backed AutoQEC demos by turning repository evidence into persuasive narrated presentations that explain why results are correct and what was done.

Core Features & Use Cases

  • Evidence-first narration: assemble and present findings from README.md, demo docs, and artifacts with a clear audit trail.
  • Multi-demo orchestration: coordinate scripted and narrated demos, generate auditable artifacts (manifests, logs, and artifacts).
  • AI-assisted narration: produce natural-sounding narration with optional AI voices and flexible playback options for live or recorded presentations.
  • Provenance-aware storytelling: distinguish mainline results from PR branches, and show what was verified.

Quick Start

Run the Demo Presenter to generate a narrated AutoQEC demo using repository evidence.

Frequently Asked Questions about demo-presenter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create evidence-backed demos from repository documentation?

To create evidence-backed demos from repository documentation, this tool transforms README files, demo docs, and artifacts into narrated presentations. It assembles findings with a clear audit trail to generate both live and scripted walkthroughs.

How does AI narration work for auto-generated demo presentations?

AI narration for demo presentations works by using script-driven TTS via the OpenAI API. It processes repository evidence to produce natural-sounding narration with optional AI voices and flexible playback options for live or recorded sessions.

Can I generate JSON manifests and narration audio from README files?

Yes, you can generate JSON manifests and narration audio from README files. The presentation workflow parses YAML frontmatter and repository artifacts to produce auditable outputs alongside the generated audio tracks.

Do I need an OpenAI API key to generate narrated demo walkthroughs?

Yes, you need an OpenAI dependency to generate narrated demo walkthroughs. The script-driven TTS functionality relies on the OpenAI API to synthesize natural-sounding audio for your evidence-backed presentations.

What is the best way to distinguish mainline results from PR branches in a demo presentation?

To distinguish mainline results from PR branches in a demo presentation, this tool uses provenance-aware storytelling. It highlights what was verified across different repository branches to ensure the narrative accurately reflects the evidence.

What are the limitations of using scripted TTS for AutoQEC demo generation?

A limitation of using scripted TTS for AutoQEC demo generation is that narration quality depends entirely on the OpenAI API voice outputs. Additionally, the accuracy of the auditable artifacts is constrained by the evidence present in the parsed YAML frontmatter and repository docs.