add-sfx

Add a new sound effect to @remotion/sfx

Quality

69%

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

90%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 body is a tight, highly actionable runbook with concrete code, commands, and a clear numbered sequence; its only real weakness is the absence of explicit validation checkpoints in the workflow.

Suggestions

Add a validation checkpoint after step 5 (e.g. 'confirm packages/docs/components/sfx-demos/sfx-waveforms.ts now contains an entry for the new sound') to lift workflow clarity toward 5.

Consider extracting the step-3 doc-page bullet list into a referenced template file (e.g. references/doc-page.template.mdx) to improve progressive disclosure now that the skill exceeds ~90 lines.

Replace the bare 'Deploy' sub-step in section 1 with the concrete deploy command so the runbook is fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is lean throughout — terse prerequisites, a formatting checklist ('WAV format / CC0 / Normalized to -3dB'), a naming table, and copy-paste commands — with every line earning its place and no padding of concepts Claude already knows, matching the score-5 anchor.	5 / 5
Actionability	Concrete code (the `export const mySound` snippet, the `generate.ts` entry), specific commands (`bun generate.ts`, `bun packages/docs/generate-sfx-waveforms.ts`, `cd packages/sfx && bun run make`), exact file paths, and a naming table make the guidance copy-paste ready across the common cases, matching the score-5 anchor.	5 / 5
Workflow Clarity	Seven numbered steps are clearly sequenced with prerequisites and a final build, but there are no explicit validation/feedback checkpoints (e.g. 'verify the export resolves' or 'confirm the waveform file updated'), so it sits at score 4 ('clear sequence, minor validation gaps') rather than 5.	4 / 5
Progressive Disclosure	No bundle files exist, so scoring is against the single-file structure: sections (Prerequisites, Steps, Naming, Version) are well organized with one-level repo-path references and no nested skill references, but the long inline doc-page checklist in step 3 is content that could live in a template file, keeping it at 4 rather than 5.	4 / 5
	Total	18 / 20 Passed

Description

48%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 clearly scoped to a distinct niche, but it states only the 'what' with a single minimal action and omits any 'when to use' trigger guidance.

Suggestions

Add a 'Use when adding or requesting a new sound effect for @remotion/sfx' trigger clause to satisfy the 'when' half of completeness.

Expand the action beyond a single verb, e.g. 'Add and wire up a new sound effect: register the WAV, export the URL, generate the doc page and waveforms'.

Include a couple of natural synonyms ('sound effect', 'sfx', 'audio clip') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Quotes 'Add a new sound effect to @remotion/sfx' name the domain and a single concrete action ('Add'), which is minimal rather than comprehensive — matching the score-2 anchor 'Processes PDF files' rather than the 1-2 actions required for a 3.	2 / 5
Completeness	A clear 'what' ('Add a new sound effect to @remotion/sfx') is present but there is no 'Use when...' trigger clause, so per the guideline a missing trigger caps completeness at 3.	3 / 5
Trigger Term Quality	Natural terms 'sound effect' and 'sfx' (plus '@remotion/sfx') are present and would be said by users, but coverage is limited to one concept with no synonyms or extensions, matching the score-3 anchor 'Works with PDF files'.	3 / 5
Distinctiveness Conflict Risk	The '@remotion/sfx' niche is highly distinct with minimal conflict risk, but the absence of an explicit trigger phrase keeps it just below the score-5 anchor that pairs a clear niche with concrete trigger guidance.	4 / 5
	Total	12 / 20 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: eca4063

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.