CtrlK
BlogDocsLog inGet started
Tessl Logo

extract

Extract and consolidate reusable components, design tokens, and patterns into your design system. Identifies opportunities for systematic reuse and enriches your component library.

77

1.04x
Quality

66%

Does it follow best practices?

Impact

99%

1.04x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./archived/legacy-companion/.agents/skills/extract/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 body is well-organized, lean, and clearly sequenced, but its guidance stays at the checklist level rather than fully executable, and the destructive Migrate phase lacks a hard validate→fix→retry loop. Tightening the migrate mechanics and adding a concrete example would raise the two mid-scoring dimensions.

Suggestions

Add a concrete migration example (e.g. a before/after import diff or a sample codemod command) to move actionability from checklist-level toward executable.

Turn the soft 'Test thoroughly' in Migrate into an explicit validation loop: 'After replacing each instance, verify parity; if visual/functional drift, revert and re-extract before proceeding.'

Specify the search step concretely (e.g. example grep/AST-search commands for finding duplicated component patterns) so Migrate is actionable rather than abstract.

DimensionReasoningScore

Conciseness

The body uses terse imperative bullets and never explains concepts Claude already knows (no 'what a design system is' filler); only the closing 'Remember' line is mildly dispensable, so it is lean and largely earns its tokens.

3 / 3

Actionability

There is concrete guidance (the grep hint, specific component/token quality criteria, and the NEVER guardrails), but the Migrate mechanics stay abstract ('Search for the patterns', 'Update each use') and there are no executable examples or before/after snippets, leaving key details missing.

2 / 3

Workflow Clarity

The Discover→Plan→Extract→Migrate→Document sequence is clear with a CRITICAL checkpoint, but the destructive/batch Migrate step relies on a soft 'Test thoroughly' with no validate→fix→retry feedback loop, so per the rubric it is capped at 2.

2 / 3

Progressive Disclosure

No bundle files exist and none are needed; the skill is a self-contained process with a brief overview followed by well-organized phase sections and no content that ought to be split out, matching the simple-skill allowance for a clean score-3.

3 / 3

Total

10

/

12

Passed

Description

60%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 is specific and action-oriented about what the skill does, but it omits any explicit 'when to use' trigger guidance, leaving completeness and trigger-term coverage at the mid level. Adding a 'Use when...' clause with natural trigger phrases would lift the weaker dimensions.

Suggestions

Append an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when the user wants to consolidate duplicated UI, build a component library, or introduce design tokens.'

Add common user-facing variations of the trigger terms (e.g. 'shared components', 'UI library', 'design system cleanup', 'tokenize hard-coded styles') to improve trigger-term coverage.

Sharpen distinctiveness by naming the boundary with general refactoring (e.g. 'Focused on design-system consolidation, not general code refactoring').

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Extract and consolidate reusable components, design tokens, and patterns', 'Identifies opportunities for systematic reuse', 'enriches your component library'), matching the score-3 anchor for multiple specific actions rather than just naming a domain.

3 / 3

Completeness

It clearly answers WHAT the skill does but provides no explicit WHEN guidance; per the rubric a missing 'Use when...' clause caps completeness at 2.

2 / 3

Trigger Term Quality

Contains relevant domain keywords a user might say ('design system', 'design tokens', 'component library', 'reusable components') but offers no natural trigger variations or 'Use when' phrasing, so coverage of natural trigger terms is incomplete.

2 / 3

Distinctiveness Conflict Risk

The design-system/component-library framing is a clear niche, but absent explicit triggers and potential overlap with general refactoring or cleanup skills means it could still trigger for the wrong skill.

2 / 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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
The-Vibe-Company/companion
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.