Remotion Maps
Knowledge for animating maps in Remotion videos: the main file routes to exactly one of five self-contained techniques — a static map image animated on top
- What
- Knowledge for animating maps in Remotion videos: the main file routes to exactly one of five self-contained techniques — a static map image animated on top
- Cost
- Free
- Needs
- Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Knowledge for animating maps in Remotion videos: the main file routes to exactly one of five self-contained techniques — a static map image animated on top, Mapbox (which requires your own Mapbox access token if you choose it), MapLibre (no API key, fully free), MapTiler (annotations over borders, rivers and labels, using your own MapTiler key if you choose it), and CesiumJS 3D terrain flythroughs (MapTiler or Google Maps key depending on the mode). Key-free techniques exist, so no key is needed unless you pick a provider technique. It works in the user's own Remotion project with local commands; no licence was found anywhere in the upstream repository at the pinned commit — see the licence note on this listing. Curated by Skill Harbor — Remotion Maps, by @remotion-dev, listed here with credit to its creator. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into Muse📌 Pinned version: commit 6c67adcBefore you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — Licence and map-key disclosure first: no licence was found anywhere in this repository at the pinned commit (not MIT, not Apache — see the listing's licence note), so the rights are unspecified upstream. Installing needs no account, no key and no payment, and nothing is run. At use time the key depends on the technique you choose: Mapbox requires your own Mapbox access token; the MapTiler technique uses your own MapTiler key (the REMOTION_MAPTILER_KEY environment variable); the Cesium landscape mode also uses a MapTiler key and its city mode a Google Maps API key. Key-free options exist: the MapLibre technique is stated as requiring no API key and fully free, and the static-map technique only needs a map/satellite image you supply yourself. Only ever provide a key for a technique you actually choose. Install "Remotion Maps" for me. It is the Remotion map-animation knowledge set: its short main file makes the agent choose exactly one technique from the intended shot, then load only that technique's TECHNIQUE.md — a static map (a satellite image mounted in an <Img>/<CanvasImage> tag, animated on top), Mapbox (nicer styles, globe view, 3D buildings), MapLibre (no API key, fully free, no 3D buildings), MapTiler (annotations drawn on geographic features: borders, rivers, labels), or CesiumJS (3D flythroughs through terrain, flight-simulator perspective). Each technique folder is self-contained — its own TECHNIQUE.md, references, example components and sample geographic data — and the main file says any technique may be removed without breaking the others. Its folder holds the main SKILL.md, its agents/openai.yaml policy file, its icon, and the five technique folders (including two small prep scripts, prep-geo.mjs and prep-cesium-path.mjs, and a large sample country-metadata JSON). Repository: https://github.com/remotion-dev/skills (the skill is the whole skills/remotion-maps/ folder at the pinned commit: SKILL.md plus 31 companion files, 32 files in total) Pinned version: install the code at commit 6c67adcd9cdbe6eb84d76342da89b225f9161cb2 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/remotion-dev/skills into a temporary folder, check out commit 6c67adcd9cdbe6eb84d76342da89b225f9161cb2, and copy the skills/remotion-maps/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 da116f9bf15fed3eadc48b5ced196a651a9e233ed0cc7a8572ca55d7f4788358 - agents/openai.yaml: SHA-256 9c6c75daec6eabd78cf6fbc7169be3f7dde934df1316e41df6658052056b29ee - assets/remotion-icon.svg: SHA-256 5007669bd0555b0f4565b4e7176fa191310ab0039b2ed09d867a9270f5b0ce58 - techniques/cesium/TECHNIQUE.md: SHA-256 09057e77b67dcda23eed8ddbf1b5bd44541a952f380913a00b3bfddaa39ab675 - techniques/cesium/assets/CesiumFlythrough.tsx: SHA-256 4d4a90e373176e840ae76ae91533fcd9dc445407693b17091c376bb597dbcb10 - techniques/cesium/assets/cesium-path.json: SHA-256 329621928df19d115f93c472a0b7ddbd2463cad502a10722d3c23579a7441d44 - techniques/cesium/assets/city-path.json: SHA-256 3bb420736d196f726b856420b319e21a8d7fc24bca7e626d67e8b00b0544e630 - techniques/cesium/assets/example-Root.tsx: SHA-256 51c2df109015adc992b66b62f1ffc9801ad13f3dc47e4290de40cbe1b8e7809e - techniques/cesium/assets/flight-path.ts: SHA-256 fab65d2d9cc0c4ca56f8a1422494d178c0e57f92a048a4720358d236ced980f0 - techniques/cesium/assets/sample-river.geojson: SHA-256 2c9f6dd35ac4aed56580078046941235ed7e1a5d432a6549dbf7fea4e8d1e9be - techniques/cesium/references/3d-data-sources.md: SHA-256 23ac1acc576d49d599b33c812dc697b264ebe28849088c04e9827cb47b95275f - techniques/cesium/references/3d-flyover-architecture.md: SHA-256 09e1891cec991a246eec60dbcf76c4ea84c52e0bee14321471197703395d0a91 - techniques/cesium/references/3d-troubleshooting.md: SHA-256 c803fe443f5bab1a50408f1f6aa6aded7913577eaefcb586b320c5a96c391bf2 - techniques/cesium/scripts/prep-cesium-path.mjs: SHA-256 6dbb4d1ae3f5fef9f3f6eb23e2a6d58622750714bb847b088ff58a3533839463 - techniques/mapbox/TECHNIQUE.md: SHA-256 8c434f680988a7212a9443ef9be0f62ef734f3d92af4dc47c11dad184677eec9 - techniques/mapbox/references/render-stability.md: SHA-256 96650329df3a870743b6255123e93dba866a37eb1ab1d07c8275efff0d4dead9 - techniques/maplibre/TECHNIQUE.md: SHA-256 8a13debcd2abfce415b5c8b7f323420ec77092d81ceb935853171ca9697b902c - techniques/maplibre/references/render-stability.md: SHA-256 96650329df3a870743b6255123e93dba866a37eb1ab1d07c8275efff0d4dead9 - techniques/maptiler/TECHNIQUE.md: SHA-256 72896873e63d675caaab765941dbb8d668f2790090a63b94e165f254b77ef887 - techniques/maptiler/assets/CountryLabel.tsx: SHA-256 6be8c7d5b3435c8d933f05394ce5e807da5fc9fe0565db94ccaee6ac049df137 - techniques/maptiler/assets/MapTilerVectorElement.ts: SHA-256 c8137792824323b9db997a88c3b923e8072cf2886cd90c38d84fdbbaad8258ed - techniques/maptiler/assets/RiverReveal.tsx: SHA-256 c3091e23dfd80178788d05c0bc43b17aee12aa4236d658f1a97c5acfb29a0f92 - techniques/maptiler/assets/example-Root.tsx: SHA-256 e53677a7a207e37cbc04693eca8ccbab5f5f040efdc67a8b5c030c3913895e83 - techniques/maptiler/assets/sample-data/country-meta.json: SHA-256 470a76cc5a45e58e7e1702cd80f74fcacf9d6e8b1ef7b05011f69853a999ba7b - techniques/maptiler/assets/sample-data/yarlung-flow.json: SHA-256 73a99e77a2ce31cb3ac39be8fe4775d53ecf127a56137b587fca090067dfbb96 - techniques/maptiler/assets/tokens.ts: SHA-256 29ae05eedb4988b5b8f2eb44d241b9c472533fb6ed05d4b33df3e71e0eabc71c - techniques/maptiler/references/map-data-sources.md: SHA-256 b99680cbda8e7d70dc2cb1a8823f66247a21fc59d10c6dae0dd9ba24d2f15b80 - techniques/maptiler/references/map-explainer-architecture.md: SHA-256 e09de8a4d00ea9a82b992918ec4d0302ee18979b73e6c777d584a9743092344f - techniques/maptiler/references/map-geo-prep.md: SHA-256 a97b1913f06195601889d4e090ad056db2fffb7b83918924c8cd92847b3829ef - techniques/maptiler/references/render-stability.md: SHA-256 96650329df3a870743b6255123e93dba866a37eb1ab1d07c8275efff0d4dead9 - techniques/maptiler/scripts/prep-geo.mjs: SHA-256 8265f56bd7c27a7d1a5fa528a77bbe1b29c6acc0e6730233583ca53e2632d490 - techniques/static-map/TECHNIQUE.md: SHA-256 5c1dd66fe41a476fb54474f29388b2caea6d8f73c81c585a761dace5aa8d8647 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 32 files: the 1,030-byte SKILL.md router, agents/openai.yaml, the icon, and 5 self-contained technique folders (static-map, mapbox, maplibre, maptiler, cesium) with their TECHNIQUE.md files, references, example TSX/GeoJSON/JSON assets and 2 prep scripts (.mjs). The prep scripts and examples are copied as-is; nothing in the folder is run during installation. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit. No API key is asked for, read or stored during installation. - At use time exactly one technique is chosen and only its TECHNIQUE.md is loaded. Keys exist only for the provider techniques the user chooses: Mapbox needs the user's own Mapbox token, MapTiler uses the user's REMOTION_MAPTILER_KEY, and Cesium's landscape/city modes use a MapTiler key or a Google Maps API key respectively — those techniques fetch map tiles/styles from their provider at use time. The MapLibre technique needs no key, and the static technique only mounts an image the user supplies. - Do not run a prep script, do not render anything, do not set or ask for any map key, and do not use the skill in any way during this install: using it is a separate step that only starts when I ask for it later. 3. When I say "yes, install", install it as a skill: copy the whole remotion-maps folder into the agent's skills directory, in a folder named exactly "remotion-maps", keeping its 32 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: remotion-maps), the 32 files in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that the key-free techniques (MapLibre, static map) need no key at all, while Mapbox, MapTiler and Cesium need my own provider key only if I choose them, and that the companion router remotion-best-practices also covers this skill). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
- It can create or modify files.
- It works with an API key or a token that you provide.
What the scan found — excerpts from the install prompt
- writes files — Install "Remotion Maps" for me. It is the Remotion map-animation knowledge set: its short main file makes the · Installe-moi « Remotion Maps ». C'est l'ensemble de connaissances Remotion pour les animations de cartes : son
- uses API keys or tokens — Prerequisites — Licence and map-key disclosure first: no licence was found anywhere in this repository at the · - At use time exactly one technique is chosen and only its TECHNIQUE.md is loaded. Keys exist only for the pro · Prérequis — Divulgation licence et clés de cartes d'abord : aucune licence n'a été trouvée nulle part dans ce
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.