CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ipollowork-video-studio

Route the active iPolloWork video request to its current storyboard, compose, voiceover or soundtrack work, using the engine's native workflow and existing media tools.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 content is an exemplary lean router: a precise dispatch table, explicit scope boundaries, and verified one-level-deep references into a well-organized eight-file reference bundle. The only weaknesses are minor — a few instructions assume context (the task contract's location) and validation specifics live in referenced files rather than the body.

DimensionReasoningScore

Conciseness

The ~19-line body contains no concept explanations, no padding, and no content Claude already knows; every sentence routes, bounds, or sequences work (e.g. "their metadata is a menu, not a preload checklist", "Do not expand a targeted task into a complete-film workflow"). This matches the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

Concrete guidance dominates: the work-to-Skill mapping table, "Generation/editing defaults to `acceptance=studio-preview`", "Prepare scene anchors before synthesis", "silent/media/music work skips TTS", and "Return the actual source and completed output paths". Minor gaps keep it below 5 — e.g. "Read the active task contract" never says where that contract lives, and acceptance criteria are delegated to a reference file.

4 / 5

Workflow Clarity

A clear sequence is present (identify scope → load the one matching Skill → storyboard-to-production progression → checks → return paths) with named checkpoints ("use component/preview checks and Studio playback", "applicable acceptance"). It is not 5 because validation details are implicit in referenced files rather than explicit in-body, and not 3 because checkpoints are named, not absent.

4 / 5

Progressive Disclosure

The body is a clear overview with well-signaled, one-level-deep references ([shared session boundaries](references/video.md), [its input contract](references/video.md#uploaded-video-input), [acceptance](references/video-acceptance.md)); all referenced files exist in the references/ bundle, the #uploaded-video-input anchor matches a real heading, and detail is appropriately split out rather than inlined. This matches the top anchor exactly.

5 / 5

Total

18

/

20

Passed

Description

70%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 specific about the routing function and the four specialist areas, and the iPolloWork branding makes conflict risk minimal. Its main weakness is the complete absence of explicit 'when to use' trigger guidance, which caps completeness at 3 and leaves several natural trigger synonyms unused.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user submits an iPolloWork video request or asks for storyboard, composition, voiceover/narration, soundtrack or uploaded-video enhancement work.'

Include natural synonyms users would say — 'narration', 'music', 'captions', 'video edit/enhance' — alongside the current storyboard/compose/voiceover/soundtrack terms.

State the routing outcome more concretely, e.g. that it selects and loads exactly one matching specialist Skill rather than preloading all of them.

DimensionReasoningScore

Specificity

"Route the active iPolloWork video request to its current storyboard, compose, voiceover or soundtrack work" names the domain plus four concrete work areas, matching the 'several specific actions; minor gaps' anchor. It falls short of 5 because routing is the only verb and the description does not state what each work area actually does.

4 / 5

Completeness

The 'what' is clear (route a video request to storyboard, compose, voiceover or soundtrack work), but there is no 'Use when...' clause or equivalent explicit trigger guidance; 'the active iPolloWork video request' only weakly implies the 'when', so per the judging guideline completeness is capped at 3. It is not a 4 because the trigger condition is never made explicit.

3 / 5

Trigger Term Quality

Natural user-facing keywords are present ("video", "storyboard", "compose", "voiceover", "soundtrack"), matching 'good keyword coverage; a few natural terms missing'. It is not a 5 because common synonyms such as 'narration', 'music', 'captions', or 'video edit/enhance' are absent.

4 / 5

Distinctiveness Conflict Risk

"iPolloWork video" is a clearly branded, narrow niche with distinct triggers, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor. Unlike score 4, there is no meaningful overlap risk with generic video or media skills.

5 / 5

Total

16

/

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

Devin-AXIS/iPolloWork

Path

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