CtrlK
BlogDocsLog inGet started
Tessl Logo

frame-logo-outro

Segmented logo assembly, glow bloom, and tagline reveal for video outros or brand closing frames.

64

Quality

76%

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/frame-logo-outro/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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 lean, well-organized spec with concrete values and a clear build sequence. Its main weakness is that code fragments contain placeholders and are not fully executable.

Suggestions

Replace placeholder code fragments (e.g. 'filter: drop-shadow(0 0 24px <accent>40)' and 'radial-gradient(...)') with complete, copy-paste-ready CSS so the template is immediately executable.

Provide one minimal fully-assembled HTML/SVG snippet demonstrating the logo block assembly and glow bloom so the spec translates directly into runnable output.

DimensionReasoningScore

Conciseness

The body is a dense spec sheet with concrete values (hex colors, timings, font weights) and no padding explaining concepts Claude already knows, matching the lean-and-efficient anchor.

3 / 3

Actionability

Concrete guidance is present (exact colors, keyframe timings, font specs), but code fragments are incomplete with placeholders like '<accent>40' and truncated 'radial-gradient(...)' rather than copy-paste-ready executable code.

2 / 3

Workflow Clarity

As a single-purpose frame template the build sequence is unambiguous and well-sequenced (logo entrance → bloom → brand name at 1.4s → tagline at 1.8s → CTA), which scores 3 for a simple skill per the scoring notes.

3 / 3

Progressive Disclosure

The skill is under 50 lines, has no bundle files (references/scripts/assets absent), and is organized into clear sections (画布/布局/调色/设计细节), qualifying for 3 under the simple-skill guideline.

3 / 3

Total

11

/

12

Passed

Description

67%

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 occupies a clear niche, naming three concrete visual actions. It is held back by a lack of explicit 'Use when' trigger guidance and limited keyword variation coverage.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when creating video outros, end cards, brand closing frames, or logo reveal animations.'

Broaden trigger terms to include natural variations users might say (e.g. 'end card', 'logo reveal', 'closing animation') alongside 'video outros' and 'brand closing frames'.

DimensionReasoningScore

Specificity

Lists three concrete actions — 'Segmented logo assembly, glow bloom, and tagline reveal' — rather than vague language, matching the multiple-specific-actions anchor.

3 / 3

Completeness

States clearly what the skill does, but the trigger ('for video outros or brand closing frames') is only implied and there is no explicit 'Use when...' clause, which per guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Includes natural terms 'video outros' and 'brand closing frames', but coverage is thin and misses common variations like 'logo reveal', 'end card', or 'outro', fitting the 'some relevant keywords but missing variations' anchor.

2 / 3

Distinctiveness Conflict Risk

Targets a clear niche — branded video closing frames — with distinct triggers, making conflict with unrelated skills unlikely.

3 / 3

Total

10

/

12

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.