CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cue

Writing and producing product videos: scripts, storyboards, narration, and reproducible Playwright demo recordings. Use for explainers, onboarding, feature walkthroughs, multi-aspect exports, captions, and video quality checks.

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./cue/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 well structured with concrete thresholds, clear recipe dispatch, and explicit two-stage workflows, but it is noticeably verbose (duplicated collaboration data, inline dated platform stats, vendor marketing detail) and its extensive reference system points at files absent from the bundle. Actionable core guidance is solid, though verification of the delegated detail is impossible.

Suggestions

Collapse the collaboration information into a single section: the HTML comment block (CAPABILITIES_SUMMARY / COLLABORATION_PATTERNS / BIDIRECTIONAL_PARTNERS), the Collaboration section, and the handoff table repeat largely the same routing data.

Move dated platform facts (YouTube Shorts 180s limit as of Oct 2024, Mar 31 2025 replay-view policy, Synthesia feature stats with 2026 source) out of the routing table and Duration Templates into a dedicated, versioned reference file so the SKILL.md body stays evergreen.

Ship the referenced bundle files (reference/*.md and _common/*) alongside SKILL.md, or trim the Reference Map and "Read First" columns to only the files that actually exist, so the progressive-disclosure chain is navigable.

DimensionReasoningScore

Conciseness

The body carries noticeable padding: collaboration data is repeated three times (HTML comment block, Collaboration section, handoff table), the Synthesia/HeyGen routing row embeds vendor marketing detail ("240+ avatars, 160+ languages... [Source: Synthesia (2026)]"), and dated platform stats ("Shorts max is 180s as of Oct 2024", "as of Mar 31, 2025... replay counts as a view") sit inline rather than in a versioned reference. Not 3: the volume of duplicated and time-sensitive inline material exceeds "some unnecessary explanation that could be tightened".

2 / 5

Actionability

Guidance is mostly concrete and executable: specific thresholds ("educational 120-130 wpm", "≤42 chars per line, and ≤17-21 CPS", "DE +30%, ES +25%, JA -10%"), a filled-in Scene Document Format template, and per-subcommand dispatch rules. Not 5: much of the deep execution guidance (code patterns, Playwright config, quality metric procedures) is delegated to reference files that are absent from the bundle, so it cannot be verified as copy-paste ready.

4 / 5

Workflow Clarity

Both workflows are explicitly sequenced with per-phase required actions and key rules (BRIEF → STRUCTURE → SCENE → NARRATE → REVIEW, then SCRIPT → STAGE → SHOOT → DELIVER), and REVIEW/DELIVER phases plus the ship/reshoot quality verdict provide validation checkpoints. Not 5: the REVIEW phase's validation detail is thin in-body and the readiness checklist lives in a reference file (demo-checklist.md) that is not present, leaving some checkpoints implicit.

4 / 5

Progressive Disclosure

Structure is well signaled — a Reference Map table, per-recipe "Read First" columns, and one-level-deep references — but the bundle contains no reference/, scripts/, or assets/ files, so all ~17 referenced files (reference/patterns.md, reference/demo-playwright-config.md, etc.) and every _common/* contract file are unverifiable or missing. Not 4: good in-body organization cannot compensate for a disclosure chain whose target files do not exist in the bundle.

3 / 5

Total

13

/

20

Passed

Description

92%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 strong: it names concrete capabilities in third person, includes an explicit "Use for..." trigger clause, and occupies a distinct niche. The only weakness is that a few natural trigger phrases (demo video, screen recording, tutorial, voiceover) are absent.

DimensionReasoningScore

Specificity

"Writing and producing product videos: scripts, storyboards, narration, and reproducible Playwright demo recordings" lists multiple specific concrete actions covering the domain comprehensively. Not 4: the capability list is complete for this skill's scope, with no minor coverage gaps.

5 / 5

Completeness

Both halves are explicit: the "what" ("Writing and producing product videos: scripts, storyboards, narration, and reproducible Playwright demo recordings") and a concrete "Use for..." when-clause. Not 4: the when-clause is explicit with concrete trigger phrases rather than merely present-but-vague.

5 / 5

Trigger Term Quality

"Use for explainers, onboarding, feature walkthroughs, multi-aspect exports, captions, and video quality checks" covers good natural trigger terms. Not 5: common user phrasings like "demo video", "screen recording", "tutorial", or "voiceover" are missing from the trigger list.

4 / 5

Distinctiveness Conflict Risk

The combination of product video scripting and Playwright demo recording is a clear niche with distinct triggers, unlike generic document or media skills. Not 4: no meaningful overlap risk with closely related skills is evident from the description alone.

5 / 5

Total

19

/

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

simota/agent-skills

Path

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