html-ppt-zhangzara-retro-windows

An IT security-awareness training on spotting phishing — the tells, the drill, and what to do in the first 60 seconds. Built as a decision-grade professional training deck for all employees.

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

72%

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 appropriately scoped as a single self-contained deck template. It loses points only on actionability (instructional rather than executable) and workflow clarity (no explicit validation checkpoint).

Suggestions

Add a brief validation or verification checkpoint in the workflow, e.g. a step to confirm the deck's navigation runtime and artifact tags are intact before emitting.

Include one small executable snippet (e.g. the exact <artifact> wrapper or a minimal example.html shell) to lift actionability toward copy-paste ready.

Clarify the 'duplicate an existing slide' step with how page-number labels and navigation state should be reconciled afterward.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient, assumes Claude's competence, and never explains concepts Claude already knows; every section earns its place.	3 / 3
Actionability	It gives concrete directives (clone example.html, replace placeholders, preserve the design system, emit between <artifact> tags), but as an instruction-only skill there is no executable code and several steps remain directional rather than copy-paste ready.	2 / 3
Workflow Clarity	The six numbered workflow steps are clearly sequenced, but there is no explicit validation or verification checkpoint for the batch/layout-duplication operations, which the guideline caps at 2.	2 / 3
Progressive Disclosure	The skill is a single self-contained file with well-organized sections and only one-level-deep references (./LICENSE, example.html), and no deeper nested references exist.	3 / 3
	Total	10 / 12 Passed

Description

35%

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, specific subject matter but omits any explicit usage trigger guidance and lacks natural user-facing keywords in the description text itself. It is a 'what' without a 'when', which caps both completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger terms a user would actually say, e.g. phishing, security-awareness training, onboarding deck.

Fold one or two concrete trigger phrases into the description field itself rather than relying solely on the separate triggers list.

Expand the action list beyond 'the tells, the drill, and the first 60 seconds' to name a few more discrete deliverables for fuller specificity.

Dimension	Reasoning	Score
Specificity	It names the domain (IT security-awareness training on spotting phishing) and several actions ('the tells, the drill, and what to do in the first 60 seconds'), but it is not a comprehensive list of multiple distinct concrete actions like the score-3 anchor.	2 / 3
Completeness	It clearly answers 'what does this do' but lacks an explicit 'Use when...' / 'when should Claude use it' clause, which the guideline caps at 2.	2 / 3
Trigger Term Quality	The description contains no natural trigger keywords a user would say; the recognizable terms ('phishing', 'security-awareness training') appear only in the separate triggers field, not in the description itself.	1 / 3
Distinctiveness Conflict Risk	The phishing-security-awareness-training niche is fairly specific, but the description alone has no explicit triggers, so it could still overlap with other training/presentation skills.	2 / 3
	Total	7 / 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-retro-windows/SKILL.md
Commit: f2760fd

Reviewed: 1 day 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.