demo-iterate

Automate run-review-fix cycles for .demo.yaml demo specifications.

6|1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/45ck/demo-machine --skill demo-iterate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: demo-iterate
Source: https://github.com/45ck/demo-machine/tree/main/.claude/skills/demo-iterate
Command: npx skills add https://github.com/45ck/demo-machine --skill demo-iterate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Iterative Demo Refinement helps teams improve product demos by guiding run-review-fix cycles to converge on a polished output.

Core Features & Use Cases

  • Structured cycle: Run, Review, Diagnose, Fix, Re-run to tighten a demo spec.
  • Artifact-oriented QA: Checks like output video, events.json, subtitles, and timing validation to ensure consistency.
  • Reproducible improvements: Keeps a history of iterations for audit and reuse.

Quick Start

Run a demo refinement cycle on a given .demo.yaml spec.

Frequently Asked Questions about demo-iterate

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

FAQPage Schema
How do I automate run-review-fix cycles for polishing demo video outputs?

Demo refinement automates run-review-fix cycles by validating .demo.yaml specs against output videos, events.json, and subtitles to iteratively tighten visual demo timing and quality.

What is iterative demo refinement and when do I need it for my pipeline?

Iterative demo refinement is a structured QA process that runs, reviews, diagnoses, and fixes demo specifications. You need it when your demo-machine pipeline requires reproducible improvements to converge on a polished output.

Do I need ffprobe and Node.js to validate demo timing and video quality?

Yes, you need a Node.js environment and access to ffprobe alongside video-rendering tools. These dependencies are required to validate timing and quality checks within the .demo.yaml based capture and rerun pipeline.

How do I validate subtitles and events.json consistency during demo iterations?

You validate subtitles and events.json consistency through artifact-oriented QA checks built into the run-review cycle, ensuring each iteration of your .demo.yaml spec produces reproducible improvements for audit and reuse.

Why does my demo spec produce inconsistent video timing across multiple runs?

Inconsistent video timing occurs when your .demo.yaml spec lacks structured run-review-fix iterations. Applying artifact-oriented QA checks to output videos and events.json helps diagnose and fix timing validation issues for reproducible results.

Can I use demo-machine to capture and rerun iterations for higher-quality visual demos?

Yes, demo-machine integrates with .demo.yaml based pipelines to capture, review, and rerun iterations. This structured cycle keeps a history of iterations for audit and reuse, producing higher-quality visual demo outputs.