CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

html-ppt-course-module

A first-30-days onboarding module for new hospitality hires — the behaviors, the practice, the checks, and the manager follow-up. Built as a decision-grade professional training deck for new hires, managers.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/_official/examples/html-ppt-course-module/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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.

A well-structured entry-point skill card with genuinely actionable, copy-ready guidance for the most fragile step (rewriting the template's parent-relative asset URLs), and appropriately lean prose. The main gap is the absence of any explicit validation checkpoint in the authoring workflow, and the detailed asset-rewrite recipes arguably belong in a referenced file rather than the entry card.

Suggestions

Add an explicit validation step after the asset rewrite (e.g., "open the deck and confirm keyboard navigation works / the four project-local assets load") so the workflow has a real checkpoint.

Move the Recipe A/B asset-rewrite detail into a reference file (or into the html-ppt master skill) and keep a one-line pointer plus the failure-mode warning in the entry card.

Include a short code snippet showing the correctly rewritten <link>/<script> tags so the fix is copy-paste ready rather than reconstructed from prose.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence ("Replace demo content, not classes", "Speaker notes go inside <aside class=\"notes\">"); step 3's prose explaining the 404 failure mode ("meaning the deck never activates and slide navigation is dead") could be trimmed. It is not a 5 because a few justifying sentences in the asset-rewrite step pad beyond the minimum needed.

4 / 5

Actionability

Concrete, mostly executable guidance: exact copy sources ("design-templates/html-ppt/templates/full-decks/course-module/"), the four asset files with exact source-to-target URL rewrites, and the theme mechanism ("<link id=\"theme-link\"> and let T cycle"). It falls short of 5 because it shows no literal snippet of the rewritten <link>/<script> tags and defers the actual authoring rules to the master skill.

4 / 5

Workflow Clarity

A clear six-step sequence is present (read master skill, copy template, fix assets, theme, replace content, notes), but no explicit validation checkpoint exists (e.g., confirming runtime.js resolves after the rewrite); the 404 explanation is preventive guidance, not a checkpoint. Not 4 because anchor 4 requires most checkpoints present, and validation here is entirely implicit.

3 / 5

Progressive Disclosure

Good entry-point structure: the card stays short and points one level deep to clearly signaled references (../html-ppt/SKILL.md, the full-decks catalog). Not 5 because the detailed Recipe A/B asset-rewrite procedure — operational detail that could live in a reference — is inlined, and the referenced files sit outside this bundle so their content cannot be verified.

4 / 5

Total

15

/

20

Passed

Description

61%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 communicates a concrete, niche deliverable but is framed as a description of the training module rather than of what the skill does, and it omits any explicit usage trigger. Adding an explicit "Use when..." clause and a capability verb would materially improve it.

Suggestions

Rewrite the description with an explicit capability verb, e.g., "Builds a first-30-days onboarding training module for new hospitality hires...", so it states what the skill does rather than what the module is.

Append a "Use when..." clause with concrete triggers (e.g., "Use when the user asks for an onboarding module, orientation deck, or new-hire training for hospitality staff") to satisfy the missing 'when' half.

Include a natural synonym or two ("orientation", "new employee training") to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

It names a concrete domain ("A first-30-days onboarding module for new hospitality hires") and one deliverable action ("Built as a decision-grade professional training deck"), matching anchor 3. Not 4 because no explicit capability verbs (create, design, generate) are stated — it reads largely as a description of the module's subject matter.

3 / 5

Completeness

The "what" is clear (a first-30-days hospitality onboarding training deck covering behaviors, practice, checks, and manager follow-up), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines. Not 4 because the "when" is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Natural phrases are present — "onboarding module", "new hires", "hospitality", "training deck", "manager follow-up" — giving good keyword coverage. Not 5 because common variations users would say ("orientation", "new employee training", "onboarding slides") are missing.

4 / 5

Distinctiveness Conflict Risk

The hospitality new-hire onboarding niche is fairly distinct with specific framing ("first-30-days", "hospitality hires", "manager follow-up"), creating only minor overlap with generic training-deck or workshop skills. Not 5 because "professional training deck" territory overlaps with the sibling html-ppt deck templates.

4 / 5

Total

14

/

20

Passed

Validation

81%

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

CriteriaDescriptionResult

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

plugins/_official/examples/html-ppt-course-module/SKILL.md

Reviewed

Table of Contents

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.