Individual skill

cdf-video-data-augmentation

Run the CDF Video Data Augmentation Airflow workflow on Kubernetes or OSMO to create Cosmos video-to-video variants and auto-label both source and generated videos. Use for VDA payload authoring, preflight, execution, monitoring, output verification, or result retrieval. OSMO requires external endpoints. Standalone augmentation or auto-labeling configuration belongs to the respective component skill. Not for retrieval-driven CDF pipelines or image-to-video event generation.

skills/cdf-video-data-augmentation/SKILL.md

Read pinned source

Source commit fce3cca4170be75e82c64920654d56ee2811b005

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
3,917
Repository last updated
Nov 9, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Run CDF Video Data Augmentation

Run the existing Video Data Augmentation workflow end to end. Read the
[getting-started guide](../../docs/video-data-augmentation/getting-started.md) and
[payload guide](../../docs/video-data-augmentation/payload-guide.md) before authoring a payload.
Treat the checked-in DAG, payload model, and platform manifest as the source of truth if the docs
and implementation differ.

Use the bundled references progressively:

- Read [setup-and-preflight.md](references/setup-and-preflight.md) when preparing input or checking
  a controller/compute environment.
- Read [payload-contract.md](references/payload-contract.md) before rendering or changing a
  payload.
Back to top