CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ipollowork-video-voiceover

Add or revise scene-bound narration or speech-linked captions in the active iPolloWork video using actual voice settings, measured audio and alignment.

Quality

70%

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-voiceover/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

An extremely lean, dense body of operational rules with well-signaled one-level-deep references — excellent token efficiency. Its weaknesses are the mirror image: no explicit step sequence or validation/retry loop for what is a batch synthesis operation, and the executable details (batch contract, media tools, file formats) are never shown inline or bundled, leaving the body more prescriptive than executable.

Suggestions

Number the workflow steps explicitly (read refs → synthesize via batch contract → mount returned audio → apply measured timing shifts → verify → return files), with the verification step defined as a validate/fix/retry loop rather than a single 'check'.

Surface the minimal concrete details of the 'built-in batch contract' and the 'existing media tools' inline (names/commands or a pointer to the exact section), so the body is actionable without relying on a sibling skill's files.

Add section headers (e.g. 'When to use', 'Synthesis workflow', 'Constraints') to break up the two dense paragraphs and make the rules scannable.

DimensionReasoningScore

Conciseness

The body is ~10 lines with zero padding: no concept explanations, no library background, no restating of what Claude already knows. Every sentence carries a rule or pointer ('Synthesize through the built-in batch contract; mount actual returned audio/captions and apply measured timing shifts once'), matching anchor 5's 'lean and efficient; assumes Claude's competence; every token earns its place'. If anything it is terse to the edge of density, but the rubric penalizes verbosity, not compression.

5 / 5

Actionability

The rules are specific in intent — 'Synthesize through the built-in batch contract', 'Captions-only work reuses saved alignment', 'Do not guess provider/voice, fabricate timings or replace the TTS service' — but no executable detail lives in the body: the batch contract itself, the media tools, and the voiceover.json/storyboard formats are never shown or pointed to concretely beyond two section references. This fits anchor 3 ('some concrete guidance but incomplete... missing key details') rather than 4, which requires mostly-executable guidance with only minor gaps.

3 / 5

Workflow Clarity

A rough sequence is recoverable (read references → synthesize via batch contract → mount returned audio/captions → apply measured timing shifts → check mounted source → return files → disclose unfinished speech), but it is embedded in dense prose with no explicit ordering, and the validation checkpoint ('Check the mounted source with the existing media tools') has no fix-and-retry loop spelled out. Per the scoring notes, batch operations without an explicit feedback loop cap workflow clarity at 3; this body sits exactly at that cap — above anchor 2 because a real check and failure path ('preserving prior speech until success', 'disclose unfinished required speech') are present.

3 / 5

Progressive Disclosure

References are one level deep and clearly signaled with roles ('Read [shared session boundaries]... once when unknown', 'affected [Voiceover]... sections'), and the body itself is short enough to be a genuine overview. It falls short of anchor 5 because both links point outside the skill's own bundle (../ipollowork-video-studio/references/...), a cross-skill dependency that is not verifiable within this skill and leaves the body with no section headers organizing its two dense paragraphs — matching anchor 4's 'minor organization gaps'.

4 / 5

Total

15

/

20

Passed

Description

58%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 specific, well-scoped description with a clear 'what', but it entirely lacks a 'when to use' trigger clause and misses the most natural trigger words (voiceover, dubbing, subtitles, TTS). Adding an explicit 'Use when...' sentence with those synonyms would lift the two weakest dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to add or change voiceover, narration, dubbing, or speech captions/subtitles in an iPolloWork video.'

Include natural synonyms users would actually say — 'voiceover' (currently only in the skill name), 'dubbing', 'subtitles', 'text-to-speech' — in the description text.

State the out-of-scope boundary explicitly ('existing audio, music-only changes do not need synthesis') in the description rather than leaving it to the body.

DimensionReasoningScore

Specificity

The description lists concrete actions — 'Add or revise scene-bound narration or speech-linked captions' — anchored to a specific artifact ('the active iPolloWork video') and qualified with 'actual voice settings, measured audio and alignment'. It stops short of anchor 5 because coverage is narrow (no mention of the synthesis/mounting workflow itself) and short of anchor 5's 'comprehensive coverage', while clearly exceeding anchor 3's 1-2 generic actions.

4 / 5

Completeness

The 'what' is clear (add or revise scene-bound narration and speech-linked captions with real settings and measured timing), but there is no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description, which per judging guidelines caps completeness at 3. It cannot score 4 (both what and when present) because 'when' is entirely absent, and exceeds 2 because 'what' is concrete rather than vague.

3 / 5

Trigger Term Quality

Relevant keywords exist ('narration', 'captions', 'voice', 'video') but common natural variations users would actually say are missing: 'voiceover' appears only in the skill name, not the description, and synonyms like 'dubbing', 'subtitles', 'text-to-speech', or 'TTS' are absent. This matches anchor 3 ('some relevant keywords but missing common variations or synonyms'), not anchor 4 which requires only 'a few' natural terms missing — here several core synonyms are absent.

3 / 5

Distinctiveness Conflict Risk

The description is tightly scoped to 'the active iPolloWork video' and 'scene-bound narration or speech-linked captions', giving it a clear niche with minimal conflict against generic skills. It falls below anchor 5 only because it could overlap with the sibling video-studio skill's own audio/music work — the description itself must clarify that 'Existing audio... and music-only work' are out of scope, which it leaves implicit.

4 / 5

Total

14

/

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-voiceover/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.