CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

general-video

Author or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds. Use motion-graphics instead for a short unnarrated motion-first unit, including an animated title. Route fresh creation through hyperframes before using this skill.

Quality

83%

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 well-engineered orchestration workflow: explicit state routing, a condition-indexed reading table, an eight-stage build sequence with lint/check validation gates, and a completion checklist. Weaknesses are verbosity in the companion-flow and dispatch prose, and one dangling internal reference (sub-agents/frame-worker.md) in an otherwise well-structured bundle.

Suggestions

Cut the companion-flow commentary to directives only — e.g., replace 'Arrive as the director, not the contractor...' with 'Deliver the strongest treatment the brief supports; flag expensive layers (render time, sign-in, billing) as you name them.'

Add or restore `sub-agents/frame-worker.md` so the dispatch step's reference to this skill's own bundle resolves.

Break the stage-1 plan paragraph into a short bulleted list (plan contents, catalog search, storyboard recording) so each rule is scannable instead of one long sentence chain.

DimensionReasoningScore

Conciseness

The body is dense with directives and correctly assumes Claude's competence (no explanation of what video editing or timelines are), but passages like "Arrive as the director, not the contractor. A user who chose companion chose involvement and quality; the honest response is the best version you can design..." and the multi-clause catalog-search sentence in stage 1 are taste commentary and run-on prose that could be cut roughly in half. This matches 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the minor-trim level of 4.

3 / 5

Actionability

Owned operations are copy-paste ready: `npx hyperframes init "videos/<project>" --non-interactive --example=blank --skill=general-video`, `npx hyperframes check`, `node <MEDIA_DIR>/scripts/prefs.mjs record --hyperframes <PROJECT_ROOT>`, and `node <SKILL_DIR>/scripts/frame-packets.mjs --project "$PROJECT_DIR" --storyboard ...`. It falls short of 5 because several core operations (clip-range editing contracts, storyboard block format, worker role) are delegated to reference files with no inline minimal example, and placeholders like `$PROJECT_DIR` are used before being defined.

4 / 5

Workflow Clarity

Stages 1–8 give a clear dependency-ordered sequence with explicit validation checkpoints: "Use `npx hyperframes lint` for fast feedback", "For the final gate, run `npx hyperframes check`", a full "## 7. Done" completion checklist, and a first-matching-row state table for project state. This matches the anchor-5 pattern of sequence plus explicit validation and completion criteria.

5 / 5

Progressive Disclosure

Structure is good: a conditions table maps each situation to the exact reference to load, references are clearly signaled and mostly one level deep, and the bundle's own script `scripts/frame-packets.mjs` exists as referenced. Not 5 because the body cites this skill's own `sub-agents/frame-worker.md`, which is not present in the bundle, and the body inlines several long passages (companion flow, dispatch guidance) that read as reference material rather than overview.

4 / 5

Total

16

/

20

Passed

Description

87%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 with an explicit what/when pair, concrete trigger artifacts, and explicit routing boundaries against sibling skills (motion-graphics, hyperframes). The main weakness is limited action variety — 'author or edit' carries the whole 'what' — and a few triggers that assume plugin-internal vocabulary.

Suggestions

Add one or two more concrete action verbs beyond 'author or edit' (e.g., assemble, cut, sequence multi-scene pieces) to broaden the 'what' coverage.

Include a couple of user-natural synonyms such as 'promo video', 'compilation', or 'highlight reel' alongside the current trigger list.

DimensionReasoningScore

Specificity

"Author or edit a custom HyperFrames composition" names the domain and two concrete actions, and the use-case list ("brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds") covers concrete deliverable types. It stays at 4 rather than 5 because the action verbs are only 'author' and 'edit' — coverage of what is done within a composition is thin compared to the anchor-5 example's multiple distinct operations.

4 / 5

Completeness

What is explicit ("Author or edit a custom HyperFrames composition") and when is explicit with concrete trigger phrases ("when no specialized workflow fits", "Use for longer or multi-scene pieces..."). Not 4 because the 'when' is not merely implied or vague — it lists specific triggering artifacts and two routing conditions.

5 / 5

Trigger Term Quality

Natural terms a user would say include "brand and sizzle reels", "montages", "static loops", "static title cards", and "footage remixes". It misses 5 because some common user phrasings (e.g., 'promo video', 'compilation', 'edit clips together') are absent and several triggers are plugin-internal ("BRIEF.md sets flow: companion") rather than user-natural.

4 / 5

Distinctiveness Conflict Risk

It explicitly de-conflicts against neighbors: "Use motion-graphics instead for a short unnarrated motion-first unit" and "Route fresh creation through hyperframes before using this skill." This is a clear niche with distinct triggers and minimal conflict risk, matching the anchor-5 pattern.

5 / 5

Total

18

/

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

relative_links

Relative link issues: 1 suspicious

Warning

referenced_paths_exist

Referenced path issues: 16 missing

Warning

Total

14

/

16

Passed

Repository

freekmurze/dotfiles

Path

config/claude/skills/general-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.