frame-logo-outro

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

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/frame-logo-outro/SKILL.md

Quality

Content

61%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 content is a compact, well-structured design spec with concrete parameters, but it relies on fragments and placeholders rather than a runnable HTML example, and lacks validation/preview checkpoints in its workflow. Providing a copy-paste scaffold and a render/reduced-motion verification step would lift the weakest dimensions.

Suggestions

Include one complete, copy-paste-ready single-file HTML scaffold (or a runnable snippet) so the common case is executable rather than assembled from hints.

Add a verification step such as 'preview index.html at 1920×1080 and confirm freeze-on-complete and prefers-reduced-motion fallback' to introduce a validation checkpoint.

Convert the bracketed pseudo-headers (【...】) into standard markdown headers (## ...) for cleaner navigation and rendering.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes competence — specific hex colors, timings, weights, and animation parameters with no concept-explaining padding. Not a 5 because a few phrases (e.g., the source-credit line and repeated intent statement) could be trimmed further.	4 / 5
Actionability	Concrete, executable guidance is present in fragments (hex colors, drop-shadow filter, @keyframes, animation-delay) but there is no complete copy-paste code block or full HTML scaffold; much is parameter hints like `<accent>40` and `radial-gradient(...)` that need assembly. Not a 4 because the common case is not covered by runnable code.	3 / 5
Workflow Clarity	The animation timeline is sequenced with timings (logo 1.2s, brand name at 1.4s, tagline at 1.8s, freeze on completion), giving a clear sequence. It stays at 3 because there are no validation/verification checkpoints (e.g., preview/render check, reduced-motion verification), and the rubric caps workflow clarity at 3 when validation is absent for the build pipeline.	3 / 5
Progressive Disclosure	The body is a single, well-organized overview with clear section headers (意图/画布/布局/调色/设计细节) and no nested references; no bundle files exist, which is appropriate for a short single-purpose template. Not a 5 only because the structure uses brackets rather than standard markdown navigation, though it is easy to navigate.	4 / 5
	Total	14 / 20 Passed

Description

53%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 clearly states the 'what' with three concrete signature effects in a distinct niche, but lacks an explicit 'Use when...' trigger clause and the trigger-term coverage is moderate. Adding a concrete usage trigger and richer natural synonyms would lift the weakest dimensions.

Suggestions

Add an explicit 'Use when ...' clause naming natural user phrasings (e.g., 'Use when creating a video outro, end card, or brand closing frame with an animated logo reveal').

Expand trigger terms to include common synonyms like 'end card', 'outro template', and 'logo reveal' directly in the description, not only in tags.

Consider listing a couple more concrete actions (e.g., CTA row, ribbon) to push specificity toward a comprehensive coverage score.

Dimension	Reasoning	Score
Specificity	Names the domain (video outros / brand closing frames) and three concrete visual actions (segmented logo assembly, glow bloom, tagline reveal), but the actions are feature names rather than a comprehensive set of operations. Not a 4 because coverage is limited to exactly three signature effects with no broader capability list.	3 / 5
Completeness	The 'what' is clear (segmented logo assembly, glow bloom, tagline reveal) but there is no explicit 'Use when...' trigger guidance in the description itself. Per the rubric, a missing 'Use when' clause caps completeness at 3.	3 / 5
Trigger Term Quality	Contains relevant natural terms (logo, outro, brand closing frames, video) but lacks common variations and file/format extensions a user might say. Not a 4 because synonyms like 'end card', 'video outro', ' outro template' are present only as tags, not in the description itself, and several natural phrasings are missing.	3 / 5
Distinctiveness Conflict Risk	Niche is fairly distinct — combining logo assembly + glow bloom + tagline reveal for video outros is specific and unlikely to fire for unrelated skills. Not a 5 because 'brand closing frames' has some overlap with generic branding/title skills.	4 / 5
	Total	13 / 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-logo-outro/SKILL.md
Commit: d4138ea

Reviewed: ~20 hours ago

Table of Contents

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.