CtrlK
BlogDocsLog inGet started
Tessl Logo

design

Simplified Aura guidance for selecting primitives, keeping token usage consistent, and applying reliable layout/copy/state patterns in Flows and Fusion apps.

49

Quality

53%

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

Quality

Content

50%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 content is a compact, well-intentioned overview that respects token budget and points to external Aura resources, but it stays at an abstract guidance level without concrete code/token examples, has a few typos, and lacks a true multi-step workflow with validation.

Suggestions

Add a short concrete example (e.g. a semantic token usage do/don't snippet or a primitive selection table) to raise actionability.

Fix typos ('node_modeules' -> 'node_modules', 'Guidlines' -> 'Guidelines') and consolidate the Role and when-to-reference lists to reduce redundancy.

If DESIGN.md is a real bundled reference, confirm it exists and link it as a clearly signaled local file; otherwise remove the dangling path.

DimensionReasoningScore

Conciseness

The body is reasonably lean and avoids re-explaining concepts Claude already knows, but the eight-bullet 'when-to-reference' list and the separate Role list overlap somewhat and could be tightened; typos ('node_modeules', 'Guidlines') suggest it could be cleaner.

2 / 3

Actionability

It gives directive guidance ('Use Aura primitives before custom UI', 'do not hardcode raw values', 'check variants/props first') and concrete pointers (DESIGN.md path, Storybook/docs URLs), but lacks specific code, token names, or concrete examples that would make it copy-paste ready.

2 / 3

Workflow Clarity

The numbered Operating Principles provide a light sequence, but this is a principles-based skill with no real multi-step workflow or validation checkpoints; sequence is present but not a guided procedure.

2 / 3

Progressive Disclosure

Sections are organized and it points to one-level-deep resources (DESIGN.md, Storybook, docs site), but the references are mostly external URLs with no actual bundle files, and the DESIGN.md path is unverifiable rather than a clearly signaled bundled reference.

2 / 3

Total

8

/

12

Passed

Description

57%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 clearly conveys the skill's purpose and is well-scoped to a distinct niche, but it omits an explicit 'Use when...' trigger and relies on somewhat abstract, jargon-leaning action language rather than crisp natural triggers.

Suggestions

Add an explicit trigger clause, e.g. 'Use when building or styling UI in Cognite Flows or Fusion apps with the Aura design system.'

Replace abstract phrasing with concrete actions users would name, such as 'choose components, apply design tokens, and lay out forms, tables, and navigation.'

Include natural user terms like 'design system', 'components', and 'styling' alongside 'primitives' and 'tokens'.

DimensionReasoningScore

Specificity

Names the domain and several action areas ('selecting primitives, keeping token usage consistent, and applying reliable layout/copy/state patterns'), but these are relatively abstract compared to concrete low-level actions, so it does not reach the 'multiple specific concrete actions' anchor.

2 / 3

Completeness

Clearly states what the skill provides (selection/token/layout/copy/state guidance) but lacks any 'Use when...' or equivalent explicit trigger clause, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Contains relevant domain terms ('Aura', 'primitives', 'token usage', 'Flows and Fusion apps') a user may say, but leans on technical jargon and omits common natural variations like 'design system' or 'components'; no explicit trigger phrasing.

2 / 3

Distinctiveness Conflict Risk

Scoped specifically to the Aura design system within Cognite Flows and Fusion apps, giving it a clear niche unlikely to trigger for unrelated skills.

3 / 3

Total

9

/

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
cognitedata/builder-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.