CtrlK
BlogDocsLog inGet started
Tessl Logo

web-renderer-test

Add a test case to the web renderer

60

Quality

70%

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.

The content is a tight, executable guide: it gives runnable commands, complete fixture/test examples, and a clear numbered workflow with verification, well-organized for a simple skill.

DimensionReasoningScore

Conciseness

The body is efficient, assumes Claude knows React/vitest, and points to exact paths with a runnable command; minor wordiness in connective phrases like 'A fixture looks like this for example' keeps it just below a 5.

4 / 5

Actionability

Provides a copy-paste runnable command, a complete fixture, and a complete matching test with specific paths and parameters; the example fully covers the common case of adding a new test.

5 / 5

Workflow Clarity

The 5-step 'Adding a new test' sequence is clear with exact paths and a verification command (run vitest), and flags important steps, but lacks an explicit failure/feedback loop, so it does not reach a 5.

4 / 5

Progressive Disclosure

A short, single-purpose skill (under 50 lines of prose) with no need for external references, organized into clear sections (Example, Adding a new test), matching the simple-skill exception for a 5.

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 concise and states a clear action with a specific domain, but it omits any 'when to use' trigger guidance and relies on a single verb, limiting completeness and trigger coverage.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g. 'Use when adding visual snapshot tests to the web renderer or when a new CSS/animation property needs coverage.'

Expand the action verb set to list multiple specific actions (e.g. 'Add fixtures, write vitest snapshot tests, and register preview entries') to improve specificity and trigger-term quality.

Include natural synonyms users might say (e.g. 'snapshot test', 'visual regression', 'vitest') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('web renderer') and one concrete action ('Add a test case'), matching the anchor for naming a domain with 1-2 concrete actions; it does not list multiple actions to reach a 4.

3 / 5

Completeness

It clearly states what to do ('Add a test case to the web renderer') but provides no 'when' or 'Use when' trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords ('test case', 'web renderer') are present but lack common synonyms or natural variations a user might say; missing 'Use when' phrasing keeps it below a 4.

3 / 5

Distinctiveness Conflict Risk

The 'web renderer' scope makes it mostly distinct from generic testing skills with only minor overlap risk; it does not fully reach a 5 because 'test case' alone is somewhat broad.

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.

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.