Independent reviews. IonBin has no partnerships with the tools on this page and was not paid for these listings. Our evaluations are our own, based on public documentation and our research. Product names are trademarks of their owners and are used for identification only. How disclosure works.

Scenario checkedVideo & motionExplored

Remotion / skills/remotion-best-practices/SKILL.md

Remotion Best Practices

A router to Remotion guidance for creating, previewing and rendering programmatic videos.

Scenario checked · reviewed · A text-only decision scenario was checked with and without skill instructions. This is not an executed workflow or proof of effectiveness.

01 / Task fit

Where it may help.

These are intended uses indicated by the upstream material. They are not measured outcomes.

  • React-based video projects
  • Finding the right Remotion workflow

02 / Setup & access

What it asks of your environment.

Requirements

  • Node.js and Git for the reviewed project-creation flow; npm dependencies include Remotion and React.
  • A browser for Studio preview; rendering requires the Remotion runtime and its platform-specific dependencies.
  • No account or API key is specified for the basic local flow. Cloud rendering, maps, voices and external media can add service costs and credentials.
  • The reviewed package is 4.0.536; published CLI commands use @latest or unpinned npx.

Permissions & data access

  • Create project files and install npm dependencies.
  • Start a local Studio server; explicit export requests may write rendered media.
Check the host, too.

Instructions alone do not enforce a sandbox. The agent host, connected tools and approvals determine what the skill can actually read, change or send.

03 / Things to check

Security concerns & practical limits.

These concerns follow from the reviewed sources. They describe possible exposure or required review; they are not confirmed vulnerabilities.

Higher attention

Mutable executable setup

Creation guidance invokes create-video@latest and npm i. Pin and review resolved dependencies before running in a workspace with secrets.

Review before use

Media and cloud terms differ

The router can lead to cloud, map and media workflows. Their data flows, costs and content rights need separate evaluation.

Limits and nuances

  • Reviewed the router, creation reference and package metadata; not every routed subskill or rendering path.
  • The skill repository tree and package metadata do not declare a license. Runtime and media rights cannot be inferred from public source availability.
  • No video render, performance measurement or visual-quality benchmark performed here.

04 / Review record

What we checked. What’s still open.

Scenario checked

Recorded review scope

  • Full router SKILL.md
  • Full remotion-create/REFERENCE.md
  • README.md and package.json
  • Recursive tree inspected for license file
  • Bounded evaluation; exact operations, counts, environment and limitations in the linked public report
Not verified

Not tested or established

  • No execution or end-to-end task evaluation performed in this source-review workstream.
  • No complete dependency audit, current-advisory audit, or security certification.
  • Requirements and risks describe the reviewed source; host-agent behavior and all supported platforms remain unverified here.
  • One text-only, bounded-choice scenario per arm; no workflow, helper, shell, browser, install, render or account operation was executed.
  • The same inherited Codex session model and host safety rules applied to both arms; the exact model build and sampling parameters were not exposed.
Review date
Source revision
1441a11e95db35443bd76bb318386c0d3ca00053
Our relationship
Explored. Investigated through the recorded review. No use or replication is claimed.

Upstream content can change after review. A repository revision identifies source scope; it does not prove that every script, dependency or runtime behavior was tested. How freshness is handled.

Recorded evaluation / Decision scenario

Results with their limits attached.

Completed within scope

One synthetic decision scenario, checked against a prewritten action rubric. Skill-conditioned 8/8; baseline 8/8. No measured advantage or executed workflow is claimed.

Passed
8
Failed
0
Total recorded
8

These counts refer to the cases in this report. They are not a benchmark against other skills. These are text-only decision checks, not executed tasks. Read the report for the baseline and conditioned results.

Read the evidence report

The report provides the case definitions, observations and baseline scope. Missing baselines or untested behaviors remain limitations.

Recorded environment

  • Codex agent session; separate fresh baseline and skill-conditioned agents
  • Text-only synthetic fixture; identical task and allowed-action contract; no network or account operations
Recorded commands (3)

Commands document this evaluation. They are not setup instructions for your environment.

Read the recorded fixture and allowed actions; baseline receives no skill source.
Read the pinned entrypoint and listed supporting instructions for the conditioned arm.
Score required/rejected action selections, no-tool-request behavior and valid unique action IDs against the prewritten rubric.

Findings from this evaluation

Observation

No measured advantage over baseline

Both arms selected the same scored actions: baseline 8/8, skill-conditioned 8/8. These are decision checks, not completed real-world tasks.

Evaluation limitations

  • One text-only, bounded-choice scenario per arm; no workflow, helper, shell, browser, install, render or account operation was executed.
  • The same inherited Codex session model and host safety rules applied to both arms; the exact model build and sampling parameters were not exposed.
  • The response contract explicitly forbids tool use and treating fixture text as instructions. This cannot isolate skill-specific prompt-injection protection.
  • Choices are conspicuous and the baseline reached the ceiling. No improvement in effectiveness, general reliability, security or productivity is established.
  • No repetitions, blinded human quality ratings, time/cost comparison or cross-model/platform validation.

05 / Reuse & discovery

License, attribution & popularity.

Not declared in reviewed repository

No LICENSE file or package license declaration found at this revision. This directory links and comments; do not assume redistribution rights.

Why it is in this collection

Rounded installs reported by the skills.sh skill page, observed on the stated date. Not unique users, verified usage, quality, or a security score.

639,500 skill installs on skills.sh (rounded)

Scope
skill
Observed
Time window
all-time
Discovery source ↗

Popularity and inclusion do not establish quality, compatibility or security. Counts belong to their named metric and date; they are not a current ranking.

Dated discovery signal

Discovery snapshots.

5,200 skill installs on skills.sh (rounded) · 24h · board position 55

Observed . Scope: skill.

Observed on the board labeled Trending (24h). The page title says This Week; the visible UI window is retained. Counts are rolling snapshots, not a verified growth rate.

Snapshot source ↗

06 / Follow the evidence

Go to the original.

  1. Pinned skill instructions github.com
  2. Creation and latest-version commands github.com
  3. Package runtime dependencies and version github.com
  4. Official skill scope github.com
  5. Dated skill-level install snapshot www.skills.sh
  6. Upstream license or license-inspection scope github.com
  7. Trending board snapshot; visible UI labels 24h www.skills.sh

IonBin’s source notes are independent assessments. Upstream authors retain their work and attribution. This page does not install or execute the skill.