html-ppt-testing-safety-alert

A hospital data-governance briefing: patient-data risk, the control framework, accountability, and the approval the board must give. Built as a decision-grade policy briefing deck for health-system board, regulators.

Quality

61%

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-testing-safety-alert/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 a well-structured, highly actionable entry card with concrete paths, class names, and copy-rewrite recipes. Its main gaps are a missing explicit verification checkpoint after the fragile URL-rewrite step and some tightening room in the recipe explanation.

Suggestions

Add an explicit verification checkpoint after step 3, e.g. 'Open index.html in a browser and confirm slides advance with arrow keys; if base.css/runtime.js 404, re-check the rewritten paths.'

Tighten the Recipe A/B preamble by stating the 404 failure in one line and letting the two recipes carry the detail, cutting the explanatory consequences sentence.

Optionally note that the referenced ../html-ppt paths resolve relative to the installed skill tree so a reader knows where the master skill must live.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and free of concepts Claude already knows, but the Recipe A/B section and the explanatory passage about why parent-relative URLs 'will 404 — meaning the deck never activates and slide navigation is dead' could be tightened without losing the operational point.	2 / 3
Actionability	It gives exact file paths to copy, precise rewrite instructions ('../../../assets/...' to 'assets/fonts.css', 'assets/base.css', 'assets/animations/animations.css', 'assets/runtime.js'), concrete class names ('.tpl-testing-safety-alert'), and the exact notes element ('<aside class="notes">'), all copy-paste ready.	3 / 3
Workflow Clarity	Authoring is laid out as a clear numbered sequence (steps 1-6 with two recipes in step 3), but there is no explicit validation/verification checkpoint (e.g. 'open index.html and confirm slides advance') even though step 3 exists precisely to prevent a silent failure mode.	2 / 3
Progressive Disclosure	It is a focused entry-point card that defers detail to clearly signaled, one-level-deep references (the master ../html-ppt/SKILL.md, the full-decks catalog, the template folder, themes/*.css), and its sections are well organized for navigation; no bundle files ship with this skill, which matches its role as a pointer card.	3 / 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 conveys a clear, domain-specific subject but describes deck content rather than the skill's actions and omits any explicit 'when to use' trigger guidance. It reads as a content brief rather than a capability + trigger statement.

Suggestions

Lead with the skill's concrete action (e.g. 'Generates an HTML decision-grade policy briefing deck for a health-system board') before describing the deck's subject matter.

Add an explicit 'Use when...' clause with natural trigger terms users would say ('board briefing', 'data-governance slides', 'compliance deck for regulators').

Differentiate from sibling policy-deck skills by naming the testing-safety-alert visual template as the distinguishing trigger.

Dimension	Reasoning	Score
Specificity	It names the domain ('hospital data-governance briefing') and several content elements ('patient-data risk, the control framework, accountability, and the approval'), but these are deck topics rather than concrete actions the skill performs; the only skill-action cue is the vague 'Built as a decision-grade policy briefing deck'.	2 / 3
Completeness	The 'what' is present (a decision-grade policy briefing deck), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Some relevant natural terms appear ('data-governance', 'policy briefing deck', 'health-system board', 'regulators'), but common variations a user would actually say ('slides', 'presentation', 'board deck', 'compliance briefing') are missing.	2 / 3
Distinctiveness Conflict Risk	The hospital data-governance niche is fairly specific, but the description shares the 'policy-briefing-deck' framing with sibling skills in the same family and lacks distinct in-description triggers, so overlap remains possible.	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: 3 suspicious	Warning
referenced_paths_exist	Referenced path issues: 5 missing, 2 deeper-than-1-level	Warning

	Total	13 / 16 Passed

Repository: nexu-io/open-design
Path: design-templates/html-ppt-testing-safety-alert/SKILL.md
Commit: f2760fd

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