Tessl • The package manager for agent skills

The body is an exemplary compact template spec: token-efficient, packed with exact values, and organized in build order with explicit constraints (color palette limits, no lorem ipsum, prefers-reduced-motion fallback, single-file output). Its only notable gap is the absence of any copy-paste-ready code snippet for the trickier pieces like the SVG turbulence grain and rgbShift filter.

Dimension	Reasoning	Score
Conciseness	The body is a lean, dense spec — every line carries concrete instructions (exact colors like '#070708', sizes '6-9vw', timings '80-160ms', opacities) with zero explanation of concepts Claude already knows and no padding, matching anchor 5. Not 4 because there are no instances of over-explanation to trim.	5 / 5
Actionability	Guidance is highly concrete with specific CSS values (translate('-3px','1px'), clip-path slices, @keyframes durations, named fonts), but it is spec prose rather than copy-paste-ready code, and the noise-grain data URI is elided ('url("data:image/svg+xml,...turbulence...")'), matching anchor 4's 'concrete code with minor gaps' rather than anchor 5's fully executable example.	4 / 5
Workflow Clarity	This is a single-task skill under 50 lines whose one action — produce a single-file HTML glitch title frame — is unambiguous, with sections ordered by build layer (canvas → title → extra layers → optional SVG filter → design constraints). The simple-skill exception applies, and no destructive or batch operations exist that would require validation checkpoints, so it is not capped at 3 or 4.	5 / 5
Progressive Disclosure	The body is under 50 lines, needs no external references (none exist in the bundle and none are cited), and is organized into clearly labeled sections (canvas, title, extra layers, SVG filter, design details), matching the scoring note that simple skills with well-organized sections earn the top score.	5 / 5
	Total	19 / 20 Passed

Description

66%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 distinctive, technique-specific description that clearly conveys what the artifact is and where it is used, but it lacks an explicit 'Use when...' trigger clause and a leading action verb. The implied usage context keeps it from being vague, yet explicit trigger guidance is needed to reach the top levels.

Suggestions

Add an explicit trigger clause, e.g. 'Use when creating a glitch or cyberpunk title card, video transition frame, or distorted hero section.'

Lead with a third-person action verb, e.g. 'Creates a digital-glitch, chromatic-offset title frame...' so the skill's action is stated, not just the artifact.

Include common trigger synonyms such as 'VHS distortion', 'RGB split', or 'glitch text effect' to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	The description names three concrete visual techniques ("Digital glitch, chromatic offset, and data-corruption") plus two concrete use contexts ("video transitions or cyberpunk heroes"), matching anchor 4's several specific items with minor gaps; it falls short of 5 because it is a noun phrase with no explicit action verb.	4 / 5
Completeness	The 'what' is clear (a digital-glitch title frame), but the 'when' is only weakly implied by "for video transitions or cyberpunk heroes" with no 'Use when...' clause, which caps completeness at 3 per the judging guidelines. It is not 4 because the when-usage is not explicit, and not 2 because the what is specific and a usage context is at least implied.	3 / 5
Trigger Term Quality	Natural keywords a user would say are present — "glitch", "cyberpunk", "title frame", "video transitions" — giving good coverage per anchor 4, but common synonyms like "VHS distortion", "RGB split", or "distorted text" are missing, so not 5.	4 / 5
Distinctiveness Conflict Risk	The niche is distinctive (glitch/chromatic-offset/cyberpunk title frames) with terms unlikely to trigger unrelated skills, but within a video/VFX template family closely related frame effects could overlap, matching anchor 4 ('mostly distinct; minor overlap risk with closely related skills') rather than 5's minimal conflict risk.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: skills/frame-glitch-title/SKILL.md
Revision: 78d5637

Reviewed: 11 days ago

Discovery Implementation Validation

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.

frame-glitch-title

Table of Contents

Is this your skill?