html-ppt-zhangzara-soft-editorial

A digital-transformation roadmap for a legacy insurer — the diagnosis, the sequenced bets, and the operating rhythm to land them. Built as a decision-grade consulting deck for client executives.

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-soft-editorial/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 and highly actionable with a clear output contract, but the workflow omits an explicit validation checkpoint and it references two files (LICENSE, template.json) that are absent from the bundle. These gaps hold it back from a top score despite otherwise strong structure.

Suggestions

Add a verification step to the workflow (e.g., 'Open the artifact in a browser and confirm keyboard navigation works before delivering').

Ship the referenced ./LICENSE and template.json files in the skill bundle, or remove the references if they are not intended to be bundled.

Consider a short 'Validation' or 'QA' subsection that lists what to check in the rendered deck before presenting it to the user.

Dimension	Reasoning	Score
Conciseness	The body is lean and well sectioned (At a glance, Best for, Avoid for, Workflow, Output contract) and never explains concepts Claude already knows; every section earns its tokens.	3 / 3
Actionability	Concrete instructions ('Clone example.html AND the assets/ folder', 'Never substitute fonts, recolor the palette', 'Adjust deck length by duplicating layouts') plus a literal copy-paste <artifact> output contract give fully actionable, specific guidance.	3 / 3
Workflow Clarity	The six workflow steps are clearly sequenced, but there is no explicit validation or verification checkpoint (e.g., confirm the deck renders or that keyboard navigation works), so the sequence lacks an explicit feedback loop.	2 / 3
Progressive Disclosure	Sections are well organized and the assets/deck-stage.js reference resolves to a real file, but the body also references ./LICENSE and template.json as shipping in the skill when neither exists in the bundle, leaving broken navigation 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 is specific to its subject and uses correct third-person voice, but it reads as a content summary rather than a capability/trigger statement and omits any explicit 'Use when' guidance. It is solid but not exemplary, scoring 2 across all dimensions.

Suggestions

Add an explicit 'Use when...' clause listing natural trigger terms (e.g., 'Use when the user needs a consulting deck, strategy deck, or digital-transformation roadmap for executive stakeholders').

Reframe the description around the skill's actions (e.g., 'Builds and renders a decision-grade consulting deck...') rather than only describing the deck's content.

Include common trigger variations like 'slides', 'presentation', and 'strategy deck' to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	It names the domain and concrete content elements ('the diagnosis, the sequenced bets, and the operating rhythm to land them', 'decision-grade consulting deck for client executives'), but it describes the deck's content rather than enumerating the skill's own actions, so it is not a comprehensive action list.	2 / 3
Completeness	It states what the skill produces (a decision-grade consulting deck) but has no explicit 'Use when...' trigger clause, so completeness is capped at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	'digital-transformation roadmap' and 'consulting deck' are natural terms, but common variations users would say (slides, presentation, strategy deck) are missing.	2 / 3
Distinctiveness Conflict Risk	The legacy-insurer subject is fairly niche, but the 'consulting deck' / strategy-deliverable category overlaps with sibling consulting-deck skills, so it is not clearly conflict-free.	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-soft-editorial/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.