CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ipollowork-video-storyboard

Write or revise the active iPolloWork video's native STORYBOARD.md, with source coverage, content-led sequence and provisional timing; use for script-only work.

Quality

79%

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

Quality

Content

82%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 exemplar of token efficiency: a complete conditional workflow, preservation rules, scope guards and a handoff contract in two dense paragraphs with no filler. Its gaps are structural rather than stylistic — the storyboard format and the brief/source artifacts live entirely in external, cross-skill references, and there is no explicit validation step before the save is declared done.

DimensionReasoningScore

Conciseness

In roughly 130 words the body packs a complete conditional reading order, a preservation list, a save requirement, a stop condition and a handoff contract, with zero padding and no explanation of concepts Claude already knows ("implementation and synthesis guides belong to later work" actively excludes off-scope material). This matches the "lean and efficient; every token earns its place" anchor.

5 / 5

Actionability

Concrete, executable instructions dominate: "Read [shared session boundaries] ... once when unknown", "Save the native editable STORYBOARD.md before production", "Preserve required facts, user edits, pinned choices and explicit caps", "return its exact path, affected frame IDs and unresolved inputs", plus explicit prohibitions. It falls short of anchor 5 because the storyboard's actual format is delegated to an external guide and the locations of the "affected brief/source/current storyboard" are unstated.

4 / 5

Workflow Clarity

The sequence is clear and conditional (read boundaries only when unknown → read the storyboard guide and affected docs → check recipe metadata only when needed → save → stop for script-only or hand off to the next phase), with an explicit decision point. It sits at anchor 4 rather than 5 because there is no explicit validation checkpoint (e.g. verifying source coverage or preserved facts before declaring the file saved), though the operation is neither destructive nor batch so no cap applies.

4 / 5

Progressive Disclosure

References are clearly signaled, one level deep, and loaded lazily ("once when unknown", "only when needed for feasibility"), and the workflow details are appropriately split out rather than inlined. It misses anchor 5 because both reference links point outside this skill's own bundle into a sibling skill (../ipollowork-video-studio/references/...), and the body has no section headers to aid navigation.

4 / 5

Total

17

/

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 concrete and tightly scoped to a named artifact in a specific product context, with a present but narrow use-when clause. Its main weaknesses are thin trigger-term coverage (no synonyms or natural user phrasings beyond "script-only work") and a "when" that only covers one invocation case.

Suggestions

Add natural trigger phrases and synonyms, e.g. "Use when the user asks to plan, outline, or revise the scene sequence or timing for the active iPolloWork video".

Broaden the 'when' clause beyond script-only work to cover the storyboard-revision and review-request cases the body actually handles.

Spell out one or two user-visible outcomes (e.g. "returns the saved storyboard path and affected frame IDs") so the value is legible to someone outside the studio suite.

DimensionReasoningScore

Specificity

"Write or revise the active iPolloWork video's native STORYBOARD.md, with source coverage, content-led sequence and provisional timing" lists several concrete actions and deliverable attributes (write, revise, source coverage, sequence, provisional timing), placing it above anchor 3's bare 1-2 actions, though it stops short of anchor 5's comprehensive multi-action coverage since everything concerns a single artifact.

4 / 5

Completeness

The "what" is explicit and concrete (writing/revising STORYBOARD.md with specified contents) and a "when" clause exists ("use for script-only work"), so it clears the anchor-3 cap; but the trigger is narrow — covering only the script-only case without other explicit trigger phrases — so it does not reach anchor 5.

4 / 5

Trigger Term Quality

Keywords like "storyboard", "script", "video", "sequence" and "timing" are relevant within the domain, but the description offers no synonyms or natural variations (e.g. "scene plan", "shot list", "outline"), matching the "some relevant keywords but missing common variations or synonyms" anchor rather than anchor 4's good coverage.

3 / 5

Distinctiveness Conflict Risk

"the active iPolloWork video's native STORYBOARD.md" carves a precise product- and artifact-specific niche, and "use for script-only work" distinguishes it from later production phases; however "script-only" wording risks minor overlap with a closely related script-writing sibling skill, matching "mostly distinct; minor overlap risk" rather than anchor 5's minimal conflict risk.

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