html-ppt-zhangzara-cobalt-grid

Open Design renewal + seat-expansion business case for a growing customer: realized value, usage proof, and the expansion ROI. Built as a decision-grade B2B sales deck for champion, finance approver.

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

Quality

Content

65%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 and well-structured with a clear workflow, but it offers no executable code example, lacks a validation checkpoint, and references bundle files (example.html, LICENSE, template.json, assets/) that are not present in the skill.

Suggestions

Ship the referenced bundle files (example.html, LICENSE, template.json, assets/deck-stage.js) so the overview's references actually resolve, or remove the references if the files are not part of this skill.

Add a small concrete HTML snippet or slide skeleton in the output contract so the guidance is copy-paste-ready rather than a placeholder wrapper.

Add an explicit validation/critic step to the workflow (e.g. 'Verify the deck still renders and the design system is intact before delivering') to close the feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — short 'At a glance' bullets, a 'Best for'/'Avoid for' split, a 6-step workflow, and a tight output contract — with no padding of concepts Claude already knows.	3 / 3
Actionability	Steps are actionable ('Clone example.html', 'Replace placeholder content', 'duplicate an existing slide') but there is no executable example — the output contract only shows an '<html>...</html>' placeholder rather than concrete, copy-paste-ready structure.	2 / 3
Workflow Clarity	The 6-step workflow is clearly sequenced (clone → replace → preserve → adjust length → design missing layouts → keep navigation) but contains no validation or verification checkpoint, so it lands at the 'steps present, checkpoints missing' anchor.	2 / 3
Progressive Disclosure	The body is well-organized as an overview with clearly signaled, one-level-deep references (example.html, LICENSE, template.json, assets/deck-stage.js), but none of those referenced bundle files actually exist in the skill directory, so the navigation does not resolve.	2 / 3
	Total	9 / 12 Passed

Description

72%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 domain-specific with natural trigger terms and a clear, distinctive niche, but it lacks an explicit 'Use when...' clause and describes the deliverable rather than enumerating concrete skill actions.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks for a renewal or expansion business case, a B2B sales deck, or a champion/finance-approver proposal.'

Lead with concrete skill actions (e.g. 'Generates a renewal + seat-expansion business case deck: structures realized-value proof, usage evidence, and expansion ROI') rather than describing the output passively.

Dimension	Reasoning	Score
Specificity	The description names the domain and deliverable ('Open Design renewal + seat-expansion business case', 'realized value, usage proof, and the expansion ROI') but does not enumerate multiple concrete skill actions, instead describing the output ('Built as a decision-grade B2B sales deck').	2 / 3
Completeness	It clearly answers 'what' (builds a renewal + expansion business case deck) but provides no explicit 'Use when...' trigger clause; the 'when' is only implied via 'for a growing customer' and 'for champion, finance approver', so completeness is capped at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	It uses natural terms an account director would actually say — 'renewal', 'seat-expansion', 'business case', 'B2B sales deck', 'ROI' — giving good coverage of the domain's common phrasing.	3 / 3
Distinctiveness Conflict Risk	The niche is specific and distinct — an Open Design renewal + seat-expansion B2B sales deck for champion/finance approver — with triggers unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 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-cobalt-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.