CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ipollowork-video-compose

Create or edit the active iPolloWork video's visual assets, installed recipes, editable composition and seek-safe motion; use for assembly or local picture/text/theme changes.

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

Quality

Content

61%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 an extremely token-efficient orchestrator that correctly pushes detail into conditionally-loaded reference files, with good one-level-deep disclosure. Its weakness is actionability: nearly all guidance is abstract directive language with no concrete steps, entry points, or explicit validation checkpoints inside SKILL.md itself, and some phrases ("current entry", "native main Agent") are cryptic without the references.

Suggestions

Add a short numbered core sequence (load context → build/audition → save & check → hand off to main Agent) so the workflow's order and checkpoints are explicit in SKILL.md.

Include one or two concrete anchors — the command or tool invocation for 'Save and check the real source', and what 'the current entry' refers to — so guidance is executable without the references.

Add brief section headers (e.g. 'When to load what', 'Core loop', 'Handoff rules') to make the dense paragraphs scannable and strengthen navigation.

DimensionReasoningScore

Conciseness

The body is ~130 words with zero padding: no concepts Claude already knows are explained, and every clause carries an instruction or a file pointer ("Read shared boundaries when unknown... Load only relevant Compose sections; small edits read affected rules"). This matches anchor 5 — lean, assumes competence, every token earns its place — rather than anchor 4, which reserves room for trimmable over-explanation that is absent here.

5 / 5

Actionability

Guidance is high-level directives with no concrete steps, commands, or entry points inside the body: "Build visible cause, change and consequence", "complete a continuous motion audition", "hand off only new required speech/sound and reconcile measured timing". It instructs at an abstract level and delegates all specifics to referenced files, matching anchor 2 (minimal concrete guidance; specific steps missing) rather than anchor 3, which would require at least partially concrete, executable detail.

2 / 5

Workflow Clarity

A rough sequence is discernible (read boundaries/storyboard → read motion principles for initial generation → build → audition → preserve timeline → save and check → main Agent integrates), and two implicit checkpoints exist ("complete a continuous motion audition before expanding the film", "Save and check the real source"). But steps are not enumerated and validation is implicit rather than explicit checkpoints with failure handling, matching anchor 3; anchor 4's 'most checkpoints present' is not met.

3 / 5

Progressive Disclosure

The body is a short overview with well-signaled, one-level-deep references to three files (video.md, video-motion-principles.md, video-compose.md#motion-audition), each with a clear loading condition ("when unknown", "must read... before authoring", "load only relevant sections"). It stops short of anchor 5 because the references live in a sibling skill's bundle (unverifiable here), the body lacks section headers, and no local bundle structure exists to navigate.

4 / 5

Total

14

/

20

Passed

Description

67%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 compact, third-person, and answers both what the skill does and when to use it, with a clearly scoped domain. Its main weakness is jargon-laden trigger language ("seek-safe motion", "installed recipes", "assembly") that users are unlikely to say naturally, weakening trigger matching and keeping completeness and distinctiveness just below the top anchors.

Suggestions

Rewrite the 'use for' clause with natural user phrasing and synonyms, e.g. "Use when assembling, editing, or restyling the current video — changing pictures, text, themes, or motion/timing."

Replace or gloss internal jargon ("seek-safe motion", "installed recipes") with plain-language equivalents so users' everyday words match the description.

State the boundary versus sibling iPolloWork skills in one clause to reduce conflict risk on broad requests like 'make this video'.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Create or edit the active iPolloWork video's visual assets", "editable composition and seek-safe motion", "use for assembly or local picture/text/theme changes" — within a clearly named domain. It falls short of anchor 5 because coverage is incomplete and some actions are stated in dense jargon rather than fully enumerated capabilities.

4 / 5

Completeness

Both parts are present: a clear "what" ("Create or edit the active iPolloWork video's visual assets, installed recipes, editable composition and seek-safe motion") and an explicit "when" ("use for assembly or local picture/text/theme changes"). It is not anchor 5 because the trigger phrases are jargon-heavy and somewhat ambiguous (e.g., "assembly" of what?), making the 'when' less concrete than the anchor-5 pattern of natural user phrasing.

4 / 5

Trigger Term Quality

Some natural terms appear ("video", "picture/text/theme changes", "create or edit"), but key phrases like "seek-safe motion", "installed recipes", "editable composition", and "assembly" are internal jargon a user would rarely say verbatim, and common synonyms are missing. This matches anchor 3 (relevant keywords but missing common variations) better than anchor 4's fuller natural-term coverage.

3 / 5

Distinctiveness Conflict Risk

The "active iPolloWork video" scope carves out a clear niche with mostly distinct triggers, but the skill is one of an iPolloWork video family (the body references a sibling studio skill), so "assembly" and general edit requests could plausibly overlap with closely related sibling skills — minor overlap risk per anchor 4 rather than anchor 5's minimal conflict.

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: 4 suspicious

Warning

Total

15

/

16

Passed

Repository

Devin-AXIS/iPolloWork

Path

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