CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

presentation-styling

Knowledge about CSS classes, component patterns, and syntax highlighting in the presentation

53

Quality

67%

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-styling/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 body is an efficient, highly actionable reference: concrete class definitions, colors, and copy-paste-ready HTML patterns for the common slide types. Its only weaknesses are minor — a duplicated weight-badge note, no explicit ordering/usage workflow, and a flat structure that could benefit from a brief orientation line.

Suggestions

Deduplicate the weight-badge guidance by stating the JS auto-injection rule once and cross-referencing it from the Journey Bar section.

Add a one-line orientation at the top (what slide types these patterns cover and when to combine them) to give the flat catalog a navigation layer.

DimensionReasoningScore

Conciseness

The body is a lean reference: one-line class descriptions (".two-col — 2-column grid layout with 24px gap") and executable HTML snippets with no explanation of concepts Claude already knows. The only trimmable redundancy is the weight-badge JS-injection note repeated in two places (the slide-pattern section and the Journey Bar section), which fits 'efficient; minor instances of over-explanation that could be trimmed' rather than the fully lean anchor 5.

4 / 5

Actionability

The content gives copy-paste-ready HTML for the common cases — a two-column good/bad slide, a trigger-box + code-block slide, and an icon list — plus concrete class semantics, hex colors for syntax spans, and an explicit 'do not hardcode' instruction. This matches 'fully executable; copy-paste ready code or commands; specific examples cover the common cases'.

5 / 5

Workflow Clarity

This is a single-purpose lookup/reference skill with unambiguous application guidance and one explicit behavioral rule (weight badges are JS-injected), and it involves no destructive or batch operations, so no validation cap applies. It sits just above the rubric's under-50-line simple-skill exception (~105 lines) with no explicit sequencing or self-check guidance, so 'clear sequence with most checkpoints present' fits better than a 5.

4 / 5

Progressive Disclosure

Sections (Layout, Content Blocks, Lists, Tags & Badges, Syntax Highlighting, Slide Type Patterns, Journey Bar) are well organized with all content appropriately inline for a single-file reference; no bundle files exist, so nothing is buried or nested. It misses the 5 anchor because the file exceeds the simple-skill threshold and reads as a flat catalog with no overview/navigation layer.

4 / 5

Total

17

/

20

Passed

Description

36%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 names a concrete domain but is a passive noun phrase with no actions, no use-when trigger guidance, and no distinctive hooks. It would rarely be selected for the right moment on its own merits. Adding explicit triggers and action verbs would substantially improve it.

Suggestions

Add an explicit trigger clause, e.g. 'Use when editing or building slides in presentation/index.html, styling slide content, or adding code blocks to the presentation.'

Convert the noun phrase into third-person actions: e.g. 'Styles presentation slides using the CSS component classes and syntax-highlighting spans defined in presentation/index.html.'

Include natural user-facing terms and file references (slide layout, HTML patterns, presentation styling) to improve trigger-term coverage and reduce overlap with generic CSS skills.

DimensionReasoningScore

Specificity

"Knowledge about CSS classes, component patterns, and syntax highlighting" names the domain but contains no concrete actions at all — it is a noun phrase describing what the skill contains, not what it does, matching the anchor 'names the domain but actions are minimal or generic'. Not a 1 because the domain topics are concrete rather than purely abstract; not a 3 because there are no verbs/actions listed.

2 / 5

Completeness

The 'what' is only weakly stated ("Knowledge about..." describes contents, not capability) and the 'when' is entirely absent — no 'Use when...' or equivalent trigger guidance, which per the rubric caps completeness at 3. Fits the anchor 'has a clear what but when is missing' only marginally; the vague what keeps it from a 4 and the presence of a stated domain keeps it above a 2.

3 / 5

Trigger Term Quality

Keywords like "CSS classes", "component patterns", and "syntax highlighting" are relevant to the domain, but natural phrases a user would say (e.g. 'styling slides', 'building the presentation', 'presentation HTML') and their synonyms are missing. Fits 'some relevant keywords but missing common variations or synonyms'; not a 4 because no natural user-facing trigger phrasing is present.

3 / 5

Distinctiveness Conflict Risk

"in the presentation" scopes this to one artifact, which is somewhat specific, but the description gives no unique trigger that would prevent overlap with general CSS or web-styling skills. Matches 'somewhat specific but could still overlap with similar skills'; not a 4 because nothing signals when this skill rather than a generic CSS skill should fire.

3 / 5

Total

11

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

shanraisshan/claude-code-best-practice

Path

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