html-ppt

For consulting delivery work: turn diagnosis, frameworks, and project work into a client-adoptable action plan. Built around the core query "consulting-final-deck", with engagement manager judgment, buyer-ready proof, and this outcome: accept the recommendation and commit owners to the roadmap.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Failed to scan

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./design-templates/html-ppt/SKILL.md

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-organized, highly actionable overview that pushes detail into verified reference files with clear navigation; its main weaknesses are mild verbosity in long enumerations and a missing explicit validation checkpoint in the render workflow.

Suggestions

Collapse the long inline theme/animation name enumerations into a pointer to references/themes.md and references/animations.md to reduce token load while keeping discoverability.

Add an explicit validation step to the render workflow (verify expected slide count, surface Playwright errors and stop) since multi-slide capture is a batch operation.

Move the detailed presenter-mode card descriptions into references/presenter-mode.md and keep only the trigger keywords and S-key summary in SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is dense but mostly purposeful cataloging of themes/layouts/animations with terse scannable bullets and avoids teaching concepts Claude already knows; the long inline theme/animation enumerations and presenter-mode detail add some bulk that could be trimmed.	4 / 5
Actionability	It provides fully executable, copy-paste-ready guidance: concrete scaffold/render shell commands, exact HTML snippets (link tags, data-anim/data-fx attributes, aside.notes), keyboard shortcuts, and file paths covering the common cases.	5 / 5
Workflow Clarity	Quick start gives a clear numbered sequence (scaffold, theme, layouts, animations, full-deck, render) and the infer-first section adds a decision sequence, but the multi-slide render path lacks an explicit validate/retry checkpoint despite being a batch operation.	4 / 5
Progressive Disclosure	SKILL.md is a concise overview with well-signaled one-level-deep references to real, verified files in references/ (themes, layouts, animations, full-decks, presenter-mode, authoring-guide) and assets/scripts; content is appropriately split and easy to navigate.	5 / 5
	Total	18 / 20 Passed

Description

53%Weight 40%Scale 1-5

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 and outcome-oriented but written in consulting-internal jargon rather than natural user trigger phrases, and it lacks an explicit 'Use when...' clause, capping completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause naming concrete user requests (e.g. 'Use when the user asks for a client-ready consulting deck, a final delivery slide, or a recommendation roadmap').

Replace consulting-internal terms ('engagement manager judgment', 'buyer-ready proof') with phrases users actually say ('client deck', 'consulting slides', 'final deliverable').

Enumerate 2-3 more concrete actions beyond 'turn diagnosis into an action plan' (e.g. structure the storyline, build the recommendation, assign roadmap owners) to lift specificity.

Dimension	Reasoning	Score
Specificity	The description names the domain (consulting delivery) and the concrete action of turning diagnosis/frameworks into an action plan plus a named core query, but does not enumerate multiple specific concrete actions; it sits at the 'domain + 1-2 actions' level rather than comprehensive coverage.	3 / 5
Completeness	It gives a clear 'what' (turn diagnosis into a client-adoptable action plan) and an outcome, but the 'when to use' guidance is only weakly implied via the core-query name instead of an explicit 'Use when...' clause, which the rubric caps at 3.	3 / 5
Trigger Term Quality	It surfaces relevant terms (consulting-final-deck, engagement manager, buyer-ready proof) but these are domain-internal jargon rather than the natural phrases a user would actually say; common synonyms users might utter are largely absent.	3 / 5
Distinctiveness Conflict Risk	The niche is fairly specific (consulting delivery decks tied to a named core query), giving a distinct trigger footprint with only minor overlap risk against generic presentation or strategy skills.	4 / 5
	Total	13 / 20 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
referenced_paths_exist	Referenced path issues: 3 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: nexu-io/open-design
Path: design-templates/html-ppt/SKILL.md
Commit: 1a7a23d

Reviewed: about 5 hours 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.