CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-audio-dsp

Review Web Audio API, Tone.js, DSP, and sound synthesis code for audio graph lifecycle leaks, glitch/pop artifacts, clipping prevention, parameter ramps, and browser AudioContext safety.

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 tight, well-structured review-lens skill: domain rules are concrete and API-specific, reporting format is explicit, and the short single-file form is exactly appropriate for progressive disclosure. The only minor gap is the absence of one worked example finding/fix.

DimensionReasoningScore

Conciseness

The ~33-line body is lean and sectioned with no padding: it never explains what Web Audio or DSP is, and every explanatory line (e.g. "Unmanaged audio graph accumulation causes memory leaks and DSP thread degradation") justifies a rule Claude would otherwise have to guess, so every token earns its place.

5 / 5

Actionability

Guidance names exact APIs and thresholds — "rampTo()", "linearRampToValueAtTime()", "setTargetAtTime()", "Tone.Limiter", "master gain ceiling <= 0.85" — making the rules directly checkable, but there is no example finding/fix pair showing how a violation and its correction read, leaving a minor gap short of fully copy-paste-ready guidance.

4 / 5

Workflow Clarity

This is a simple single-purpose skill whose one action is unambiguous: numbered sections sequence scope ("Review only files responsible for audio synthesis...") then the four-rule rubric then a concrete reporting format that even covers the compliant case ("state approval in one clear line"). It is a read-only review, so no destructive/batch validation loop is required.

5 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and uses well-organized headed sections (Scope, Rubric & Rules, Reporting Guidance) with no bundle files to navigate — squarely matching the simple-skill exception for a top score.

5 / 5

Total

19

/

20

Passed

Description

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

A highly specific, distinctive description that clearly states what the skill reviews, but it omits any explicit 'Use when...' trigger clause, which both caps completeness and leaves a few natural trigger synonyms unused.

Suggestions

Append an explicit trigger clause, e.g. "Use when reviewing or changing audio synthesis code, Tone.js patches, Web Audio node graphs, or any diff under src/audio/."

Add natural user-facing synonyms such as "synth", "sound design", "audio engine", or "music generation code" to broaden trigger coverage without adding vagueness.

DimensionReasoningScore

Specificity

The description lists five concrete, distinct review actions — "audio graph lifecycle leaks, glitch/pop artifacts, clipping prevention, parameter ramps, and browser AudioContext safety" — giving comprehensive coverage of the audio-DSP review domain with no meaningful gaps, matching the anchor for multiple specific concrete actions.

5 / 5

Completeness

The "what" is clearly and concretely stated, but there is no "Use when..." clause or equivalent explicit trigger guidance telling Claude when to reach for this skill; the judging guidelines cap completeness at 3 in that case.

3 / 5

Trigger Term Quality

Strong natural keywords are present ("Web Audio API", "Tone.js", "DSP", "sound synthesis", "AudioContext"), but common variations users might say — such as "synth", "sound design", "audio engine", or "web audio code" — are missing, placing it just below the comprehensive-synonym anchor.

4 / 5

Distinctiveness Conflict Risk

The Tone.js / Web Audio API / DSP vocabulary defines a clear niche with distinct triggers, making confusion with generic code-review or document skills unlikely — it squarely matches the minimal-conflict anchor.

5 / 5

Total

17

/

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

colinhallett/tcr-ambient-monitor

Path

skills/review-audio-dsp/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.