CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

make-custom-video

Create a custom video with sourced product accuracy, explicit sound routing and exact-final audiovisual review.

Quality

72%

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 ./skills/entry/make-custom-video/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 exceptionally lean operational contract: every sentence instructs, dense phase headers sequence the work end to end, and validation gates plus repair loops are explicit at every approval, paid batch and completion. Actionability is high — named server actions with exact fields and thresholds — though nothing is copy-paste executable since exact schemas are deliberately deferred to live inspection. The one structural defect is a dangling, unclearly-signaled reference to references/recipe-format.md, which does not exist in the delivered bundle.

Suggestions

Ship the cited references/recipe-format.md file in the bundle, or remove the citation and state the recipe format inline — as delivered, the skill's only self-referenced path is unresolvable.

Turn the recipe-format citation into a clearly signaled link with a one-phrase description of its contents (e.g. '**Rebuild recipe**: See [recipe-format.md](references/recipe-format.md) for the exact recipe schema to store') instead of a bare parenthetical.

DimensionReasoningScore

Conciseness

Every sentence is an instruction ("Custom skips styles. Ask which product or service to advertise; wait even with one saved."; "Never infer consent or approve yourself. Honor Stop.") — there is no explanation of concepts Claude already knows and no padding to trim, matching 'lean and efficient; assumes Claude's competence; every token earns its place'. Not 4 because no instance of over-explanation exists; the two-line owner-facing preamble is minimal and functional.

5 / 5

Actionability

Guidance names concrete operations with exact fields and thresholds ("call video_approve with the custom phase, review_token and total_credits from custom_review.approval_quote ... expected_revision and their words as user_quote"; "run video_read with include [\"blockers\"] (free)"; "up to 20 per call"), which is concrete command-level guidance with minor gaps — matching anchor 4. Not 5 because nothing is copy-paste executable: exact call syntax is deferred to live schema inspection ('inspect live schemas before writes'), a flexibility that is explicitly justified but still leaves the literal command forms unstated; not 3 because this is far more specific than pseudocode.

4 / 5

Workflow Clarity

The body sequences the work in ordered phase sections (Load and resume → Reference, product and creative contract → Save and review twice → Produce, assemble and deliver) with pervasive explicit validation gates ("Before each approval, paid batch or completion, run video_read with include [\"blockers\"] ... and fix every blocking and must-fix finding in one pass"; "only checked bytes enter the final"), feedback loops ("Reject double mouths, extra hands, smears and garbled labels ... Re-make affected sources within approval"), and a checklist (the 8-item Non-negotiables). This matches anchor 5; not 4 because checkpoints gate every approval, paid batch and completion rather than only 'most' being present.

5 / 5

Progressive Disclosure

The bundle ships no references/, scripts/ or assets/ directories, yet the body cites "references/recipe-format.md" ("Store the rebuild recipe (references/recipe-format.md)") as a bare parenthetical — a reference that is neither clearly signaled nor resolvable in the delivered bundle, and the only other file pointer ("harness references/talking-actor.md") belongs to a different skill. This matches 'references present but not clearly signaled'; not 4 because the unresolvable self-reference is more than a minor organization gap, not 2 because the ~46-line body is well-sectioned and its content appropriately lives inline.

3 / 5

Total

17

/

20

Passed

Description

50%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 states one concrete capability with distinctive process qualifiers, but the qualifiers read as internal process guarantees rather than user-facing actions or triggers. It entirely lacks a 'Use when...' clause and natural trigger phrasing, which caps both completeness and trigger-term quality at mid-scale. Distinctiveness is moderate because the broad lead phrase 'Create a custom video' overlaps the trigger surface of sibling video-creation skills.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the owner asks for a custom video ad for a specific product or service, with or without a reference video.'

Include natural terms users would actually say — 'video ad', 'product video', 'commercial', 'make a video for my product' — instead of internal process vocabulary like 'exact-final audiovisual review'.

Recast the process qualifiers as concrete capabilities (e.g. 'writes the ad script, sources real product photos and dimensions, keeps the reference's format and sound, and verifies the final cut by listening or measurement') to raise specificity.

DimensionReasoningScore

Specificity

"Create a custom video" is one concrete action, and the qualifiers "sourced product accuracy", "explicit sound routing" and "exact-final audiovisual review" name constraints rather than additional actions, matching the anchor 'names domain and 1-2 concrete actions, but not comprehensive'. It is above 2 because the domain and action are concrete, but below 4 because the full capability set (scripting, sourcing, assembly, delivery) is only implied, never listed as actions.

3 / 5

Completeness

The 'what' is stated clearly ("Create a custom video with sourced product accuracy, explicit sound routing and exact-final audiovisual review") but there is no 'Use when...' clause or any equivalent trigger guidance, which per the judging guidelines caps completeness at 3. Not 2 because the 'what' is concrete rather than vague; not 4 because 'when' is entirely absent, not merely implicit-but-stated.

3 / 5

Trigger Term Quality

"custom video" is a natural phrase a user might say, but the remaining vocabulary ("sourced product accuracy", "sound routing", "exact-final audiovisual review") is internal process jargon, and common variations like "video ad", "product video", "commercial" or "make a video" are absent. This fits 'some relevant keywords but missing common variations or synonyms' — above 2 because a genuinely natural trigger term exists, below 4 because synonym coverage is missing.

3 / 5

Distinctiveness Conflict Risk

The qualifiers carve a niche (product accuracy, sound routing, measured final review), but the lead phrase "Create a custom video" is a broad trigger that would plausibly fire alongside sibling video-creation skills in the same environment (the frontmatter itself lists create-video-fal and create-video-seedance-2-fal among required skills). This matches 'somewhat specific but could still overlap with similar skills' — more than minor overlap risk, so below 4, but clearly not generic enough for 2.

3 / 5

Total

12

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

14

/

16

Passed

Repository

gooseworks-ai/goose-skills

Path

skills/entry/make-custom-video/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.