html-ppt-zhangzara-8-bit-orbit

A gamer's journey building a retro-arcade collection — the obsession, the hunt, and what the machines came to mean. Built as a decision-grade story deck for friends, hobby community.

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./design-templates/html-ppt-zhangzara-8-bit-orbit/SKILL.md

Quality

Content

65%

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 clean, concise template guide with a concrete workflow and copy-paste output contract, but it stops short of executable commands and lacks any validation checkpoint. Its progressive-disclosure structure would score higher if the referenced bundle files (LICENSE, example.html, template.json, assets/) actually shipped alongside the skill.

Suggestions

Add a verification checkpoint to the workflow (e.g. open example.html in a browser / run an HTML lint pass and confirm all asset paths resolve before emitting the artifact).

Ship the referenced bundle files (LICENSE, example.html, template.json, and the assets/ runtime) so the signaled references are real rather than dangling.

Where possible, replace abstract design direction ('design it from scratch using the same fonts, palette') with concrete anchors (font-family values, hex palette tokens, spacing rhythm) from the template.

Dimension	Reasoning	Score
Conciseness	The body is lean: short at-a-glance facts, tight 'Best for'/'Avoid for' guidance, and a six-step workflow with no padding or explanations of concepts Claude already knows; every section earns its place.	3 / 3
Actionability	Concrete guidance is present (clone example.html, replace placeholders, preserve named decorative elements, duplicate layouts, emit an <artifact> block) and the output contract is copy-paste ready, but there are no executable commands and steps like 'design it from scratch using the same fonts' remain abstract.	2 / 3
Workflow Clarity	The six numbered steps form a clear sequence, but there is no validation or verification checkpoint (e.g. preview/render check, link or asset integrity check) and no error-recovery loop, so checkpoints are missing rather than explicit.	2 / 3
Progressive Disclosure	The overview is well-organized and references are clearly signaled one level deep ([LICENSE](./LICENSE), example.html, template.json, assets/deck-stage.js), but none of these bundle files actually exist on disk, so the disclosure path is broken with dangling references.	2 / 3
	Total	9 / 12 Passed

Description

50%

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 conveys a vivid subject and a single concrete capability, but it reads as an example-topic blurb rather than a capability+trigger statement, and it omits an explicit 'Use when' clause. Trigger coverage leans on the separate triggers list instead of being embedded in the description.

Suggestions

Rewrite the description in third-person capability form naming several concrete actions (e.g. 'Builds, writes, and critiques a decision-grade story deck from a hobby or photo-essay subject').

Add an explicit 'Use when...' clause listing natural trigger terms (e.g. 'Use when the user wants a personal photo-essay or hobby story deck, html slides, or a decision-grade life deck').

Tighten trigger terms to the skill's distinctive niche (retro-arcade / 8-bit visual system) to reduce overlap with generic story-deck skills.

Dimension	Reasoning	Score
Specificity	Names a concrete domain ('building a retro-arcade collection — the obsession, the hunt') and an action ('Built as a decision-grade story deck'), but the capability verbs are limited to one (building a deck) rather than a comprehensive set of concrete actions.	2 / 3
Completeness	Clearly states what the skill produces (a decision-grade story deck about a gamer's retro-arcade collection) but the 'when to use it' trigger is only implied via the subject matter and the external triggers list — there is no explicit 'Use when...' clause, which caps completeness at 2.	2 / 3
Trigger Term Quality	Contains some natural niche terms ('retro-arcade collection', 'story deck', 'hobby community') but relies on the separate triggers list for coverage and lacks common phrasings a user would naturally say; no explicit 'Use when' phrasing in the description itself.	2 / 3
Distinctiveness Conflict Risk	The retro-arcade / hobby-story niche is fairly specific, but the skill is really a general hobby-story-deck template (per en_name) and the trigger list shares broad terms ('life', 'story', 'personal', 'photo-essay') that could overlap with sibling deck skills.	2 / 3
	Total	8 / 12 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 missing	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	13 / 16 Passed

Repository: nexu-io/open-design
Path: design-templates/html-ppt-zhangzara-8-bit-orbit/SKILL.md
Commit: f2760fd

Reviewed: 2 days 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.