CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

web-renderer-test

Add explicitly requested web renderer tests or update existing ones for implementation changes.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/web-renderer-test/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

A strong, disciplined skill body: it gives complete executable examples, exact paths, and a clear checklist, while staying lean and assuming competence. The only real gaps are the absence of feedback-loop guidance for failing/changed snapshots and a couple of wordy phrasings.

DimensionReasoningScore

Conciseness

The body is lean with no concept explanations (it never explains what vitest or snapshot testing is) and all code blocks are load-bearing, matching anchor 4. Minor trims exist — the hedging phrasings 'A test file can for example be executed using' and 'A fixture looks like this for example', plus step 4 repeating the vitest command already shown above — which keep it below the 'every token earns its place' anchor 5.

4 / 5

Actionability

Guidance is fully executable and copy-paste ready: the run command 'bunx vitest src/test/video.test.tsx', a complete fixture with all composition fields, a complete test showing renderStillOnWeb plus the testImage({blob, testId}) call, and exact file paths for fixtures, Root.tsx, and limitations.mdx. This covers the common case end-to-end, matching anchor 5 rather than anchor 4, which expects minor gaps.

5 / 5

Workflow Clarity

The 5-step numbered list with two flagged **Important** steps (Root.tsx registration, docs update) and step 4 running the test as a checkpoint matches anchor 4's 'clear sequence with most checkpoints present'. It is not 5 because there is no error-recovery guidance — e.g., what to do when a snapshot legitimately changes (vitest snapshot update), a common failure mode for visual snapshot tests; it is above anchor 3 because the run step and the Important flags catch the likely failure modes.

4 / 5

Progressive Disclosure

The skill is self-contained with well-organized sections ('Keep the suite small', 'Example', 'Adding a new test'), no bundle files, and no content that belongs in a separate reference — the example code is illustrative and correctly inline. Per the simple-skill note, no external references are needed, so this matches anchor 5's easy navigation and appropriate placement rather than anchor 4, which expects organization gaps.

5 / 5

Total

18

/

20

Passed

Description

53%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.

The description is accurate and honest about its narrow scope, with a clear 'what' and a distinctive niche, but it reads more like a policy statement than a trigger. It lacks an explicit 'Use when...' clause and natural trigger synonyms that would help it fire at the right moments.

Suggestions

Add an explicit trigger clause, e.g. 'Use when modifying code in packages/web-renderer and existing tests need updating, or when the user explicitly asks to add renderer tests.'

Include natural trigger synonyms users would actually say: 'snapshot tests', 'visual tests', 'vitest', or 'web-renderer test suite'.

Mention the visual snapshot testing methodology (e.g., 'add or update visual snapshot tests') to make the 'what' more concrete and further distinguish it from generic testing skills.

DimensionReasoningScore

Specificity

'Add explicitly requested web renderer tests or update existing ones for implementation changes' names the domain plus two concrete actions (add, update), matching anchor 3 ('1-2 concrete actions, but not comprehensive'). It is not 4 because add/update are variants of one activity rather than several distinct actions, and it omits the visual snapshot methodology that characterizes the work.

3 / 5

Completeness

The 'what' is clear (add/update web renderer tests), but there is no explicit 'Use when...' clause; the 'when' exists only implicitly inside the action phrase ('explicitly requested', 'for implementation changes'). Per the judging guideline, a missing 'Use when...' clause or equivalent explicit trigger guidance caps completeness at 3, which also matches anchor 3's 'when is missing or only weakly implied'.

3 / 5

Trigger Term Quality

'web renderer tests' and 'implementation changes' are phrases a user might plausibly say, but common variations are missing — 'snapshot tests', 'visual tests', 'vitest', 'test suite'. This matches anchor 3 ('some relevant keywords but missing common variations or synonyms'), below anchor 4's good coverage and above anchor 2's purely generic terms.

3 / 5

Distinctiveness Conflict Risk

'web renderer tests' carves out a clear niche tied to a specific package, so conflict risk is low — matching anchor 4 ('mostly distinct; minor overlap risk'). It is not 5 because the standalone words 'tests' and 'implementation changes' could also match a general testing skill, and the description lacks the uniquely distinctive triggers (tool names, file extensions) of anchor 5.

4 / 5

Total

13

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

remotion-dev/remotion

Path

.agents/skills/web-renderer-test/SKILL.md

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.