CtrlK
BlogDocsLog inGet started
Tessl Logo

friendly

Approachable, intuitive design with rounded elements, ample whitespace, and soft pastel color palettes.

54

Quality

61%

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/friendly/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 content is a well-structured, concise instruction skill with concrete tokens and a clear authoring workflow. Its main gaps are the absence of a worked example and the lack of inline validation checkpoints in the workflow.

Suggestions

Add one fully worked example (e.g. a sample component rule with anatomy, states, and a QA checklist line) to make the expected output copy-paste ready.

Insert explicit inline validation checkpoints in the authoring workflow (e.g. "verify every rule anchors to a token before proceeding") rather than relying on a separate Quality Gates section.

Dedupe the overlapping guidance in Rules, Component Rule Expectations, Quality Gates, and Example Constraint Language to tighten the content further.

DimensionReasoningScore

Conciseness

The body is lean and sectioned, assumes Claude's competence, and does not explain known concepts; the only mild redundancy is overlap between Rules, Component Rule Expectations, Quality Gates, and Example Constraint Language, which does not rise to verbosity.

3 / 3

Actionability

It provides concrete scaffolding (specific hex tokens, font stack, type scale, WCAG 2.2 AA, required interaction states, output structure) but includes no filled worked example of an actual guideline, leaving the expected artifact modeled only abstractly.

2 / 3

Workflow Clarity

The 6-step Guideline Authoring Workflow is clearly sequenced and references a QA checklist, but validation checkpoints are implicit in a separate Quality Gates section rather than inline feedback loops within the workflow steps.

2 / 3

Progressive Disclosure

The single self-contained SKILL.md is well-organized into clear sections with no nested or dangling external references, which is appropriate for a single-purpose skill needing no bundle files.

3 / 3

Total

10

/

12

Passed

Description

50%

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 a clear, specific aesthetic but omits any action verbs and any "Use when..." trigger guidance. It is descriptive rather than capability-oriented, which limits specificity and completeness.

Suggestions

Add an action verb phrase describing what the skill does, e.g. "Generate friendly design-system guidelines...".

Append a "Use when..." clause naming natural trigger terms (friendly UI, soft/pastel design, rounded corners, approachable interfaces).

Include the brand keyword "friendly" in the description to improve trigger matching and distinctiveness.

DimensionReasoningScore

Specificity

The description names the domain and concrete aesthetic attributes ("rounded elements", "ample whitespace", "soft pastel color palettes") but states no actions/verbs describing what the skill does, so it sits between vague and comprehensive.

2 / 3

Completeness

The "what" is only implied (it describes a design aesthetic rather than an explicit action) and the "when" is entirely missing with no "Use when..." clause, which caps completeness at 2 per the guidelines.

2 / 3

Trigger Term Quality

It includes some natural design terms ("rounded elements", "whitespace", "pastel color palettes", "approachable") a user might say, but misses common variations like "friendly UI", "soft design", or "rounded corners" and has no explicit trigger clause.

2 / 3

Distinctiveness Conflict Risk

The pastel/friendly aesthetic gives it a recognizable niche, but without explicit triggers it could overlap with other soft or rounded design skills, so it is not at the clearly-distinct level.

2 / 3

Total

8

/

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.