kanban-video-orchestrator — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited kanban-video-orchestrator (Agent Skill) and scored it 87/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 3 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 3 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Wrap any video request — from a 15-second product teaser to a 5-minute narrative short to a music video to an ASCII loop — in a Hermes Kanban pipeline that decomposes the work to specialized agent profiles.
This skill does not render anything itself. It is a meta-pipeline that:
The actual rendering happens inside the kanban once it's running, via whichever existing skills + tools fit the scenes — ascii-video, manim-video, p5js, comfyui, touchdesigner-mcp, blender-mcp, songwriting-and-ai-music, heartmula, external APIs, or plain Python with PIL + ffmpeg.
ascii-art, gifs, meme-generation, songwriting-and-ai-music).ascii-video).DISCOVER → BRIEF → TEAM DESIGN → SETUP → EXECUTE → MONITORThe discovery process is adaptive: ask only what is actually needed. Always start with three questions to identify the broad shape:
From the answer, classify the style category. The style determines which follow-up questions to ask. Do not ask all questions at once. Ask 2-4 at a time, listen, then proceed. Make reasonable assumptions whenever the user implies an answer.
For complete intake patterns and per-style question banks, see [references/intake.md](references/intake.md).
Once enough is known, produce a structured brief.md using the template in assets/brief.md.tmpl. Stages:
Show the brief to the user for confirmation before designing the team. The brief is the contract — every downstream task references it.
Pick role archetypes from the library that fit this video. Compose, don't clone. Most videos need 4-7 profiles. The director is always present; the rest are picked by what the brief actually requires.
For the role library and per-style team compositions, see [references/role-archetypes.md](references/role-archetypes.md).
For mapping role → which Hermes skills + toolsets it loads, see [references/tool-matrix.md](references/tool-matrix.md).
Generate a setup script (setup.sh) and run it. The script:
~/projects/video-pipeline/<slug>/)taste/, audio/, assets/hermes profile create --cloneSOUL.md (personality + role definition)brief.md, TEAM.md, and taste/ contenthermes kanban create task assigned to the directorUse scripts/bootstrap_pipeline.py to generate setup.sh from a brief + team-design JSON. See [references/kanban-setup.md](references/kanban-setup.md) for the setup script structure, profile config patterns, and the critical "shared workspace" rule.
Run setup.sh. Then provide the user with monitoring commands:
hermes kanban watch --tenant <project-tenant> # live events
hermes kanban list --tenant <project-tenant> # board snapshot
hermes dashboard # visual board UIThe director profile takes over from here, decomposing the work and routing tasks to specialist profiles via the kanban toolset.
Stay engaged — the kanban runs autonomously but a stuck task or bad output needs human (or AI) judgment.
Monitoring patterns: poll kanban list periodically, inspect any RUNNING task that exceeds its expected duration with kanban show <id>, and check heartbeats. When a worker's output fails review, the standard interventions are:
kanban_comment)For diagnostic patterns, intervention recipes, and the "task is stuck" playbook, see [references/monitoring.md](references/monitoring.md).
Six concrete pipelines covering very different video styles — narrative film, product/marketing, music video, math/algorithm explainer, ASCII video, real-time installation — showing how the same workflow yields very different teams and task graphs. See [references/examples.md](references/examples.md).
asking at least the three baseline questions. A bad brief cascades through the entire pipeline.
every job. A music video that doesn't have a beat-analysis profile will misfire. A narrative film that doesn't have a writer profile will produce incoherent scenes. See references/role-archetypes.md.
dir: workspace. Tasks pass artifacts via shared filesystem and structured handoffs. Every kanban_create call passes workspace_kind="dir" + workspace_path="<absolute project path>".
(--tenant <project-slug>). Keeps the dashboard scoped and prevents cross-pollination with other ongoing kanbans.
relevant renderer should load that skill via --skill <name> on its task or always_load in its profile. Do not re-derive what a skill already provides.
file toolset, the director's SOUL.md rules forbid it from executing work itself. It decomposes and routes only — every concrete task becomes a hermes kanban create call to a specialist profile. The kanban-orchestrator` skill spells this out further.
Aim for the smallest task graph that still parallelizes well and exposes the right human-review gates.
image-to-video) need keys in ~/.hermes/.env or the user's secret store. A worker that hits a missing-key error wastes a task slot. The setup script's check_key helper aborts cleanly if a required key is missing.
SKILL.md ← this file (workflow + rules)
references/
intake.md ← discovery question banks per style
role-archetypes.md ← role library (writer, designer, animator, …)
tool-matrix.md ← skill + toolset mapping per role
kanban-setup.md ← setup script structure & profile config
monitoring.md ← watch + intervene patterns
examples.md ← six worked pipelines
assets/
brief.md.tmpl ← brief skeleton
setup.sh.tmpl ← setup script skeleton
soul.md.tmpl ← profile personality skeleton
scripts/
bootstrap_pipeline.py ← generate setup.sh from brief + team JSON
monitor.py ← polling + intervention helpers~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.