update-chrome-binaries-test-region

Publish Remotion Lambda Chrome binaries to the eu-central-1 test region and update hosted layer and Chrome version references. Use when updating Chrome binaries before full regional rollout.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary procedural skill: precise commands, exact file-level edit lists, validation gates before each risky step, and troubleshooting hints for the known failure mode. The only nit is a slightly long explanation of how run.sh's packaging works internally.

Suggestions

Trim the pack-cli.ts internals (tarball walking, local-cli-package.json emission) to one line — "tests run against the local workspace build, so renderer source changes are picked up pre-publish" — since the skill only needs to run run.sh, not reimplement it.

Dimension	Reasoning	Score
Conciseness	The body is dense with repo-specific facts Claude cannot infer (account id, shell-invocation coupling, exact file paths) and explains nothing Claude already knows. One minor trim candidate: the pack-cli.ts internals paragraph explains tooling the skill merely runs. Anchor 4 — efficient with minor instances of over-explanation.	4 / 5
Actionability	Fully executable throughout: exact commands (aws sts get-caller-identity, the eval export-credentials incantation, bun src/admin/make-layer-public.ts --region=eu-central-1, curl -sI against named URLs) and per-file lists of the exact fields to change. Matches anchor 5 for an instruction-only skill.	5 / 5
Workflow Clarity	Sections form a clear publish → update files → verify sequence with explicit checkpoints (verify LayerArn/Version output, "Continue only when all return HTTP 200", "Do not proceed to publishing all regions until the test region has been verified") and error-recovery guidance for the html-in-canvas failure. The batch-operation validation cap does not apply because validation is present.	5 / 5
Progressive Disclosure	A ~50-line self-contained skill with no bundle files and no content that belongs in a separate reference; the four well-organized sections are sufficient structure, matching the simple-skill exception for progressive disclosure.	5 / 5
	Total	19 / 20 Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, well-scoped description with an explicit use-when clause and a distinctive niche. It is slightly narrow in its trigger phrasing — a user asking to update Chrome version references or docs tables without mentioning the test-region publish might not trigger it.

Suggestions

Broaden the trigger clause to cover the reference/doc updates too, e.g., "Use when updating Chrome binaries, hosted layer versions, or Chrome version references before full regional rollout."

Add a natural synonym such as "publishing Chrome/Lambda layers" to the description so layer-publishing requests also trigger it.

Dimension	Reasoning	Score
Specificity	"Publish Remotion Lambda Chrome binaries to the eu-central-1 test region" and "update hosted layer and Chrome version references" are concrete, artifact-level actions with the region named. Coverage has minor gaps — the docs-table updates and Docker verification the body performs are not surfaced, so it does not reach anchor 5.	4 / 5
Completeness	Both what and when are present, with an explicit "Use when updating Chrome binaries before full regional rollout" clause. The "when" covers only the publish step and does not signal that version-reference updates and Docker verification are in scope, keeping it at anchor 4 rather than 5.	4 / 5
Trigger Term Quality	Natural phrases a Remotion developer would say are present ("Chrome binaries", "Remotion Lambda", "test region", "eu-central-1", "hosted layer", "full regional rollout"), but a few natural variants are missing (e.g., "publish layers", "bump Chrome version"). Anchor 4 fits: good keyword coverage with a few terms missing.	4 / 5
Distinctiveness Conflict Risk	"Remotion Lambda Chrome binaries" plus "eu-central-1 test region" carves out a clear niche with distinct triggers; no plausible conflict with generic skills. Matches anchor 5.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: remotion-dev/remotion
Path: .agents/skills/update-chrome-binaries-test-region/SKILL.md
Commit: 6f4e0d5

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.