weekly-demo-video
Skill573 starsChanged 8 months agoMITView on GitHub
**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.
- Installs packages
In this repository25 other files it gives its agents.
- cli/azd/AGENTS.mdAGENTS.md
- cli/azd/extensions/azure.ai.agents/AGENTS.mdAGENTS.md
- cli/azd/extensions/azure.ai.connections/AGENTS.mdAGENTS.md
- cli/azd/extensions/azure.ai.inspector/AGENTS.mdAGENTS.md
- cli/azd/extensions/azure.ai.projects/AGENTS.mdAGENTS.md
- cli/azd/extensions/azure.ai.routines/AGENTS.mdAGENTS.md
- cli/azd/extensions/azure.ai.skills/AGENTS.mdAGENTS.md
- cli/azd/extensions/azure.ai.toolboxes/AGENTS.mdAGENTS.md
- ext/vscode/AGENTS.mdAGENTS.md
- .github/skills/extension-user-contract-review/evals/fixtures/cli/azd/AGENTS.mdAGENTS.md
- ext/vscode/.github/copilot-instructions.mdCopilot instructions
- .github/copilot-instructions.mdCopilot instructions
- azdSkill
- agentic-workflowsSkill
- azd-code-reviewerSkill
- azd-grpc-contractsSkill
- azd-preflightSkill
- changelog-generationSkill
- extension-user-contract-reviewSkill
- foundry-extension-scenario-authoringSkill
- foundry-extension-scenario-pr-regressionSkill
- foundry-extension-scenario-suite-runSkill
- senseiSkill
- tool-version-upgradeSkill
- weekly-reportSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
Ensure these tools are installed:
- Distinctive: line 59
Use the current week window (7 days).
- Distinctive: line 64
Look for: new commands, UX improvements, perf gains, new flags, agent features.
- Distinctive: line 66
Use explore agents in parallel to research each feature group (give them specific commit SHAs).
- Distinctive: line 74
Follow the conventions strictly:
- Distinctive: line 85
ffmpeg failure: Check the ffmpeg error output.
- Very specific: line 90
All videos go to: <repo-root>/demo-video/
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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/nullExecution Flow
Step 1: Pull latest
cd <repo-root> # the azure-dev repository root
git checkout main && git pull --rebaseStep 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-mergesUse 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.gitignoreto 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)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

