Name: core-components
Rating: 59.2 (1 reviews)
Author: administrakt0r

core-components

Core component library and design system patterns. Use when building UI, using design tokens, or working with the component library.

Quality

69%

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

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

Quality

Content

72%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 a highly actionable, code-dense reference with excellent copy-paste examples and token tables. Its weaknesses are the absence of any multi-step workflow and the lack of progressive disclosure — everything lives in one ~270-line file with no external references.

Suggestions

Move the full token tables (spacing, color, typography) and the per-component prop reference into separate files under references/ (e.g. TOKENS.md, COMPONENTS.md) and link to them from SKILL.md, keeping only a quick-start overview inline.

Delete the generic 'When to Use: This skill is applicable to execute the workflow or actions described in the overview.' line — it adds no information.

If a usage workflow is intended (e.g. choose component -> apply tokens -> verify against anti-patterns), add it as a short numbered checklist so the skill has an explicit sequence.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean tables and executable code that assume Claude's competence; only minor filler ('When to Use: This skill is applicable to execute the workflow or actions described in the overview.') and some repeated anti-patterns keep it below the top anchor.	4 / 5
Actionability	Copy-paste-ready TSX snippets for each component (Box, HStack, Text, Button, Input, Card) plus concrete token tables cover the common cases fully, matching the 'specific examples cover the common cases' anchor.	5 / 5
Workflow Clarity	This is a reference/patterns catalog rather than a multi-step procedure, so there is no sequence or validation checkpoints to evaluate; no destructive/batch operations trigger the cap, but there is also no workflow to reward, placing it at the middle anchor.	3 / 5
Progressive Disclosure	Section headers and tables give good structure, but ~270 lines inlining full token catalogs and a component API reference — with no bundle files in references/scripts/assets and no pointers to separate files — means content that could be split stays inline.	3 / 5
	Total	15 / 20 Passed

Description

66%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 clearly states both purpose and triggers in third person, with natural keywords. Its main weakness is a generic noun-phrase 'what' and some overlap risk with adjacent UI/design-system skills.

Suggestions

Replace the noun-phrase 'what' with concrete verbs, e.g. 'Compose UI from core components, apply design tokens instead of hard-coded values, and follow layout patterns.'

Sharpen the trigger to reduce overlap, e.g. 'Use when building UI with the core component library or applying design tokens — not for raw platform components.'

Add a synonym users might say, such as 'theme tokens' or 'design system', to broaden natural-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Core component library and design system patterns') and a couple of actions ('building UI, using design tokens'), but the 'what' is a noun phrase rather than a comprehensive list of concrete actions, so it sits at the anchor rather than above.	3 / 5
Completeness	Explicitly answers both what ('Core component library and design system patterns') and when ('Use when building UI, using design tokens, or working with the component library'), but the 'what' is slightly generic so it does not fully reach the top anchor.	4 / 5
Trigger Term Quality	Includes natural phrases users would say — 'building UI', 'design tokens', 'component library' — giving good keyword coverage, though a few synonyms or variations are missing.	4 / 5
Distinctiveness Conflict Risk	The design-token / component-library niche is somewhat specific, but the body itself references a sibling 'react-ui-patterns' skill, signaling real overlap risk with closely related UI skills.	3 / 5
	Total	14 / 20 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
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
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/core-components/SKILL.md
Commit: 57c135b

Reviewed: 3 days 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.