html-ppt-zhangzara-retro-zine

A neighborhood zine on the disappearing corner shops — portraits, voices, and what a block loses when they close. Built as a decision-grade story deck for community, local readers.

Quality

68%

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-retro-zine/SKILL.md

Quality

Content

80%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise, well-structured, and gives concrete actionable guidance with a precise output contract. Its weaknesses are the absence of an explicit validation/verification step in the workflow and that referenced bundle files (example.html, LICENSE, template.json) do not actually exist in the skill directory.

Suggestions

Add an explicit validation/critic step to the workflow (e.g. open the emitted HTML and check fonts/palette/spacing are intact before delivering) to move workflow clarity to 3.

Ship the referenced bundle files (example.html, LICENSE, template.json, and any assets/) so the one-level-deep references resolve, which is required for progressive disclosure to score 3.

Add a short verification checklist at the end of the workflow (page-number labels updated, decorative elements preserved, navigation runtime intact).

Dimension	Reasoning	Score
Conciseness	The body is lean and well-sectioned ("At a glance", "Best for", "Avoid for", "Workflow", "Output contract", "Source & license") with a one-line identity blockquote and no padding or explaining of concepts Claude already knows; every section earns its place, matching the score-3 anchor.	3 / 3
Actionability	Guidance is concrete and specific for an instruction-only skill: "Clone `example.html`", "Never substitute fonts, recolor the palette", "duplicate an existing slide", and an exact `<artifact>` output contract; per the scoring notes, absence of code is not penalized when guidance is this actionable, so it reaches score 3.	3 / 3
Workflow Clarity	The workflow is a clear numbered sequence (steps 1-6), but it has no explicit validation or verification checkpoint (no "validate the HTML" or critic pass in the body), and the score-3 anchor requires explicit validation steps and feedback loops; it is above score 1's unclear/missing sequence but capped at 2 by the missing checkpoints.	2 / 3
Progressive Disclosure	Sections are well-organized and references are one level deep and clearly signaled ("[`LICENSE`](./LICENSE)", "`template.json`", "`example.html`"), but the referenced bundle files (example.html, LICENSE, template.json, assets/deck-stage.js) are not present in the skill bundle, so the navigation points to missing material rather than a clean split, holding it at score 2.	2 / 3
	Total	10 / 12 Passed

Description

57%Weight 40%Scale 1-3

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, distinctive niche and target audience but reads more like a story premise than a capability/trigger statement. It lacks explicit "Use when..." guidance and functional trigger terms, which hold completeness and trigger quality at the middle band.

Suggestions

Add an explicit "Use when..." clause naming when to invoke the skill (e.g. when the user wants an HTML photo-essay/zine deck) to raise completeness.

Include functional trigger terms users would actually say ("html deck", "slides", "photo-essay", "zine") alongside the narrative phrasing.

Lead with the concrete actions the skill performs (build an HTML deck from a template, swap in real content, preserve the design system) before the story premise.

Dimension	Reasoning	Score
Specificity	Names the domain and a few concrete content elements ("portraits, voices, and what a block loses when they close", "decision-grade story deck") but describes the product rather than listing multiple distinct skill actions, so it does not reach the score-3 level of enumerated capabilities.	2 / 3
Completeness	It states what the deck is ("a neighborhood zine on the disappearing corner shops") and implies an audience ("for community, local readers"), but lacks any explicit "Use when..." trigger clause, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Terms like "neighborhood zine", "corner shops", "story deck", "community", "local readers" are natural for the niche but miss common functional variations a user would say (e.g. "html deck", "slides", "photo-essay"), placing it above score 1 yet short of score 3's broad coverage.	2 / 3
Distinctiveness Conflict Risk	The niche is sharply specific ("disappearing corner shops", "neighborhood zine") with a distinct subject framing, making it unlikely to trigger for the wrong skill; it clearly clears the score-3 anchor of a clear niche with distinct triggers.	3 / 3
	Total	9 / 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-retro-zine/SKILL.md
Commit: f2760fd

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