html-ppt-zhangzara-raw-grid

A brutalist poster-series case study for a music festival — the concept, the system, and how it scaled across formats. Built as a decision-grade design craft deck for design peers, client.

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-raw-grid/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 and actionable with a clear sequenced workflow, but lacks a validation checkpoint and references bundle files (LICENSE, template.json, example.html, assets/) that are not present, weakening workflow clarity and progressive disclosure.

Suggestions

Add an explicit validation/verification step to the workflow, e.g., confirm the deck opens in a browser and the design system (fonts, palette, decorative elements) is intact before emitting.

Ship the referenced bundle files (example.html, template.json, LICENSE, and assets/) so the one-level-deep references resolve to real material.

Reconcile the output contract (artifact identifier='zhangzara-raw-grid') with the workflow so the final emitted artifact is explicitly the validated result of step 6.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding or explanation of concepts Claude already knows; every section (at a glance, best for, avoid for, workflow, output contract) earns its place.	3 / 3
Actionability	Guidance is concrete and executable for an instruction skill: clone example.html, replace placeholders matching dimensions, duplicate layouts, and emit a specific <artifact> block with a named identifier.	3 / 3
Workflow Clarity	Six numbered workflow steps are clearly sequenced, but there is no validation or verification checkpoint (e.g., checking the HTML renders or the design system is preserved), which per the guidelines caps workflow clarity at 2.	2 / 3
Progressive Disclosure	Sections are well organized with one-level-deep references to ./LICENSE, template.json, and example.html, but none of these referenced bundle files actually ship with the skill, so the signaled navigation points to missing material.	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 is specific and distinctive about its niche, but lacks an explicit 'when to use' trigger clause and natural user-facing trigger terms, which caps completeness and trigger term quality.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers such as 'poster series', 'festival posters', 'case study deck', or 'design craft slides'.

List concrete actions the skill performs (e.g., 'drafts slide plan, writes slides, sets visual direction, runs a critic pass') to raise specificity.

Surface the most natural user keywords ('poster', 'deck', 'slides') in the description text rather than only in tags/triggers.

Dimension	Reasoning	Score
Specificity	Names the domain ('brutalist poster-series case study for a music festival') and a few abstracted actions ('the concept, the system, and how it scaled across formats'), but does not enumerate multiple concrete actions like the score-3 anchor.	2 / 3
Completeness	Clearly states what the skill produces, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	Contains some relevant domain framing ('poster-series case study', 'music festival', 'design craft deck'), but no explicit natural trigger keywords such as 'poster', 'slides', or 'deck' appear in the description itself, missing common variations.	2 / 3
Distinctiveness Conflict Risk	'Brutalist poster-series case study for a music festival ... decision-grade design craft deck' carves a clear niche with distinct triggers, making it unlikely to fire for unrelated skills.	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-raw-grid/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.