CtrlK
BlogDocsLog inGet started
Tessl Logo

frame-glitch-title

Digital glitch, chromatic offset, and data-corruption title frame for video transitions or cyberpunk heroes.

60

Quality

70%

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 ./skills/frame-glitch-title/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 a tight, concrete design spec with actionable values and clean section organization well-suited to a simple single-frame template skill. It lacks a complete executable HTML artifact and explicit validation checkpoints, capping actionability and workflow clarity just below full marks.

DimensionReasoningScore

Conciseness

The body is a dense, spec-style list with concrete values and no padding explaining what glitch art is; only minor bits like 'Inspired by hyperframes glitch' could be trimmed, so it is efficient but not perfectly lean.

4 / 5

Actionability

Concrete guidance dominates — exact hex colors, px/vw sizes, font names, keyframe durations, and CSS filter references — making it mostly executable, though it stops short of complete copy-paste HTML.

4 / 5

Workflow Clarity

Sections are logically ordered (canvas, title, additional layers, filter, design details) and the single-frame task is unambiguous, but it is not a numbered sequence with explicit validation checkpoints, so it sits just below 5.

4 / 5

Progressive Disclosure

This is a simple under-50-line single-purpose skill with no external references and well-organized section headers, meeting the rubric's exception allowing a 5 on progressive disclosure for well-structured simple skills.

5 / 5

Total

17

/

20

Passed

Description

61%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 specific and distinctive about its niche but lacks an explicit 'Use when...' trigger clause, capping completeness. Trigger-term coverage is good but includes some technical jargon over natural phrasing.

Suggestions

Add an explicit trigger clause, e.g. 'Use when creating glitch or cyberpunk title frames, video transitions, or VFX hero shots.'

Soften technical jargon ('chromatic offset', 'data-corruption') with natural synonyms users actually say, and include file/context cues.

Lead with concrete verb-based actions (e.g. 'Generates... applies... overlays...') rather than a noun-heavy attribute list.

DimensionReasoningScore

Specificity

The description names the domain with three concrete visual techniques ("Digital glitch, chromatic offset, and data-corruption") and the output type, but these are descriptive attributes rather than concrete verb-based actions, so it sits at the 'names domain and 1-2 concrete actions' level.

3 / 5

Completeness

The "what" is clear (a glitch title frame), but there is no explicit "Use when..." clause; the trailing "for video transitions or cyberpunk heroes" is only weak implicit trigger guidance, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Natural terms users would say are present ("glitch", "cyberpunk", "title", "video transitions"), giving good keyword coverage, though "chromatic offset" and "data-corruption" lean technical and a few synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

The niche (glitch/cyberpunk data-corruption title frames) is mostly distinct with minimal overlap risk, though it could overlap with other video title or VFX template skills.

4 / 5

Total

14

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
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.