CtrlK
BlogDocsLog inGet started
Tessl Logo

normalize

Normalize design to match your design system and ensure consistency

74

1.00x
Quality

61%

Does it follow best practices?

Impact

98%

1.00x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./archived/legacy-companion/.agents/skills/normalize/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%Weight 40%Scale 1-3

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

The body is a well-structured, actionable guide with clean sectioning, but it would benefit from explicit mid-workflow validation checkpoints and trimming the closing fluff.

Suggestions

Add an explicit validation feedback loop in Execute, e.g. after normalizing each dimension, run lint/type-check and fix regressions before moving on.

Remove the closing motivational paragraph ('You are a brilliant frontend designer... world class.') to improve token efficiency.

Insert a verification checkpoint between Execute and Clean Up (e.g. 'Before cleanup, confirm the feature visually matches design-system examples and passes type-checking').

DimensionReasoningScore

Conciseness

The body is mostly efficient with well-organized checklists, but the closing motivational paragraph ('You are a brilliant frontend designer...') is unnecessary padding that could be trimmed.

2 / 3

Actionability

Provides concrete, specific directives per dimension (e.g. 'Replace hard-coded values with typographic tokens', 'grep for "design system"') that are directly actionable for an instruction-only skill.

3 / 3

Workflow Clarity

Plan/Execute/Clean Up is sequenced, but destructive redesign work has no explicit validate→fix→retry feedback loop during execution, capping workflow clarity at 2 per the rubric scoring notes.

2 / 3

Progressive Disclosure

A single, well-organized SKILL.md with clearly labeled Plan/Execute/Clean Up sections and no nested references; appropriate for a self-contained instruction skill.

3 / 3

Total

10

/

12

Passed

Description

50%Weight 40%Scale 1-3

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 skill's purpose concisely but stops at one general action and omits any explicit trigger guidance, leaving every dimension at the midpoint.

Suggestions

Add concrete actions, e.g. 'Replace hard-coded values with design tokens, swap custom components for design-system equivalents, and align spacing, color, and typography.'

Append a 'Use when...' clause with natural triggers, e.g. 'Use when the user asks to normalize a feature, match the design system, fix UI inconsistencies, or align components to design tokens.'

Include more user-natural trigger terms such as 'redesign', 'UI consistency', 'design tokens', and 'component library' to improve trigger term coverage and distinctiveness.

DimensionReasoningScore

Specificity

Names the domain ('design system') and one general action ('normalize design') but does not list multiple specific concrete actions like the anchor-3 example does.

2 / 3

Completeness

States what the skill does ('Normalize design to match your design system and ensure consistency') but lacks any explicit 'Use when...' trigger clause, capping completeness at 2 per the rubric guideline.

2 / 3

Trigger Term Quality

Includes relevant keywords ('design system', 'consistency') a user might say, but misses common variations such as 'redesign', 'UI', 'components', or 'styles'.

2 / 3

Distinctiveness Conflict Risk

The design-system normalization niche is somewhat specific, but the trigger terms could still overlap with general design or redesign skills.

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
The-Vibe-Company/companion
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.