ant

Structured, enterprise-focused design system emphasizing clarity, consistency, and efficiency for data-dense web applications.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/ant/SKILL.md

Quality

Content

85%

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 instruction-only skill with concrete tokens, a clear authoring workflow, and a QA checklist. Its main weakness is mild redundancy across the philosophy sections that could be tightened for token efficiency.

Suggestions

Consolidate the overlapping philosophy in Mission, Brand, Expected Behavior, and Quality Gates into a single concise section to remove restated phrasing.

Add one short worked example of a generated component guideline to demonstrate the Required Output Structure in practice.

Consider moving the full token tables (color/typography/spacing) into a references file and summarizing only the scale in SKILL.md if the file grows further.

Dimension	Reasoning	Score
Conciseness	The body is lean bullet-style prose with no over-explanation of concepts Claude already knows, but Mission, Brand, Expected Behavior, and Quality Gates restate the same "structured, enterprise, clarity/consistency/efficiency" philosophy, so it could be tightened — matching the 'mostly efficient but could be tightened' anchor rather than the fully lean anchor 3.	2 / 3
Actionability	Concrete tokens (#1677ff, spacing 4/8/12/16/24/32, type scale 12/14/16/20/24/32), named component states (default, hover, focus-visible, active, disabled, loading, error), a Required Output Structure, and a QA checklist give specific, copy-paste-ready guidance — the instruction-only equivalent of the 'fully executable / specific examples' anchor.	3 / 3
Workflow Clarity	The six-step "Guideline Authoring Workflow" is clearly sequenced and closes with a QA checklist that serves as the validation checkpoint; the task is authoring (non-destructive), so the missing-destructive-feedback-loop cap does not apply, reaching the 'clear sequence with explicit validation' anchor.	3 / 3
Progressive Disclosure	The skill is a single self-contained file with well-organized sections and no nested or external references; with no need for bundle files, the well-organized-sections condition for a top progressive-disclosure score is met.	3 / 3
	Total	11 / 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 clearly identifies the design-system domain and its core qualities but never states what the skill actually does or when to invoke it. Adding concrete actions and an explicit 'Use when...' trigger would move it from adequate to strong.

Suggestions

Lead with concrete actions the skill performs, e.g. "Authors, audits, and documents implementation-ready design-system guidelines for Ant."

Add an explicit trigger clause such as "Use when creating or reviewing enterprise UI guidelines, design tokens, or component specs for data-dense web apps."

Include natural trigger variations users would actually say (e.g. "design system", "UI guidelines", "component rules", "design tokens") to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Structured, enterprise-focused design system emphasizing clarity, consistency, and efficiency for data-dense web applications" names the domain and qualities clearly but lists no concrete skill actions (e.g. author, generate, audit), matching the 'names domain and some actions, but not comprehensive' anchor rather than the vague anchor 1 or the multi-action anchor 3.	2 / 3
Completeness	It weakly answers 'what' (describes the design system) but provides no 'when' or 'Use when...' trigger guidance, so per the judging guidelines completeness is capped at 2 rather than reaching the explicit-trigger anchor 3.	2 / 3
Trigger Term Quality	Terms like "design system", "enterprise", and "data-dense" are relevant and natural, but common variations (e.g. UI guidelines, design tokens, component specs) and explicit trigger phrasing are missing, fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The enterprise data-dense niche is fairly specific, yet the description omits "Ant" and could still overlap with other design-system skills, matching the 'somewhat specific but could still overlap' anchor.	2 / 3
	Total	8 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: bergside/awesome-design-skills
Path: skills/ant/SKILL.md
Commit: f631a09

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.