CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

changelog-video

Turn a weekly changelog .md into a finished branded changelog video (square 1080, ~45-60s, Annie VO, animated brand background, mock-UI visualizations, lowkey captions). Use when the user provides a changelog/digest markdown and wants the weekly video, or says "changelog video". Self-contained — fonts, background, lexicon, and scripts ship in this skill.

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

73%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.

A highly actionable, well-gated pipeline skill with excellent workflow sequencing and validation loops, undermined by a broken bundle reference (the missing examples/master-skeleton.html scaffold the whole build depends on) and notable repetition of the same warnings across sections. Tightening the duplicated emphasis and shipping or correcting the scaffold path would raise both conciseness and actionability.

Suggestions

Ship examples/master-skeleton.html in the bundle or fix the two references to it (step 0 and the anti-patterns table) to point at the actual scaffold path — the entire step 5 placeholder workflow depends on this file.

Dedupe the repeated warnings: state the captions-are-mandatory and use-this-scaffold rules once each (e.g., in step 5 and step 0 respectively) and let the anti-patterns table carry only a one-line pointer instead of restating full rationale.

Trim step 0's meta-commentary ("that's the single most common way this skill goes off-brand", the STOP paragraph) to a compact rule + one-line rationale; the current multi-sentence emphasis costs tokens without adding new instruction.

DimensionReasoningScore

Conciseness

The body is dense and imperative with no explanations of concepts Claude already knows, but key warnings are repeated three to four times: the scaffold/off-brand warning appears in the "Load first" preamble, step 0's bolded paragraph, and the anti-patterns table; the captions-are-non-optional point is stated in step 4, step 5, step 6 gate 5, and again in the anti-patterns table. This goes beyond the score-4 anchor's "minor instances of over-explanation"; it is not a 2 because there is no padding or tutorial-style filler — the content is otherwise lean, high-signal instruction.

3 / 5

Actionability

Guidance is almost entirely copy-paste-ready: concrete ffmpeg/heygen/whisper CLI invocations with flags, a pinned voice ID, exact gate commands, and a concrete LINES-array paste pattern. It misses 5 because step 0's critical command `cp <SKILL_DIR>/examples/master-skeleton.html project/index.html` references a file that does not exist in the bundle (no examples/ directory ships), so the foundational copy step fails as written; still well above 3 since every other command is executable and complete.

4 / 5

Workflow Clarity

The 0-6 pipeline is clearly sequenced with explicit validation checkpoints and feedback loops: the word-timings hard gate before step 5, "resolve every one" for MISMATCH warnings, the whisper forced-alignment fallback, seam-gate verify, frame spot-checks, and the hard-fail caption presence gate with a recovery path ("re-check step 5's LINES population"). This matches the score-5 anchor including error-recovery loops.

5 / 5

Progressive Disclosure

Structure is good: the SKILL.md body is a router over well-signaled, one-level-deep references — references/build-spec.md, references/visualization-registry.md, references/script-voice.md, references/lexicon.json, scripts/align-captions.mjs, and assets/ — all of which exist in the bundle. It falls short of 5 because the twice-referenced `examples/master-skeleton.html` does not exist in the bundle, leaving a broken navigation path on the critical path; not a 3 since all other references are real, clearly signaled, and content is appropriately split.

4 / 5

Total

16

/

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.

A strong description: specific, parameterized capabilities paired with an explicit use-when trigger clause and a distinctive quoted trigger phrase. The only gap is modest synonym coverage (e.g., "release notes") in the trigger terms.

DimensionReasoningScore

Specificity

"Turn a weekly changelog .md into a finished branded changelog video (square 1080, ~45-60s, Annie VO, animated brand background, mock-UI visualizations, lowkey captions)" names multiple concrete actions with concrete parameters (format, duration, voice, background, visualizations, captions). Coverage of the pipeline's outputs is comprehensive and nothing is generic.

5 / 5

Completeness

Explicitly answers both: the "what" is the full video production pipeline with deliverable details, and the "when" is a concrete "Use when the user provides a changelog/digest markdown and wants the weekly video, or says 'changelog video'" trigger clause. Matches the score-5 anchor's dual what+when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases a user would say are present — "changelog video", "changelog/digest markdown", "wants the weekly video" — and they map well to the niche. Falls short of 5 because common synonyms like "release notes" or "weekly recap/digest video" are missing; clearly above 3 since the included terms are exactly what a user would utter rather than technical jargon.

4 / 5

Distinctiveness Conflict Risk

"changelog" + "weekly video" + the quoted phrase "changelog video" form a clear niche with distinct triggers; no plausible overlap with generic video, changelog-writing, or brand-skills. The explicit self-contained note ("fonts, background, lexicon, and scripts ship in this skill") further separates it from sibling skills.

5 / 5

Total

19

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

16

Passed

Repository

heygen-com/hyperframes

Path

.agents/skills/changelog-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.