CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ipollowork-video-soundtrack

Add or revise music, sound effects and their mix in the active iPolloWork video, using authorized sources, real editable tracks and measured event cues.

Quality

71%

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/ipollowork-video-soundtrack/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 exceptionally lean and dense with project-specific constraints, but it trades away executability and sequencing: it is a prose constraint list whose actual operational detail lives in external, cross-bundle references not shipped with this skill. Converting the implicit flow into a numbered workflow and either shipping the key operational details or the referenced files within the bundle would address the main weaknesses.

Suggestions

Replace the prose with an explicit numbered workflow (read references → acquire tracks → save provenance/receipts → mount as separate editable timeline clips → return files), so the sequence and checkpoints are unambiguous.

Ship the critical operational details (or copies of the referenced guidance) inside this skill's own references/ directory instead of relying solely on ../ipollowork-video-studio/references/, so the skill is self-contained and the links resolve.

Add an explicit validation checkpoint (e.g. verify mounted clips are editable and mix claims are backed by observed playback evidence before reporting completion) to turn the implicit evidence rules into a feedback loop.

DimensionReasoningScore

Conciseness

The body is two short paragraphs with zero padding: no concept explanations Claude already knows, no filler, and every token is a project-specific constraint ("Preserve existing narration and visual timing; a soundtrack task does not load TTS or regenerate speech"). This matches anchor 5 ("Lean and efficient; assumes Claude's competence; every token earns its place") and clearly not anchor 4, which requires over-explanation to trim.

5 / 5

Actionability

There are concrete behavioral rules — "mount the same real music/SFX files as separate editable timeline clips", "Save provenance/receipts", "Return the actual saved source and sound files to the native main Agent" — but no executable specifics: no commands, tool invocations, or file paths inside this bundle, and the actual operational detail is deferred to external references that are not part of this skill. This sits between anchor 2 (high-level hints) and anchor 4 (mostly executable guidance), matching anchor 3 ("Some concrete guidance but incomplete... missing key details").

3 / 5

Workflow Clarity

A rough sequence is discernible from the prose (read shared references → reuse or source/generate tracks → save provenance → mount as editable clips → return files to the main Agent), and outcome-verification rules exist ("keep mix/audible-sync claims tied to observed evidence", "unavailable required sound remains disclosed unfinished scope"). However, the steps are never explicitly listed, checkpoints are implicit rather than explicit, and execution details for each step are missing — anchor 3 ("sequence present but checkpoints missing or implicit") fits; validation is not wholly absent, ruling out anchor 2, while the lack of explicit listed steps and feedback loops rules out anchor 4.

3 / 5

Progressive Disclosure

The body points to two clearly signaled, one-level-deep references ([shared session boundaries](../ipollowork-video-studio/references/video.md) and [Soundtrack](../ipollowork-video-studio/references/video-soundtrack.md)), and nothing that belongs in a separate file is inlined. But the referenced paths live outside this skill's bundle in a sibling skill that does not exist alongside it, and the bundle itself contains no references/, scripts/, or assets/ files — navigation cannot be completed from this skill alone, and the body has no section organization. This matches anchor 3 ("references present but" structure could be better organized / not resolvable within the bundle) rather than anchor 4, which assumes appropriately placed, working references.

3 / 5

Total

14

/

20

Passed

Description

66%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 compact, third-person description with concrete capabilities and a clear niche, but it omits any explicit 'when to use' trigger guidance, which caps completeness and weakens its value for skill routing. It also misses several natural synonyms (audio, soundtrack, background music) users might say. Adding a "Use when..." clause with those synonyms would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to add or change music, sound effects, audio, soundtrack, or the mix in an iPolloWork video."

Include common synonyms such as "audio", "soundtrack", and "background music" alongside "music" and "sound effects" to improve trigger term coverage.

Optionally name one or two more concrete operations (e.g. adjusting track volume or timing cues) to close the coverage gap between "several specific actions" and comprehensive.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Add or revise music, sound effects and their mix" — anchored to a named domain ("the active iPolloWork video") and qualified with concrete constraints ("authorized sources, real editable tracks and measured event cues"). It falls short of the comprehensive anchor (5) because coverage has gaps: no mention of removing/muting tracks, volume or fade adjustments, or syncing specifics, so "several specific actions; minor gaps" (4) is the closest fit.

4 / 5

Completeness

The "what" is clear and concrete (add or revise music, sound effects, and mix in the iPolloWork video), but there is no "Use when..." clause or equivalent explicit trigger guidance anywhere in the description. Per the judging guidelines, a missing 'Use when' clause caps completeness at 3; the description matches anchor 3 ("Has a clear 'what' but 'when' is missing or only weakly implied") and clearly not anchor 4, which requires both what and when.

3 / 5

Trigger Term Quality

Natural user-facing terms are present — "music", "sound effects", "mix" — which a user would plausibly say when needing this skill. It is not comprehensive (5) because common synonyms and variations are missing: "audio", "soundtrack", "background music", and "volume" are absent, matching "good keyword coverage; a few natural terms missing" (4).

4 / 5

Distinctiveness Conflict Risk

"in the active iPolloWork video" carves out a clear niche that distinguishes this skill from generic media skills, and the music/SFX/mix scope separates it from sibling concerns like narration or visuals. It does not reach anchor 5 because the trigger terms themselves ("music", "sound effects", "mix") are generic and would overlap with closely related audio-editing skills outside the iPolloWork family — "mostly distinct; minor overlap risk" (4) fits best.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository

Devin-AXIS/iPolloWork

Path

.agents/skills/ipollowork-video-soundtrack/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.