CtrlK
BlogDocsLog inGet started
Tessl Logo

design-system

Guide for using Sentry's layout and text primitives. Use when implementing UI components, layouts, or typography. Enforces use of core components over styled components.

64

Quality

78%

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

Quality

Content

82%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.

A well-structured, highly actionable reference with executable examples and clearly signaled one-level-deep pointers to implementation files. Minor conciseness gains are available from de-duplicating repeated anti-pattern examples.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: prop tables and concise ✅/❌ examples earn their tokens, though the styled-component anti-pattern and the 'Plus ALL Container props' note repeat across several sections and could be trimmed, keeping it just below the 5-anchor.

4 / 5

Actionability

Fully executable TSX snippets with imports, concrete prop values, and ✅/❌ contrasts that cover the common cases, matching the 'copy-paste ready, specific examples cover common cases' anchor.

5 / 5

Workflow Clarity

The 'Creating Thin Abstractions' section is a clearly sequenced 4-step process with an explicit checkpoint ('Wait for explicit approval') and the Quick Reference Checklist serves as verification; it is not a destructive/batch operation so the validation cap does not apply, but there is no error-recovery feedback loop to reach 5.

4 / 5

Progressive Disclosure

Well-organized sections with complete prop lists deferred to clearly-signaled, one-level-deep implementation files (e.g. 'see container.tsx for complete list') and no nested references; no bundle files are provided to score against, and a moderate amount of inline reference bulk keeps it just short of the 5-anchor.

4 / 5

Total

17

/

20

Passed

Description

73%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.

A concise, third-person description that clearly states what it covers and when to use it, with a distinct Sentry-specific niche. It is held back only by limited enumeration of concrete capabilities.

Suggestions

List a few more concrete actions (e.g. 'build flex/grid/stack layouts, apply typography, add tooltips') to raise specificity from 3 toward 4-5.

Tighten the 'what' clause from 'Guide for using' to a more concrete verb phrase like 'Build UI with Sentry's layout and text primitives' to strengthen completeness.

DimensionReasoningScore

Specificity

Names the domain ('layout and text primitives') and a couple of behaviors ('implementing UI components', 'Enforces use of core components over styled components'), but does not enumerate multiple concrete actions, so it sits at the 'domain + 1-2 actions, not comprehensive' anchor rather than the 4-anchor's 'several specific actions'.

3 / 5

Completeness

Provides a clear 'what' ('Guide for using Sentry's layout and text primitives') and an explicit 'when' with concrete trigger phrases ('Use when implementing UI components, layouts, or typography'), but the 'what' is slightly generic so it does not reach the fully concrete 5-anchor.

4 / 5

Trigger Term Quality

Includes natural developer phrasing ('UI components, layouts, typography', 'styled components') users would actually say, with only a few synonyms (e.g. 'CSS', 'styling') missing, matching the 'good keyword coverage' anchor.

4 / 5

Distinctiveness Conflict Risk

Targets a specific Sentry design-system niche with distinct triggers and minimal overlap with other skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.

5 / 5

Total

16

/

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

skill_md_line_count

SKILL.md is long (627 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
getsentry/sentry
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.