skills
- Type
- Skill
- Scanned
- Nov 13, 2026
- Version
- 7e541aa4d736
- Files read
- 266
This project provides guides and code templates that teach AI coding assistants how to create, preview, caption, and render React videos with Remotion. The biggest risk is exposing your secret keys (such as pasting an API key directly into the AI chat or passing license keys in terminal commands), alongside running external scripts and packages without locking them to specific versions.
What it can reach
- Files
- Reads, creates, and edits project code, package files, media assets, captions, map data, and rendered videos, and deletes temporary system files like .DS_Store in empty folders.
- Shell commands
- Runs terminal commands (such as npm, npx, node, and FFmpeg) to set up projects, install or update packages, process media, start a local preview server, and render videos.
- Network
- Starts a local preview server and connects to the internet to fetch documentation, packages, browser tools, AI models, voiceovers, sound effects, and map data from services like npm, remotion.dev, Hugging Face, ElevenLabs, Google Maps, MapTiler, Mapbox, and Cesium.
- Browser
- Opens local video previews in your web browser and runs an invisible background browser to render finished videos.
- Secrets
- Uses environment variables for API keys, license keys, and cloud credentials from ElevenLabs, MapTiler, Google Maps, Mapbox, Remotion, and AWS Lambda.
Findings
-
MediumVoiceover skill instructs the agent to ask for the user's API key in chat
skills/remotion-markup/voiceover.md:16
When a user wants to generate a voiceover without specifying a provider, this guide tells the AI agent to ask the user for their ElevenLabs API key. If the user pastes their secret key into the conversation, it is sent to the AI model provider and stored in chat logs, contradicting the AWS Lambda guide elsewhere in this project which warns never to ask users to paste secrets into chat. This instruction also appears in the duplicate copy under skills/remotion-best-practices/remotion-markup/voiceover.md.
Fix: Instruct the agent to have the user save ELEVENLABS_API_KEY directly in their local .env file and explicitly warn never to paste secret API keys into the chat.
-
LowCaptions guide downloads and saves unpinned remote TypeScript code into the project
skills/remotion-captions/display-captions.md:32
To display captions, this skill instructs the agent to fetch TypeScript code at runtime from a live web URL and save it directly into the project unchanged, where the running Remotion Studio server immediately bundles and executes it. Unlike other templates in this repository that are shipped as local files, there is no version pin or checksum, so a compromise of that web page could execute untrusted code or inject instructions into the agent. This also appears in the duplicate copy under skills/remotion-best-practices/remotion-captions/display-captions.md.
Fix: Ship basic-captions.element.tsx locally inside the skill's assets directory or install it via a versioned npm package instead of fetching raw code from a URL.
-
LowMap components load JavaScript from external CDNs at runtime without Subresource Integrity
skills/remotion-maps/techniques/cesium/assets/CesiumFlythrough.tsx:32
CesiumFlythrough.tsx dynamically injects Cesium.js from cesium.com into the browser without a Subresource Integrity (integrity) hash, and the MapLibre guide (skills/remotion-maps/techniques/maplibre/TECHNIQUE.md) similarly imports a worker script from unpkg.com at runtime without integrity checks. Because these components run inside Remotion Studio, which has local endpoints that edit project source files and access to bundled map API keys, a compromised CDN file could execute arbitrary code in the Studio session. Duplicate copies exist under remotion-best-practices and remotion-markup.
Fix: Import CesiumJS and the MapLibre worker from locally installed npm packages, or add Subresource Integrity hashes (integrity and crossOrigin attributes) when loading from a CDN.
-
LowMapTiler guide advises putting an unrestricted API key into a client-bundled variable
skills/remotion-maps/techniques/maptiler/TECHNIQUE.md:20
The MapTiler instructions tell users to place an unrestricted API key in REMOTION_MAPTILER_KEY (also repeated in 3d-troubleshooting.md). Remotion automatically embeds environment variables prefixed with REMOTION_ into browser JavaScript bundles; if a user later embeds their composition in a public web page using Remotion Player or deploys a Remotion site, visitors can extract the unrestricted key and abuse the user's quota or billing.
Fix: Warn users that REMOTION_ environment variables are exposed in client-side bundles and advise restricting keys by allowed origins, APIs, or usage quotas before any web deployment.
-
LowScaffolding and skill update commands run unpinned npm packages with auto-confirmation
skills/remotion-create/SKILL.md:27
The project creation workflow runs npx create-video@latest --yes (and remotion-upgrade runs npx skills update with --yes), which downloads and executes whatever version is currently tagged latest on npm without version pinning or interactive confirmation, even though the skill itself is pinned to version 4.0.543.
Fix: Pin create-video to the matching Remotion release version (such as create-video@4.0.543) and avoid bypassing confirmation prompts on unpinned npx packages.
-
LowTroubleshooting guide advises using an unrestricted MapTiler API key
To fix 403 errors during headless rendering, the guide tells users to switch to an unrestricted MapTiler key. Because Remotion bundles REMOTION_ prefixed environment variables into client-side JavaScript, removing all restrictions exposes the account to quota theft or billing abuse if a preview or web player is shared.
Fix: Recommend restricting rendering keys by IP address or API scope and using a separate domain-restricted key for any browser-deployed player.
