CtrlK
BlogDocsLog inGet started
Tessl Logo

add-expert

Add a new expert to the Remotion experts page

66

Quality

78%

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/add-expert/SKILL.md
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.

The body is a tight, fully-actionable three-step workflow with concrete paths, a copy-paste entry template, an executable render command, and an explicit verification checkpoint, all well-organized within a compact single-purpose skill.

DimensionReasoningScore

Conciseness

The body is lean with concrete file paths, a parameterized TSX template, and specific rules; it never explains basic concepts Claude already knows, so every token earns its place. It avoids the unnecessary explanation that would drop it to score 2.

3 / 3

Actionability

Provides exact paths, a complete copy-paste TSX entry template with real field names and types, and an executable command ('bun render-cards'), matching the 'fully executable code/commands; copy-paste ready' anchor.

3 / 3

Workflow Clarity

Three clearly sequenced numbered steps culminating in an explicit validation checkpoint ('Verify it says Rendered experts-<slug> (not Existed)'), with feedback on what a wrong result looks like. This matches the 'clear sequence with explicit validation steps' anchor.

3 / 3

Progressive Disclosure

The skill is under 50 lines, single-purpose, and well-organized into numbered steps with sub-bullets; per the rubric's simple-skill guidance, no external file references are needed and the clear sections warrant a 3.

3 / 3

Total

12

/

12

Passed

Description

57%

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 specific to a clear niche and uses third-person voice, but it only names one action and omits any 'Use when' trigger guidance, capping completeness and trigger coverage at the mid level.

Suggestions

Add a 'Use when ...' clause to provide explicit trigger guidance, e.g. 'Use when adding or updating a freelancer entry on the Remotion experts page.'

Broaden the action list to reflect the full capability set (e.g. add, update, remove an expert) so the description is more comprehensive.

Include a few more natural keyword variations users might say (e.g. 'freelancer', 'add to the experts/experts page') to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Remotion experts page') and one concrete action ('Add a new expert'), but describes only a single action rather than a comprehensive list of capabilities. It is not vague (avoids score 1) yet falls short of the multiple concrete actions required for score 3.

2 / 3

Completeness

Clearly states what the skill does ('Add a new expert to the Remotion experts page') but provides no 'Use when...' clause or equivalent trigger guidance; per the guidelines a missing trigger caps completeness at 2.

2 / 3

Trigger Term Quality

Contains natural terms a user might say ('add a new expert', 'experts page') but lacks common variations or broader keywords, matching the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

Tied to a specific 'Remotion experts page' niche, making it unlikely to trigger for unrelated skills; matches the 'clear niche with distinct triggers' anchor.

3 / 3

Total

9

/

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.