html-ppt-zhangzara-editorial-tri-tone

A type-and-color system for a culture magazine relaunch — the grid, the tri-tone palette, and the layout kit. Built as a decision-grade design craft deck for editorial & design team.

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-editorial-tri-tone/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 a well-organized, lean template skill with concrete, copy-paste-ready guidance and a strong "best for/avoid for" framing. Its two weak spots are the missing validation checkpoint in the workflow and missing bundle files (example.html, LICENSE, template.json) that several references point to.

Suggestions

Add an explicit validation step to the workflow (e.g., after building, open the deck in a browser and confirm keyboard navigation works and assets resolve with no 404s) to close the feedback loop around the silent-break risk already noted in step 1.

Ship the referenced example.html, LICENSE, and template.json alongside assets/deck-stage.js so the clone instruction and source/license links resolve — currently only assets/deck-stage.js exists in the bundle.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — the blockquote and intro, "At a glance", and "Best for/Avoid for" are compact; the one elaboration (the assets/404 risk in step 1) is genuine craft knowledge, not padding Claude already knows.	3 / 3
Actionability	Guidance is concrete and specific for a template skill — "Clone example.html AND the assets/ folder", "Never substitute fonts, recolor the palette", and a copy-paste-ready <artifact> contract with identifier/type; absence of code is not penalized for an instruction-only skill with actionable guidance.	3 / 3
Workflow Clarity	The six numbered steps give a clear sequence, but there are no validation/verification checkpoints: the skill flags a silent navigation-break failure mode yet provides no step to verify the deck renders or that assets resolve, matching the "steps listed but checkpoints missing" anchor.	2 / 3
Progressive Disclosure	Sections are well organized and references are one-level-deep and clearly signaled (markdown links/code spans), but key referenced files — example.html, ./LICENSE, and template.json — are absent from the bundle (only assets/deck-stage.js ships), so navigation to those references is broken, capping the score below the top band.	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 is specific and niche-aware but stops at the middle band on every dimension: it names concrete deliverables without action verbs, carries some natural trigger terms without broad coverage, and gives a clear "what" with only an implied "when". It is solidly competent but lacks the explicit trigger guidance and action framing that would lift it to the top band.

Suggestions

Add an explicit "Use when..." clause naming concrete trigger situations (e.g., "Use when building a fashion/editorial magazine-style deck, brand pitch, or art-direction review needing tri-tone discipline and serif/sans contrast").

Broaden natural trigger terms to cover variations users actually say — "slides", "presentation", "fashion brand deck", "lookbook", "art direction review" — so activation coverage is comprehensive.

Lead with an action verb framing (e.g., "Builds an editorial design system: grid, tri-tone palette, and layout kit...") so capabilities read as concrete actions rather than a noun list.

Dimension	Reasoning	Score
Specificity	Quotes like "the grid, the tri-tone palette, and the layout kit" name concrete domain deliverables rather than actions; it is specific and not vague, but lacks the action verbs the top anchor requires ("Extract... fill... merge").	2 / 3
Completeness	It answers "what" (a type-and-color design deck) but the "when" is only implied via "for editorial & design team" with no "Use when..." clause; per the guidelines a missing explicit trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	Natural terms appear ("magazine", "editorial", "design", "deck") but common variations a user would say ("slides", "presentation", "fashion/brand deck", "lookbook") are missing, matching the "some relevant keywords but missing common variations" anchor.	2 / 3
Distinctiveness Conflict Risk	The editorial tri-tone magazine niche is fairly distinctive, but broad terms ("design", "deck", "design craft") leave it overlapping with other design/deck skills, matching the "somewhat specific but could still overlap" anchor rather than a clearly conflict-free niche.	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-editorial-tri-tone/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.