html-ppt-zhangzara-creative-mode

A brand visual-identity system reveal for an outdoor label — logo, color, type, and the rules that keep it consistent. Built as a decision-grade design craft deck for brand team, client.

Quality

65%

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-creative-mode/SKILL.md

Quality

Content

80%

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 actionable with concrete file names and an output contract. Its main gaps are the absence of validation checkpoints in the workflow and references to bundle files (LICENSE, template.json) that are not present.

Suggestions

Add a verification step to the workflow, e.g. after cloning, confirm assets/deck-stage.js resolves and keyboard navigation works before delivering the deck.

Ship the referenced ./LICENSE and template.json files in the bundle, or remove the links from 'Source & license' to avoid dangling references.

Condense step 1's 404 rationale into a one-line caution to tighten token use while preserving the actionable warning.

Dimension	Reasoning	Score
Conciseness	Lean, well-sectioned body with no concept explanation Claude already knows; each section (At a glance, Best/Avoid for, Workflow, Output contract) earns its place.	3 / 3
Actionability	Concrete, copy-paste-ready guidance: named files (assets/deck-stage.js), explicit clone/replace/preserve steps, and a literal <artifact> tag output template.	3 / 3
Workflow Clarity	Six steps are clearly sequenced, but there are no explicit validation or verification checkpoints, even around the asset-path and navigation-runtime cautions in steps 1 and 6.	2 / 3
Progressive Disclosure	Well-organized sections and one-level references, but cited files like ./LICENSE and template.json do not exist in the bundle, leaving dangling links.	2 / 3
	Total	10 / 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 concretely names the deliverable and its components but reads as a subject description rather than an action-and-trigger statement. It lacks an explicit 'Use when...' clause, which caps completeness.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger terms, e.g. 'Use when creating a brand visual-identity deck, logo/color/type system reveal, or design-led pitch for a brand team or client.'

Lead with concrete actions ('Build a brand visual-identity reveal deck — design logo, color, type, and consistency rules into...') rather than a noun-phrase subject description.

Sharpen distinctiveness by naming what sets this template apart from sibling deck templates (e.g., the cream-paper multi-accent Archivo Black system) directly in the description.

Dimension	Reasoning	Score
Specificity	Names concrete domain elements ('logo, color, type, and the rules that keep it consistent') but uses few action verbs, describing the deliverable rather than listing executable actions.	2 / 3
Completeness	Clearly states what the skill produces ('A brand visual-identity system reveal... Built as a decision-grade design craft deck') but provides no explicit 'when to use' trigger guidance, capping completeness at 2.	2 / 3
Trigger Term Quality	Includes relevant natural terms like 'brand', 'visual-identity', 'logo', and 'deck', but lacks a 'Use when...' clause and misses common variations a user might actually say.	2 / 3
Distinctiveness Conflict Risk	The 'visual-identity system reveal' niche is fairly specific, but the 'design craft deck' framing risks overlap with sibling template deck skills.	2 / 3
	Total	8 / 12 Passed

Validation

87%

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 — 14 / 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

	Total	14 / 16 Passed

Repository: nexu-io/open-design
Path: design-templates/html-ppt-zhangzara-creative-mode/SKILL.md
Commit: f2760fd

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