html-ppt-zhangzara-block-frame

Rescuing a messy startup deck into a board-grade system — the diagnosis, the page grammar, and the rebuilt proof pages. Built as a decision-grade design craft deck for founders, exec presenter.

Quality

70%

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-block-frame/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 content is concise, well-structured, and highly actionable with concrete file operations and a clear output contract. Its main gaps are the absence of an explicit verification checkpoint in the workflow and references to bundle files that are not present.

Suggestions

Add a final verification step to the Workflow (e.g., 'Open the deck in a browser to confirm navigation and layout render correctly before delivering').

Ensure referenced bundle files (example.html, LICENSE, template.json, and any assets/) actually ship in the skill directory, or remove the references if they are not bundled.

Dimension	Reasoning	Score
Conciseness	The body is lean and sectioned ('At a glance', 'Best for', 'Avoid for', 'Workflow', 'Output contract') with no padding or explanation of concepts Claude already knows, matching the 'lean and efficient; every token earns its place' anchor.	3 / 3
Actionability	Concrete executable guidance such as 'Clone example.html', the copy-paste-ready <artifact> skeleton, and 'leave assets/deck-stage.js intact' matches the 'fully executable; copy-paste ready' anchor.	3 / 3
Workflow Clarity	The numbered 6-step Workflow is clearly sequenced, but for producing an HTML artifact there is no validation/verification checkpoint (e.g., 'open in a browser to verify'), which per the guidelines caps workflow clarity at 2.	2 / 3
Progressive Disclosure	The body is well-organized but references bundle files (example.html, LICENSE, template.json, assets/) that do not actually exist in the skill directory, so references are not reliably signaled to real files; matches the 'some structure but could be better organized' anchor.	2 / 3
	Total	10 / 12 Passed

Description

60%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 clearly conveys a concrete deck-rescue capability for a defined audience but lacks an explicit 'Use when...' trigger clause and relies on buzzy phrasing rather than natural user keywords. It is specific in action but only average in trigger quality and completeness.

Suggestions

Add an explicit 'Use when ...' clause listing natural trigger phrases (e.g., 'Use when the user wants to rescue a messy slide deck, upgrade a startup pitch to board-grade, or rebuild a presentation into a design system').

Replace buzzy terms ('board-grade system', 'decision-grade design craft deck') with concrete keywords a user would actually say, such as 'slide deck', 'pitch deck', 'presentation redesign', and 'deck upgrade'.

Dimension	Reasoning	Score
Specificity	Quotes 'Rescuing a messy startup deck into a board-grade system — the diagnosis, the page grammar, and the rebuilt proof pages' name multiple concrete deliverables, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	It states what the skill does but only implies when via audience ('for founders, exec presenter') with no 'Use when...' clause, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	The phrase 'board-grade system' and 'decision-grade design craft deck' are buzzy rather than natural user keywords, and common terms like 'slide deck' or 'deck upgrade' are absent; matches the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The deck-rescue niche is fairly specific, but broad tags ('design', 'brand', 'visual-system') could overlap with general design skills, matching the 'somewhat specific but could still overlap' anchor.	2 / 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-block-frame/SKILL.md
Commit: f2760fd

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