add-cli-option
Add a new Remotion CLI or config option by creating an AnyRemotionOption, registering CLI parsing, wiring config setters, and updating documentation. Use when adding or converting command-line flags or Remotion options.
Install
With your agent
Install OMGSkills skill "remotion-dev/remotion:add-cli-option" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/remotion-dev/remotion /tmp/remotion && ln -s /tmp/remotion/.agents/skills/add-cli-option ~/.claude/skills/add-cli-optionFrom README
Add a new CLI option How to convert a hardcoded CLI flag into a proper AnyRemotionOption, or add a brand new one. Create the option definition Create packages/renderer/src/options/ .tsx: The type in AnyRemotionOption and type: as T determines the option's value type. Use boolean, string | null, number | null, etc. The id must be unique and contain only lowercase letters, digits, and hyphens. It determines the /docs/options/ page and the value. It usually matches cliFlag, but shared flags can have distinct option IDs. Set docLink to https://www.remotion.dev/docs/options/ . For negating flags (like --disable-ask-ai → askAIEnabled = false), handle the inversion in getValue. Register in options index packages/renderer/src/options/index.tsx: Add the import (keep alphabetical within the import block) Add the option to the allOptions object This makes it available as BrowserSafeApis.options.myFlagOption throughout the codebase.