add-sfx

Add a new sound effect to @remotion/sfx

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/add-sfx/SKILL.md

Quality

Content

87%

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

The body is concise, highly actionable, and well-structured as a single-file workflow, but it lacks explicit validation/verification checkpoints for the batch waveform regeneration and build steps.

Suggestions

Add an explicit verification step after the build (e.g. confirm the build succeeded and the new sound is exported) to create a feedback loop.

Include a checkpoint after waveform regeneration to confirm the new sound's samples were generated correctly before proceeding.

Add a final smoke-check such as playing or inspecting the new sound to catch errors before declaring the task complete.

Dimension	Reasoning	Score
Conciseness	The body is lean and task-focused with no padding or explanation of concepts Claude already knows (WAV, CC0, ffmpeg); every section earns its place, matching anchor 3.	3 / 3
Actionability	Provides exact file paths, runnable commands ('bun generate.ts', 'cd packages/sfx && bun run make') and copy-paste-ready code blocks, matching the fully-executable anchor 3.	3 / 3
Workflow Clarity	Seven steps are clearly numbered and sequenced, but there is no validation/verification checkpoint; since step 5 regenerates waveforms across all sounds (a batch op) and step 7 builds, the guideline caps workflow_clarity at 2.	2 / 3
Progressive Disclosure	No bundle files are needed; the self-contained workflow is organized into clear sections (Prerequisites, Steps, Naming conventions, Version) with appropriate inline structure, so anchor 3 applies.	3 / 3
	Total	11 / 12 Passed

Description

50%

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 clearly states a single concrete action in a specific niche but lacks any 'when to use' trigger guidance and natural trigger-term coverage, leaving every dimension at the middle anchor.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to add or register a new sound effect in @remotion/sfx'.

Broaden trigger terms with natural phrasings a user would say ('sound effects', 'sfx', 'audio clip', 'add a sound').

List the concrete sub-actions briefly (e.g. register the asset, export the variable, generate the doc page) to lift specificity.

Dimension	Reasoning	Score
Specificity	Names a concrete domain ('@remotion/sfx') and one concrete action ('Add a new sound effect'), matching anchor 2; it does not list multiple specific actions so it is not a 3.	2 / 3
Completeness	States what the skill does but has no 'Use when...' trigger clause, which per the guidelines caps completeness at 2 rather than 3.	2 / 3
Trigger Term Quality	Includes the natural term 'sound effect' but '@remotion/sfx' is technical jargon and common variations are missing, so it is only at anchor 2 rather than full coverage.	2 / 3
Distinctiveness Conflict Risk	It targets a specific package niche, yet 'sound effect' could overlap with generic audio skills and no explicit distinct triggers are given, keeping it at anchor 2.	2 / 3
	Total	8 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: remotion-dev/remotion
Path: .agents/skills/add-sfx/SKILL.md
Commit: 1b58387

Reviewed: 2 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.