CtrlK
BlogDocsLog inGet started
Tessl Logo

presentation-structure

Knowledge about the presentation slide format, weight system, navigation, and section structure

47

Quality

48%

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 ./.claude/skills/presentation/presentation-structure/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.

The content is concise, concrete, and well-structured, giving actionable guidance for editing and renumbering the deck. Its main weakness is the renumbering workflow, which is a batch operation with only a weak verification checkpoint and no error-recovery loop.

Suggestions

Strengthen the renumbering workflow with an explicit validation checkpoint and retry loop, e.g. after renumbering, run a check ("gaps/duplicates") and only proceed once clean — this would lift workflow_clarity above 3.

Add a brief "common mistakes" note for the level-badge injection (it is currently repeated across two sections), consolidating it to remove redundancy.

Show the actual JS contract for goToSlide/totalSlides (or point to where it lives) so navigation edits are fully executable rather than named by reference.

DimensionReasoningScore

Conciseness

The body is dense and well-organized — slide format, level system, navigation, and renumbering rules are laid out with code and a compact table, with only minor redundancy (the level-badge injection note is stated twice).

4 / 5

Actionability

Concrete HTML examples, attribute names, the level-to-bar-percentage mapping, and an explicit renumbering checklist give mostly executable guidance; the few JS hooks (goToSlide, totalSlides) are named but not shown as code.

4 / 5

Workflow Clarity

The Renumbering Rules section lists a clear 4-step sequence but the renumbering/editing operation is a batch change to many slides and the only validation is "Verify no gaps or duplicates exist" — a weak checkpoint with no error-recovery loop, so it sits at 3.

3 / 5

Progressive Disclosure

For a sub-50-line skill with no bundle files, the body is well structured into labeled sections with code examples and a table; there is nothing to push to a separate file, so this is good organization with only minor gaps.

4 / 5

Total

15

/

20

Passed

Description

28%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 identifies the domain but describes knowledge rather than actions and omits any explicit "when to use" trigger. It is distinct but generic in trigger phrasing.

Suggestions

Rewrite as concrete actions, e.g. "Edits and renumbers slides, sets journey-bar levels, and fixes navigation links in the presentation/index.html deck."

Add an explicit trigger clause: "Use when adding, removing, reordering, or re-leveling slides in this presentation."

Include natural user-facing terms like "slide", "section divider", "journey bar", and "renumber" so the skill triggers on how users actually phrase the request.

DimensionReasoningScore

Specificity

Names the domain ("presentation slide format, weight system, navigation, and section structure") but lists no concrete actions — it describes what the skill knows rather than what it does, matching the score-2 anchor where the domain is named but actions are minimal.

2 / 5

Completeness

It states a vague "what" (knowledge of the structure) and entirely omits "when to use it" — no "Use when..." clause and only an implicit, unstated trigger, which the guidelines cap at 3 and the absence places at 2.

2 / 5

Trigger Term Quality

Terms like "presentation" and "slide" are relevant but generic; no natural phrases a user would say (e.g. "edit slides", "add a section", "presentation weight") and no synonyms or file references beyond the generic noun.

2 / 5

Distinctiveness Conflict Risk

Scoping to a single-file HTML presentation structure is a fairly distinct niche with low overlap risk, but the description does not signal the trigger clearly enough to fully separate it from generic presentation skills.

3 / 5

Total

9

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
shanraisshan/claude-code-best-practice
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.