html-ppt-hermes-cyber-terminal

Open Design + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.

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-hermes-cyber-terminal/SKILL.md

Quality

Content

87%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 highly actionable and well-structured, delegating shared rules to the master skill and concentrating on template-specific, copy-paste-ready guidance. The main gap is the absence of an explicit verification step confirming the deck actually activates after the asset-path rewrite.

Suggestions

Add an explicit verification checkpoint after Recipe A/B, e.g., 'Open index.html and confirm slide navigation works; if base.css/runtime.js 404, recheck the rewritten link/script paths.'

Briefly note how to confirm the .tpl-hermes-cyber-terminal body class and structural classes are intact before replacing demo content.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, delegating generic rules to the master skill and keeping only template-specific guidance; the detailed asset-path explanation earns its tokens because it flags a real 404 gotcha rather than padding with basics Claude already knows.	3 / 3
Actionability	It gives concrete, executable guidance — exact folder paths, file names (index.html, style.css, base.css, animations.css, runtime.js), the .tpl-hermes-cyber-terminal class, and copy-paste-ready Recipe A/B for rewriting link/script tags — matching 'fully executable; copy-paste ready'.	3 / 3
Workflow Clarity	The six-step authoring sequence is clearly ordered, but there is no explicit validation or verification checkpoint (e.g., 'confirm the deck loads / navigation works after copying'), leaving it at 'steps listed but validation gaps' rather than the level-3 checkpoint anchor.	2 / 3
Progressive Disclosure	It is a focused entry point that points one level deep via clearly signaled links to the master skill and full-decks catalog, with generic rules kept in the parent skill, matching 'clear overview with well-signaled one-level-deep references'.	3 / 3
	Total	11 / 12 Passed

Description

50%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 conveys a clear niche and audience but stops short of listing concrete actions or an explicit use-trigger, leaving it at the mid-level on most dimensions. Adding a 'Use when...' clause and more concrete verbs would lift completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when planning a BYOK model-choice session or AI literacy deck') to satisfy the completeness trigger requirement.

Expand concrete actions beyond 'choosing and wiring' to specifics like comparing cost/quality, routing requests, and producing the slide plan.

Include natural user-facing variations such as 'slides', 'model selection', and 'bring-your-own-key' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and a couple of actions ("choosing and wiring your own model, hands-on", "the routing decision") but does not list multiple concrete actions, matching the 'names domain and some actions, but not comprehensive' anchor rather than the multi-action level 3.	2 / 3
Completeness	It states what the skill produces ("decision-grade AI literacy deck") but has no explicit "Use when..." trigger clause, so per the rubric guideline completeness is capped at 2 even though the what is present.	2 / 3
Trigger Term Quality	Relevant terms like "BYOK", "model", and "AI literacy deck" appear, but common natural variations (slides, model selection, bring-your-own-key) are missing, fitting 'some relevant keywords but missing common variations' rather than full coverage.	2 / 3
Distinctiveness Conflict Risk	The BYOK model-choice niche is fairly specific, but as a deck-creation skill it overlaps with the broader html-ppt deck family, matching 'somewhat specific but could still overlap with similar skills' rather than a conflict-free niche.	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-hermes-cyber-terminal/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.