CtrlK
BlogDocsLog inGet started
Tessl Logo

presentation-styling

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

57

Quality

65%

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, actionable reference with copy-paste HTML examples and clear section organization, requiring no external bundle files. Minor gains are possible by deduplicating the .code-block description and optionally splitting the longer pattern examples into a reference file.

DimensionReasoningScore

Conciseness

The body is a lean, reference-style catalog with terse bullet descriptions and code blocks and no padding about what CSS/HTML is, though a few items (e.g. .code-block) are described twice across sections and could be tightened.

4 / 5

Actionability

Copy-paste-ready HTML examples for each slide-type pattern, syntax-highlighting spans, and the icon-list pattern concretely cover the common cases a user would build.

5 / 5

Workflow Clarity

For a single-purpose styling reference the patterns are clearly organized and unambiguous, but there is no explicit sequencing or validation checkpoint because there is no multi-step or destructive workflow to gate.

4 / 5

Progressive Disclosure

Content is well organized under clear section headers in one file with no external bundle files needed, though at ~107 lines some pattern examples could optionally be split into a reference file.

4 / 5

Total

17

/

20

Passed

Description

48%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 a concrete, fairly distinctive niche but is framed as passive "Knowledge about" rather than actions and omits any "Use when…" trigger guidance, which caps completeness. Adding verbs and an explicit trigger clause would lift specificity and completeness.

Suggestions

Rewrite as actions, e.g. "Apply CSS classes and component patterns…" instead of "Knowledge about…", to give the description concrete capabilities.

Add a "Use when…" clause naming natural triggers, e.g. "Use when editing presentation/index.html slides or adding styled content blocks."

Include user-natural synonyms such as "slides", "badges", and "callout boxes" alongside the technical class names.

DimensionReasoningScore

Specificity

The phrase "Knowledge about CSS classes, component patterns, and syntax highlighting" names a concrete domain but contains no action verbs at all, so actions are effectively absent rather than just minimal.

2 / 5

Completeness

It states a clear "what" (knowledge about presentation styling primitives) but has no "when should Claude use it" clause; the rubric caps completeness at 3 when explicit trigger guidance is absent.

3 / 5

Trigger Term Quality

"CSS classes", "component patterns", "syntax highlighting", and "presentation" are relevant, mostly natural terms, but common synonyms and a "Use when…" trigger phrasing are missing.

3 / 5

Distinctiveness Conflict Risk

Scoping to "in the presentation" plus specific primitives (slide classes, weight badges, journey bar) gives it a clear niche with only minor overlap risk against generic CSS/web skills.

4 / 5

Total

12

/

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.