CtrlK
BlogDocsLog inGet started
Tessl Logo

lingo

Playful, minimal design with bright colors, rounded shapes, tactile 3D borders, and friendly illustrations for approachable interfaces.

56

Quality

63%

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

Quality

Content

77%

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

The body is highly actionable and clearly sequenced for a guideline-authoring skill, with concrete tokens and a QA checklist. Its main weaknesses are minor inter-section redundancy and the lack of any progressive file structure.

Suggestions

Consolidate the overlapping Rules Do/Don't, Quality Gates, and Example Constraint Language sections to remove redundancy and tighten the body.

Consider splitting the component-level rule expectations and QA checklist into a referenced file (e.g. COMPONENT_RULES.md) to add progressive disclosure structure, or trim the body under 50 lines to qualify for the simple-skill carve-out.

Add an explicit validate-and-retry note in the authoring workflow (e.g. re-check tokens/states against foundations before finalizing the QA checklist) to strengthen the feedback loop.

DimensionReasoningScore

Conciseness

The body is lean and bullet-driven without explaining general concepts Claude knows, but several sections overlap (Rules Do/Don't restated by Quality Gates and Example Constraint Language; Component Rule Expectations echoing the Required Output Structure), so it could be tightened.

2 / 3

Actionability

For an instruction-only skill the guidance is concrete and copy-paste ready: exact token values (hex colors, 4/8/12/16/24/32 spacing, type scale), an explicit state list, a 6-step workflow, and an output structure with 'must/should' language.

3 / 3

Workflow Clarity

The Guideline Authoring Workflow is a clearly sequenced 6-step process anchored by a terminal QA checklist and Quality Gates that serve as validation checkpoints, and the task is non-destructive so no interleaved retry loop is required.

3 / 3

Progressive Disclosure

The single file is well-organized into clear sections, but it is a monolithic ~80-line document above the simple-skill (<50 line) threshold with no references split out, so there is no progressive disclosure structure to reward.

2 / 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 visual style but reads as a descriptor rather than capability-and-trigger guidance, with no "Use when" clause. This leaves every dimension at the mid-anchor.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g. 'Use when applying a Duolingo-inspired playful UI style, or when the user asks for bright, rounded, friendly interface designs').

Lead with the concrete actions the skill performs (e.g. 'Authors and applies Lingo design-system guidelines: tokens, components, states, and accessibility rules').

Include distinctive trigger terms like 'duolingo-style', 'playful UI', or 'look-and-feel' to reduce overlap with generic design skills.

DimensionReasoningScore

Specificity

The description names concrete visual attributes ("bright colors, rounded shapes, tactile 3D borders, friendly illustrations"), but it characterizes a style rather than enumerating the concrete actions the skill performs, so it stops short of the multi-action bar for a 3.

2 / 3

Completeness

It answers what the skill is (a playful minimal design style) but provides no "Use when..." clause or equivalent trigger guidance, which caps completeness at 2 per the rubric.

2 / 3

Trigger Term Quality

Terms like "design", "colors", and "illustrations" are reasonably natural, but common trigger variations a user would actually say (e.g. "duolingo", "look-and-feel", "brand style") are missing, leaving coverage partial.

2 / 3

Distinctiveness Conflict Risk

The design-style framing is somewhat specific, but the generic design vocabulary ("colors", "shapes", "interfaces") could overlap with other design skills, and no distinct trigger separates it.

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.