CtrlK
BlogDocsLog inGet started
Tessl Logo

bold

Strong visual presence with heavyweight typography, high-contrast colors, and commanding layouts.

55

Quality

62%

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

Quality

Content

85%

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

The content is a concise, well-structured instruction set with a clear authoring workflow and validation gates; its main limitation is that guidance is structural rather than executable. It is appropriate for an instruction-only design-system skill.

Suggestions

Add at least one concrete worked example (e.g. a sample component rule with anatomy, states, and token usage) to move guidance from structural to copy-paste ready.

Include a short illustrative token-usage snippet showing semantic tokens applied to a component to strengthen actionability.

Optionally show a one-line "good vs prohibited" implementation contrast to make the do/don't rules executable in review.

DimensionReasoningScore

Conciseness

The body is lean and token-efficient, avoiding re-explanation of concepts Claude already knows; every section (tokens, rules, workflow, quality gates) earns its place.

3 / 3

Actionability

Concrete tokens (hex values, spacing scale, enumerated required states) make the guidance specific, but it remains structural rather than copy-paste ready; as an instruction-only skill the absence of code is acceptable yet guidance is not fully executable.

2 / 3

Workflow Clarity

A 6-step Guideline Authoring Workflow with explicit validation checkpoints (Quality Gates, a QA checklist "executed in code review") gives a clear sequenced process with feedback loops.

3 / 3

Progressive Disclosure

The body is a self-contained overview organized into clear, well-signaled sections with no need for external references (none provided), satisfying the simple/well-organized skill allowance for a top score.

3 / 3

Total

11

/

12

Passed

Description

40%

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 conveys the Bold system's visual character clearly but reads as a descriptor rather than a capability statement, omitting any explicit "Use when" trigger. It is specific to a niche yet would benefit from concrete actions and trigger terms.

Suggestions

Rewrite as third-person capability actions, e.g. "Author implementation-ready Bold design-system guidance with heavyweight typography, high-contrast color tokens, and commanding layouts."

Add an explicit trigger clause such as "Use when creating or reviewing UI guidance, component specs, or design tokens for the Bold visual style."

Include natural user-facing keywords (e.g. "bold design system", "high-contrast UI", "design tokens", "component guidelines") to improve trigger coverage.

DimensionReasoningScore

Specificity

The description lists visual attributes ("heavyweight typography, high-contrast colors, commanding layouts") rather than concrete actions or capabilities, fitting the vague/abstract anchor.

1 / 3

Completeness

It states what the system looks like but provides no explicit "when to use" trigger guidance, so per the rubric a missing Use-when clause caps completeness at 2.

2 / 3

Trigger Term Quality

Terms like "heavyweight typography" and "high-contrast colors" are somewhat natural design vocabulary, but coverage is thin and missing common variations or a "Use when" cluster.

2 / 3

Distinctiveness Conflict Risk

"Bold" names a fairly specific design-system niche, making it unlikely to trigger for unrelated skills, but the description lacks explicit triggers that fully distinguish it from sibling style skills.

2 / 3

Total

7

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
bergside/awesome-design-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.