Organizing & declutter video generation

Picture this: a messy pile of clothes, sorted by a bear’s paws into neat rows, colors shifting into a gradient rainbow—the moment the clear box lid clicks, the frame goes still in the best way. That’s what this skill delivers; describe the scene in one line and generate.

Dependencies: WERYAI_API_KEY + Node.js 18+. When you run the CLI, scripts/video_gen.js must exist; WERYAI_VIDEO_API.md must exist under resources/ (supply both via publish or pre-use assembly). Full commands and JSON fields: see resources/WERYAI_VIDEO_API.md. No other Cursor skills. Default parameters and model tiers are in the tables below; live API limits follow weryai models. Before installing or running, review the bundled video_gen.js to confirm it meets your requirements. Pay particular attention to how it handles local files if you choose to allow their usage, ensuring this behavior aligns with the skill's intended workflow for image-to-video requests.

Registry metadata: The only required runtime secret is WERYAI_API_KEY. It appears in YAML frontmatter as top-level requires.env (flow mapping, for tools that flatten root keys only), metadata.openclaw.primaryEnv, and metadata.openclaw.requires.env. Skill directories and registries should surface that requirement up front so installers see it before download. Never commit the key inside the package.

Before you install or set WERYAI_API_KEY

Complete this checklist before installing the package or placing any API key in the environment:

1. Trust and account fit: Decide whether you trust WeryAI as a processor and whether your key’s permissions and quotas are acceptable for paid video generation.
2. Key hygiene: Do not paste a production key into chat or logs. Start with a limited-scope or test key until you are satisfied with behavior and cost.
3. Review scripts/video_gen.js: Read the bundled script yourself. Non–--dry-run runs send your prompt and image inputs (public https URLs and, when used, bytes uploaded per WERYAI_VIDEO_API.md) to https://api.weryai.com and https://api-growth-agent.weryai.com (models / upload paths as documented). Treat prompts and media as leaving the device.
4. Data sensitivity: If you must limit leakage, run in an isolated or test environment. Use --dry-run on wait / submit-* (see WERYAI_VIDEO_API.md) to inspect the JSON the CLI would send without performing a paid submit.
5. If you are not comfortable with authenticated network calls to WeryAI or with exposing prompts/media to that service, do not set WERYAI_API_KEY or run paid commands.

Prerequisites