CtrlK
BlogDocsLog inGet started
Tessl Logo

light-mode-paper-technical

Create a light-mode technical design system with warm paper surfaces, dark outer framing, subtle diagonal texture, precise bracketed geometry, and restrained accent signals.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./agent-skills/web-design/light-mode-paper-technical/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is lean, well-structured, and free of redundant explanation, with clear organization that suits a concise single-purpose design skill. Its weaknesses are an empty Workflow header and advisory rather than fully concrete specifications (e.g., no exact color tokens or measurements).

Suggestions

Either populate the '## Workflow' section with a short sequenced set of steps (define surfaces -> apply framing -> add texture -> place accent) or remove the empty header to avoid implying a missing process.

Add a few concrete spec anchors — example hex/tone ranges for paper surfaces, a recommended outer-shell radius, or an accent-color saturation guideline — to move guidance from advisory to executable.

Optionally include one compact before/after or element checklist so the direction translates directly into implementation choices.

DimensionReasoningScore

Conciseness

The body is organized into tight, focused sections with no padding or explanation of concepts Claude already knows; nearly every line delivers concrete design direction that earns its place.

3 / 3

Actionability

Provides concrete directional guidance ('Build the main experience on warm off-white...', 'Wrap the lighter interior inside a darker outer shell') but stays advisory ('should', 'prefer') without executable specifics like exact color values, radii, or ratios, so it is incomplete versus copy-paste-ready.

2 / 3

Workflow Clarity

The '## Workflow' header is empty with no sequenced steps, and the remaining content is organized by topic rather than process; while not a fragile multi-step operation, the missing sequence keeps it below 3.

2 / 3

Progressive Disclosure

The skill is under 50 lines, has no external bundle files, and is well-organized into clearly labeled sections, meeting the simple-skill allowance for a top progressive-disclosure score.

3 / 3

Total

10

/

12

Passed

Description

67%

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 is specific and defines a distinct design niche, but it omits explicit 'when to use' trigger guidance and leans on abstract design vocabulary rather than natural user phrasing. Adding a 'Use when...' clause with concrete trigger terms would raise completeness and trigger-term quality.

Suggestions

Add a 'Use when...' clause naming concrete trigger situations, e.g. 'Use when creating a light-mode technical UI that should feel warm and paper-like rather than a cold enterprise dashboard.'

Include natural user-facing keywords users would actually say (e.g. 'light mode UI', 'paper texture', 'technical dashboard design') alongside the abstract design vocabulary.

Lead with the core action verb and primary deliverable before the attribute list so the capability reads first.

DimensionReasoningScore

Specificity

Lists multiple specific concrete attributes and actions — 'warm paper surfaces', 'dark outer framing', 'subtle diagonal texture', 'precise bracketed geometry', and 'restrained accent signals' — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Clearly answers 'what' but lacks any 'Use when...' clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2 rather than 3.

2 / 3

Trigger Term Quality

Contains some relevant keywords ('light-mode', 'technical design system') but relies on abstract design vocabulary rather than natural terms a user would actually say, and misses common variations; not pure jargon so above 1.

2 / 3

Distinctiveness Conflict Risk

Targets a clear niche (light-mode paper-technical design system) with distinguishing attributes unlikely to trigger for unrelated skills, matching the clear-niche anchor.

3 / 3

Total

10

/

12

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
MengTo/Skills
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.