CtrlK
BlogDocsLog inGet started
Tessl Logo

ui-skills

Opinionated, evolving constraints to guide agents when building interfaces

30

Quality

23%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/ui-skills/SKILL.md

The canonical home for this skill is ui-skills in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

22%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 essentially a placeholder that restates the description and links to an external repo, with no concrete guidance, patterns, or workflow. It fails to add anything Claude does not already know from the frontmatter.

Suggestions

Replace the restated prose with concrete, executable guidance or code snippets that embody the constraints (e.g., example component patterns the skill enforces).

Add an explicit multi-step workflow for applying the constraints, including a validation/check step so output can be verified.

Move detailed material into signaled reference files under ./references/ and link them with clear 'See X.md' pointers instead of a single buried repo URL.

DimensionReasoningScore

Conciseness

The body is short and does not over-explain known concepts, but it wastes tokens by restating the same description three times (Overview, When to Use, Instructions) instead of delivering lean, useful content.

3 / 5

Actionability

It provides no concrete code, commands, or specific patterns — only 'This skill provides guidance and patterns for...', describing rather than instructing, which matches the entirely vague/abstract anchor.

1 / 5

Workflow Clarity

There are no steps, sequence, or validation checkpoints; the only actionable element is an external repository link, matching the 'steps missing or incoherent' anchor.

1 / 5

Progressive Disclosure

Sections exist and there is a single one-level external link, but the reference is a buried prose 'see the source repository' link rather than clearly signaled reference files, and no bundle files are provided to offload detail.

3 / 5

Total

8

/

20

Passed

Description

25%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 is generic and circular, restating the skill name without concrete actions, natural trigger terms, or a 'Use when...' clause. It scores uniformly low across specificity, triggers, completeness, and distinctiveness.

Suggestions

Add concrete actions the skill performs, e.g. 'Enforces spacing, color, and typography constraints on generated UI components'.

Append an explicit 'Use when...' clause with natural trigger phrases users would say, e.g. 'Use when building or reviewing UI components, layouts, or design-system adherence'.

Narrow the niche to reduce overlap with generic design skills, e.g. by naming the specific constraint set or framework it targets.

DimensionReasoningScore

Specificity

The description names the UI/interface domain ('building interfaces') but provides only the generic action 'to guide agents' with no concrete capabilities like enforcing spacing, validating color tokens, or applying design systems.

2 / 5

Completeness

It offers only a vague 'what' (constraints to guide agents) and no 'when' trigger clause at all, matching the 'vague what and no when' anchor; not a 1 because a domain is at least named.

2 / 5

Trigger Term Quality

Keywords like 'opinionated, evolving constraints' and 'building interfaces' are technical phrasing rather than natural user utterances; it lacks the natural phrases (e.g., 'design a UI', 'build a component') a user would actually say.

2 / 5

Distinctiveness Conflict Risk

'Building interfaces' is broad and would overlap heavily with general UI/design and component skills, with nothing narrowing it to a distinct niche.

2 / 5

Total

8

/

20

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.