html-ppt-zhangzara-signal

Open Design's strategy memo: should it monetize the plugin registry now or hold — options, risks, and the recommendation. Built as a decision-grade corporate strategy deck for CEO, strategy team.

Quality

61%

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

Quality

Content

65%

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 gives a clear sequenced workflow with a concrete output contract. Its main weaknesses are missing validation checkpoints in the workflow and references to bundle files (example.html, LICENSE, template.json, assets/) that are not present in the skill bundle.

Suggestions

Add a verification step to the workflow, e.g. after replacing placeholders: confirm no placeholder text remains and that the deck still renders before emitting the artifact.

Ship the referenced bundle files (example.html, template.json, LICENSE, and assets/deck-stage.js if used) so the 'Clone example.html' instruction is actually executable, or remove references to files that are not bundled.

Include a minimal concrete HTML snippet (a single slide skeleton in the template's design system) so the guidance is copy-paste ready even before opening example.html.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: tight sections (At a glance, Best for, Avoid for, Workflow, Output contract) with no padding or explanation of concepts Claude already knows.	3 / 3
Actionability	Concrete workflow steps and an explicit <artifact> output contract are present, but guidance depends on example.html/template.json which are not in the bundle, and no actual HTML/code example is shown beyond the artifact wrapper skeleton.	2 / 3
Workflow Clarity	Six steps are clearly numbered and sequenced, but there are no validation checkpoints (e.g., confirm all placeholders replaced, verify the deck renders), so checkpoints are missing.	2 / 3
Progressive Disclosure	Sections are well-organized and references are clearly signaled one level deep (./LICENSE, example.html, template.json, assets/deck-stage.js), but none of the referenced bundle files actually exist, so the disclosure is not functional.	2 / 3
	Total	9 / 12 Passed

Description

57%

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 conveys a clear, distinct niche and a recognizable output format, but it is dominated by a single hardcoded example subject and omits any explicit 'Use when...' trigger guidance. It answers 'what' well enough but only implies 'when'.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when the user needs a board pre-read deck, corporate strategy memo, or business-review decision deck').

Generalize the description so the capability leads and the Open Design example is illustrative rather than the headline, e.g. 'Writes decision-grade corporate strategy decks: frames options, risks, and a recommendation for a CEO/board audience.'

List the concrete actions the skill performs (structure the decision, draft options/risk slides, produce the HTML deck) rather than describing only the subject matter.

Dimension	Reasoning	Score
Specificity	Names the domain ('corporate strategy deck') and an output action ('options, risks, and the recommendation'), but does not enumerate multiple concrete actions; it is topic-bound to the Open Design example rather than capability-listing.	2 / 3
Completeness	The 'what' (build a decision-grade corporate strategy deck) is present, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	Contains relevant natural terms ('strategy memo', 'corporate strategy deck', 'CEO', 'board'), but they are buried under a hardcoded subject ('Open Design's plugin registry') and lack common variations a user would naturally say.	2 / 3
Distinctiveness Conflict Risk	The niche (decision-grade corporate strategy / board pre-read deck) is clearly scoped and unlikely to conflict with unrelated skills, even though the example subject is overly specific.	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-signal/SKILL.md
Commit: f2760fd

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