video-production-pipeline
PassAudited by ClawScan on May 7, 2026.
Overview
This instruction-only video workflow shows no code, credentials, or hidden execution, but users should review its multi-agent handoffs, optional publishing steps, and asset caching expectations.
This appears safe to install as an instruction-only workflow. Before using it with real production accounts or private media, confirm which agents and services will receive your content, require explicit approval before publishing or scheduling anything, and understand where generated assets and logs will be stored.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If connected to real agents, scripts, URLs, media assets, and project metadata could be shared between multiple components.
The skill is designed around passing work between multiple specialized agents. This is coherent with the video-production purpose, but real deployments should define which agents receive which user content and assets.
interface AgentOrchestration { mode: 'sequential' | 'parallel' | 'hybrid'; agents: AgentConfig[]; handoffs: HandoffRule[]; errorHandling: ErrorStrategy; }Use only trusted agents, limit what each agent receives, and require review before sharing sensitive project materials outside the main workflow.
If later connected to social or video platform accounts, an accidental publish or schedule action could make content public.
The workflow contemplates public publishing or scheduling at final review. It is framed as a human approval option and no platform credentials or auto-publish code are shown, so this is a notice rather than a concern.
options: ['publish', 'schedule', 'hold-for-review']
Keep publish and schedule actions behind explicit user confirmation and use narrowly scoped platform permissions.
Generated scripts, media, logs, or project history may persist if an implementation follows these recommendations.
The skill recommends retaining project assets and history. This is normal for video production, but the artifacts do not define storage paths, retention, or cleanup behavior.
Cache reusable assets ... Maintain consistency logs ... Track version history
Confirm where assets and logs are stored, how long they are kept, and how to delete them when a project is finished.