html-ppt-zhangzara-mat

A margin-recovery diagnosis for a regional grocery chain — the governing thought, the driver tree, the priorities, and the roadmap. Built as a decision-grade consulting deck for client sponsor, steering committee.

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-mat/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, actionable, and well-structured for a template-styling skill, but it lacks an explicit validation/verification step in its workflow and references bundle files that do not exist alongside it. Adding a verify step and ensuring referenced files are present would lift the two middle dimensions.

Suggestions

Add an explicit validation checkpoint to the workflow, e.g. 'Open the emitted deck and confirm it renders; run a critic pass against the Monday-morning rubric before delivering.'

Ensure the referenced files (LICENSE, example.html, template.json, and any assets/ runtime) actually ship in the skill bundle, or remove/soften the references so navigation is not broken.

Clarify which referenced artifacts are required vs. optional (e.g. mark assets/deck-stage.js as 'if shipped') so the reader knows what to expect in the bundle.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-paced — 'A single self-contained HTML deck... Mixing layouts across templates breaks the system; stay inside this one.' — with no padding or explanation of concepts Claude already knows.	3 / 3
Actionability	It gives concrete instructions ('Clone example.html into the user's workspace', 'Replace placeholder content', 'Preserve the design system', 'Adjust deck length by duplicating layouts') and an exact output contract with the artifact tag format, all copy-ready for an instruction/template skill.	3 / 3
Workflow Clarity	The six-step Workflow is clearly sequenced, but there is no validation or verification checkpoint (e.g. 'confirm the deck renders / critic pass against the rubric before emitting'); for a produced-output deck task the rubric caps workflow clarity at 2 without a feedback loop.	2 / 3
Progressive Disclosure	Sections are well organized, but the body references files that are not present in the bundle — './LICENSE', 'example.html', 'template.json', and 'assets/deck-stage.js' — with no references/ directory, so the navigation it promises is not actually backed by the bundle structure.	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 is specific about the deliverable and domain but lacks an explicit 'when to use it' trigger and relies on consulting jargon over natural user language. Adding a 'Use when...' clause with plain-language triggers would raise completeness and trigger-term quality.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when the user needs a margin-recovery or profit-improvement diagnosis deck, a consulting final deliverable, or a decision-grade slide pack for a client sponsor or steering committee.'

Replace or supplement internal jargon ('governing thought', 'driver tree') with natural trigger terms users would actually say ('profit-margin analysis', 'consulting deck', 'final deliverable slides').

Sharpen distinctiveness by naming the single thing that sets this skill apart (a mid-century Mat-styled HTML consulting deck) so it does not collide with other deck/presentation skills.

Dimension	Reasoning	Score
Specificity	The description names the domain ('margin-recovery diagnosis for a regional grocery chain') and lists several concrete deliverables — 'the governing thought, the driver tree, the priorities, and the roadmap' — and the form ('decision-grade consulting deck').	3 / 3
Completeness	It clearly answers 'what does this do' but never states 'when Claude should use it' with an explicit trigger; per the rubric guideline, a missing 'Use when...' clause caps completeness at 2.	2 / 3
Trigger Term Quality	It includes some relevant terms ('consulting deck', 'margin-recovery', 'steering committee') but leans on domain-internal jargon ('governing thought', 'driver tree') rather than natural phrases a user would say, and offers no 'Use when...' phrasing.	2 / 3
Distinctiveness Conflict Risk	The grocery-chain margin-recovery niche is fairly specific, but 'consulting deck / final deck' could overlap with other deck skills and there is no explicit distinguishing trigger to prevent misfires.	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-mat/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.