trackdub-media-cleanup

Diagnose and verify media cleanup in Trackdub projects.

Quality

65%

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 ./.claude/skills/trackdub-media-cleanup/SKILL.md

Quality

Content

77%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 disciplined, well-sequenced procedure with per-step completion checkpoints and unusually honest handling of unavailable capabilities and failure states. Its weaknesses are external: linked supporting files (report template, attribution, license) are missing from the bundle, and the description frontmatter undersells the skill's scope.

Suggestions

Ship or remove the dangling links — templates/cleanup-report.md, ATTRIBUTION.md, and LICENSE are referenced in the body but absent from the skill directory.

Add the concrete verification commands for step 6 (e.g. an ebur128 before/after invocation) so the re-measurement instruction is executable rather than directional.

Move secondary material such as the Pitfalls list or the skill-maintenance verification section into a reference file to slim the main body and strengthen progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is dense with genuinely non-obvious, project-specific facts (CLI invocation form, routing policy, fallback semantics, artifact path contract) and never explains concepts Claude already knows — e.g. 'Provider registered != model downloaded != stage ran != stage succeeded' packs four distinctions into one line. Minor trimming is possible in section 4's long run of negative prescriptions, so 4 rather than 5.	4 / 5
Actionability	Concrete, copy-paste-ready commands are provided for the CLI ('dotnet run --project src/Trackdub.Cli --framework net10.0 -- doctor --json') and for independent measurement (ffprobe/ebur128), plus a specific source-file pointer for artifact paths. Gaps keep it at 4: no commands for the before/after re-measurement in step 6, and the report template is linked but its contents are unavailable.	4 / 5
Workflow Clarity	A six-step numbered procedure where every step ends in a bolded 'Completion:' checkpoint — effectively a per-step checklist — with explicit verification in step 6 (re-read project info, recompute source hash, re-measure loudness/peaks) and feedback handling (record skip/fallback states, isolate comparisons before rerun). This matches the anchor for clear sequence with explicit validation steps and error-recovery guidance.	5 / 5
Progressive Disclosure	Section structure is good, but the bundle contains no separate files at all: the three linked paths (ATTRIBUTION.md, LICENSE, templates/cleanup-report.md) do not exist in the skill directory, and material such as the Pitfalls and verification guidance is fully inlined. Some structure with inline content and problematic references fits anchor 3; the dangling links rule out 4.	3 / 5
	Total	16 / 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 short and names a distinct niche, but it reads as a minimal two-verb capability statement rather than a trigger-rich description. It lacks any 'when to use' guidance and the natural vocabulary (noise, echo, speech, audio) that would let a user's request match it.

Suggestions

Add a 'Use when...' clause naming trigger situations, e.g. 'Use when source speech is noisy, echoey, clipped, or uneven, or when cleanup is needed before transcription, diarization, or dubbing.'

Enumerate the concrete operations covered — e.g. measuring loudness/clipping/balance, diagnosing quality artifacts, running speech enhancement stages, verifying output artifacts — instead of the generic 'media cleanup'.

Include natural user vocabulary and synonyms: 'noisy audio', 'clean up speech', 'denoise', 'enhance audio', and relevant formats like .mp4 or .trackdub projects.

Dimension	Reasoning	Score
Specificity	The description names its domain ('media cleanup in Trackdub projects') and two actions ('Diagnose and verify'), but stops short of listing what cleanup covers — speech quality, loudness, denoising, artifact verification. This matches the 'names domain and 1-2 concrete actions, but not comprehensive' anchor, not 4, since it does not list several specific actions.	3 / 5
Completeness	The 'what' is clear (diagnose and verify media cleanup), but there is no 'Use when...' clause or equivalent trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. Not 2 because the 'what' is specific rather than vague.	3 / 5
Trigger Term Quality	'Media cleanup', 'diagnose', 'verify', and 'Trackdub' are relevant keywords, but natural phrases a user would actually say — 'noisy audio', 'echo', 'clean up the speech', 'denoise', 'enhance audio', or file extensions like .mp4/.trackdub — are all missing. Some relevant keywords, missing common variations and synonyms.	3 / 5
Distinctiveness Conflict Risk	'Trackdub projects' establishes a clear niche unlikely to collide with other skills, but the generic 'media cleanup' phrasing alone could overlap with broader audio/video cleanup skills — mostly distinct with minor overlap risk, so 4 rather than 5.	4 / 5
	Total	13 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 3 missing	Warning

	Total	13 / 16 Passed

Repository: trackdubllc/Trackdub
Path: .claude/skills/trackdub-media-cleanup/SKILL.md
Commit: 6ed9e28

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