CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

extract

Extract and consolidate reusable components, design tokens, and patterns into your design system. Identifies opportunities for systematic reuse and enriches your component library. Use when the user asks to create components, refactor repeated UI patterns, build a design system, or extract tokens.

Quality

77%

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 ./templates/skills/impeccable/extract/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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-organized, concise process skill with a clear phase sequence and sensible judgment heuristics. Its main gaps are executability — no concrete examples of token naming, component scaffolds, or migration commands — and vague validation for the batch migration phase where feedback loops matter most.

Suggestions

Add a small executable example for the core artifacts: a sample design-token file with primitive vs. semantic naming, and a minimal component scaffold showing the expected props/types/documentation format.

Make the Migrate validation actionable: specify how to verify parity (e.g. search for remaining old implementations, visually compare before/after, run existing tests) before deleting dead code, and loop back on failures.

Move detail such as component quality checklists and token-organization guidance into a one-level-deep references file (e.g. references/authoring.md) linked from the relevant section to keep SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

The body is efficient — tight bullet lists, no explanation of concepts Claude already knows, concrete heuristics like "Is this used 3+ times?" — with only minor trimmable padding: the opening line restates the description and the closing "Remember: A good design system is a living system..." sentence is motivational filler, keeping it below anchor 5.

4 / 5

Actionability

There is some concrete guidance ("grep for 'design system', 'ui', 'components'", the "3+ times" reuse threshold, the ask-before-creating checkpoint), but the core extraction work lacks executable specifics: no example token naming scheme, no component/prop scaffold, no documentation or migration command patterns — key details are missing, matching anchor 3 rather than anchor 4's mostly-executable guidance.

3 / 5

Workflow Clarity

The five phases (Discover → Plan → Extract & Enrich → Migrate → Document) are clearly sequenced with a decision checkpoint, but the Migrate phase performs batch replacement and dead-code deletion with only the implicit, method-less validation "Test thoroughly: Ensure visual and functional parity" — under the batch/destructive validation guidance this caps the score at 3.

3 / 5

Progressive Disclosure

The body has good section structure with no bundle files and no dangling references, and all content is appropriately inline for a process skill; however, at ~84 lines with detail (component authoring standards, token naming, migration mechanics) that could live in one-level-deep reference files, it sits at anchor 4 rather than anchor 5's well-signaled split.

4 / 5

Total

14

/

20

Passed

Description

83%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 strong description that clearly and explicitly states both what the skill does and when to use it, with mostly natural trigger phrases. Its weaknesses are minor: action phrasing is slightly process-abstract and trigger coverage omits a few common synonyms like "component library".

Suggestions

Add natural synonyms to the trigger clause, e.g. "...or when the user mentions a component library, shared UI components, or design tokens".

Make the action phrasing slightly more concrete, e.g. naming the artifacts produced (component files, token files, documentation entries) rather than "identifies opportunities for systematic reuse".

DimensionReasoningScore

Specificity

Lists several specific actions — "Extract and consolidate reusable components, design tokens, and patterns", "Identifies opportunities for systematic reuse", "enriches your component library" — though they are process-level rather than fully concrete deliverables, which keeps it just below the comprehensive anchor 5.

4 / 5

Completeness

Explicitly answers both questions: the "what" is concrete ("Extract and consolidate reusable components, design tokens, and patterns into your design system") and the "when" is an explicit "Use when the user asks to create components, refactor repeated UI patterns, build a design system, or extract tokens" with concrete trigger phrases, matching anchor 5.

5 / 5

Trigger Term Quality

The "Use when" clause covers natural phrases users would say — "create components", "refactor repeated UI patterns", "build a design system", "extract tokens" — but misses common synonyms such as "component library", "shared components", or "design tokens" as explicit triggers, so it falls short of anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Design-system extraction is a clear niche with distinct triggers ("build a design system", "extract tokens"), but "create components" is broad enough to overlap with general frontend/component-creation skills, matching anchor 4 rather than anchor 5's minimal conflict risk.

4 / 5

Total

17

/

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.

Validation — 15 / 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

fengshao1227/ccg-workflow

Path

templates/skills/impeccable/extract/SKILL.md

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.