mcpbeat

Weekly Demo Video

azure/weekly-demo-video

>- **WORKFLOW SKILL** — Generate narrated weekly demo videos for azd features. Pulls latest commits, identifies demo-worthy features, researches PRs, and produces MP4 videos with dark-themed slides and neural TTS narration. make demo video, demo for LT, weekly demo video, azd demo. weekly reports (use weekly-report).

2k tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
555
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/Azure/azure-dev --skill weekly-demo-video

What comes with it

3 126 bytes besides the instruction
references/CONVENTIONS.md

The instruction itself

12 sections, as written by the author

Weekly Demo Video Generator

Generates narrated MP4 demo videos for azd features using Python + Pillow + edge-tts + ffmpeg.

Prerequisites

Ensure these tools are installed:

| Tool | Purpose |

|------|---------|

| Python 3 | Script execution |

| Pillow | Slide generation (pip install Pillow) |

| ffmpeg | Video/audio stitch |

| edge-tts | Neural TTS (pip install edge-tts) |

Verify prerequisites (bash):

python3 -c "from PIL import Image; print('ok')"
ffmpeg -version
edge-tts --list-voices > /dev/null

Execution Flow

Step 1: Pull latest

cd <repo-root>  # the azure-dev repository root
git checkout main && git pull --rebase

Step 2: Find commits for the week

Replace the dates below with the actual week range:

git log --oneline --since="YYYY-MM-DD" --until="YYYY-MM-DD" --no-merges

Use the current week window (7 days). For sprint demos, use a 2-week window.

Step 3: Identify demo-worthy features

Group related commits. Skip: typos, CI fixes, test-only, deps bumps, docs-only.

Look for: new commands, UX improvements, perf gains, new flags, agent features.

Use explore agents in parallel to research each feature group (give them specific commit SHAs).

Step 4: Confirm with user

Present a table of proposed demos. Ask user to confirm or adjust before generating.

Step 5: Generate videos

Follow the conventions strictly:

{{ references/CONVENTIONS.md }}

Step 6: Report

List generated videos with filenames and durations. Offer short descriptions for docs.

Error Handling

  • edge-tts failure: Retry once. If it fails again, log the error and skip that slide's audio — notify the user.
  • ffmpeg failure: Check the ffmpeg error output. Common issues: missing codec, invalid image path. Print the error and stop — don't produce a partial video.
  • Font not found: Falls back to ImageFont.load_default() automatically. Warn the user that slides may look different.

Output

All videos go to: <repo-root>/demo-video/

> Note: demo-video/ is listed in .gitignore to prevent accidental commits.

Demo Naming

  • Weekly demos: azd_weekly_demo_{date}_{name}.mp4 (e.g. azd_weekly_demo_may_07_exegraph.mp4)
  • Sprint demos: azd_sprint_demo_{date}_{name}.mp4 (e.g. azd_sprint_demo_apr_28_agent_sessions.mp4)

How to use it

Copy the folder

Take azure/weekly-demo-video from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.

Install what it needs

The instructions reference pip. Without those the skill loads but fails at the first command.