html-ppt-zhangzara-daisy-days

A customer-success workshop onboarding users to a project-management app — the first-value path and the habits that retain. Built as a decision-grade professional training deck for new customers, CS team.

Quality

57%

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-daisy-days/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 and clearly structured with a concrete workflow and output contract, but it is undermined by referencing bundle files (example.html, LICENSE, template.json, assets/) that are absent and by lacking any validation checkpoint in the workflow.

Suggestions

Ship the referenced bundle files (example.html, template.json, LICENSE, and the assets/ runtime) so the workflow's file references resolve, or remove references to files that are not bundled.

Add a validation/verification checkpoint to the workflow (e.g. open the generated deck and confirm slides render and navigation works) to reach workflow clarity 3.

Fold the frontmatter's critic-pass rubric ('can a learner perform the target task the next day') into the body as an explicit final review step.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-organized with no padding or explanation of concepts Claude already knows — every section (At a glance, Best for, Avoid for, Workflow, Output contract, Source & license) earns its place, matching the 'lean and efficient; every token earns its place' anchor.	3 / 3
Actionability	The workflow gives concrete operational steps (clone example.html, replace placeholders, duplicate layouts, keep the deck-stage.js runtime) and a copy-paste-ready <artifact> output contract, but several referenced files (example.html, assets/deck-stage.js, LICENSE, template.json) are not present in the bundle, leaving the guidance incomplete and not fully copy-paste ready.	2 / 3
Workflow Clarity	A clear six-step numbered sequence is present, but there are no validation or verification checkpoints (e.g. 'confirm the deck renders' or the critic pass mentioned in the frontmatter), so the sequence lacks the explicit checkpoints that anchor 3 requires.	2 / 3
Progressive Disclosure	Sections are well-organized and the body is appropriately short, but it signals one-level-deep references (./LICENSE, template.json, example.html, assets/deck-stage.js) that do not exist in the bundle, so the signaled navigation points to nothing and cannot reach the 'clear overview with well-signaled real references' anchor.	2 / 3
	Total	9 / 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 clearly identifies the deck's subject and audience but reads more like a content brief than a skill description: it lists no concrete skill actions and omits any 'Use when...' trigger guidance. It is distinguishable but not trigger-ready.

Suggestions

Add an explicit 'Use when...' clause naming the natural trigger phrases (e.g. onboarding deck, customer training slides, CS workshop) so completeness can reach 3.

Reframe the description around concrete actions the skill performs (e.g. 'Builds a self-contained HTML onboarding deck by cloning a template, replacing placeholders, and preserving the design system') rather than describing the deck's subject.

Include common keyword variations users would actually say (onboarding slides, training deck, customer-success workshop, CS enablement) to strengthen trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names a concrete domain ('customer-success workshop onboarding users to a project-management app') and framing like 'first-value path and the habits that retain', but describes the deck's subject rather than listing concrete actions the skill performs, so it stops at the 'names domain and some actions' anchor rather than the multi-action level 3.	2 / 3
Completeness	It states what the skill produces (an onboarding workshop deck) but provides no 'when should Claude use it' guidance at all — not even implied — which the rubric caps at 2 for a missing Use-when clause.	2 / 3
Trigger Term Quality	Includes some natural terms a user might say ('customer-success workshop', 'onboarding', 'project-management app', 'training deck', 'CS team') but lacks an explicit trigger clause and common variations, matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The niche (an HTML deck template tuned for customer-onboarding training content) is reasonably specific and unlikely to conflict broadly, but the description reads as a content brief rather than carving a distinct trigger niche, so it sits at 'somewhat specific but could overlap'.	2 / 3
	Total	8 / 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-daisy-days/SKILL.md
Commit: f2760fd

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