CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

An excellent operational runbook: lean, fully actionable, with strong validation checkpoints and clean section organization. No bundle files are needed and none are referenced, so progressive disclosure is satisfied by the well-organized single file.

DimensionReasoningScore

Conciseness

The body is a dense runbook of operational specifics (exact commands, file paths, gotchas) with no concept explanations Claude already knows; every line carries actionable information.

3 / 3

Actionability

It provides copy-paste-ready commands (e.g. `aws sts get-caller-identity`, `eval "$(aws configure export-credentials --format env)"`, `bun src/admin/make-layer-public.ts --region=eu-central-1`, `curl -sI`) and exact file paths to edit.

3 / 3

Workflow Clarity

Steps are sequenced across clear sections with explicit validation checkpoints ("Verify the output prints a LayerArn and Version", "Continue only when all return HTTP 200", "Do not proceed to publishing all regions until the test region has been verified end-to-end").

3 / 3

Progressive Disclosure

It is a single ~50-line file with no need for external bundle references and is organized into clear, well-signaled sections, satisfying the simple-skills guideline.

3 / 3

Total

12

/

12

Passed

Description

85%

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-targeted description that answers both what and when with concrete actions and a distinct niche. The only weakness is narrow trigger-term coverage lacking common variations.

Suggestions

Broaden trigger-term coverage with natural variations a user might say, e.g. 'Use when updating Chrome binaries, bumping the Chromium/headless-shell version, or preparing a Lambda layer rollout'.

DimensionReasoningScore

Specificity

"Publish Remotion Lambda Chrome binaries to the eu-central-1 test region and update hosted layer and Chrome version references" lists multiple concrete actions (publish binaries, update hosted layers, update Chrome version references).

3 / 3

Completeness

It states what ("Publish...and update hosted layer and Chrome version references") and an explicit when ("Use when updating Chrome binaries before full regional rollout"), satisfying both halves.

3 / 3

Trigger Term Quality

"Chrome binaries" and "regional rollout" are natural trigger terms, but coverage is thin with no common variations, matching the anchor for some relevant keywords missing variations. Not 3 because it lacks the broad term coverage of the top anchor; not 1 because the terms are natural and relevant rather than generic jargon.

2 / 3

Distinctiveness Conflict Risk

The niche is extremely specific (Remotion Lambda Chrome binaries, eu-central-1 test region), making it clearly distinguishable and unlikely to trigger for the wrong skill.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
remotion-dev/remotion
Reviewed

Table of Contents

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.