CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

card

Deprecated compatibility entry for Card construction. This component is now maintained in Bricks; install and use component-builder to build a new Card.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/components/layout/card/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

As a deprecation/compatibility stub, the body is exemplary: minimal, fully actionable, and unambiguous. It states where the content moved, gives a copy-paste install command, and explicitly disclaims that this entry contains no component rules.

DimensionReasoningScore

Conciseness

The 18-line body contains zero padding and no explanations of concepts Claude already knows; every sentence states the move, the install command, or the delegation directive. Each token earns its place.

5 / 5

Actionability

Provides a copy-paste ready command ('npx skills add kostja94/bricks --skill component-builder'), direct links to the successor reference, and an explicit directive ('Ask the agent to use component-builder to build a new Card') covering the single common case.

5 / 5

Workflow Clarity

This is a simple, single-purpose redirect skill whose one action is unambiguous (install the successor, delegate Card builds), and it involves no destructive or batch operations requiring validation — the simple-skill exception applies.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files (verified: no references/, scripts/, or assets/ exist, consistent with 'This compatibility entry contains no component rules'), is well organized with a heading, and its single external reference is clearly signaled one level deep.

5 / 5

Total

20

/

20

Passed

Description

50%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 communicates the deprecation and the migration path, which is appropriate for a compatibility stub, but it lacks explicit trigger guidance and natural synonym coverage. Completeness is capped by the missing 'Use when...' clause.

Suggestions

Add an explicit trigger clause, e.g. 'Use when building or styling Card components' — the missing 'Use when...' guidance currently caps completeness at 3.

Include natural variations users would say, such as 'card component', 'UI card', or 'create/edit a card', to improve trigger term coverage.

Clarify the scope of 'Card' (UI component vs. other card meanings) to reduce overlap/conflict risk with unrelated skills.

DimensionReasoningScore

Specificity

Names the domain ('Card construction') and one or two concrete actions ('install and use component-builder to build a new Card'), but coverage of capabilities is minimal — matching the anchor for domain plus 1-2 concrete actions, not a comprehensive list.

3 / 5

Completeness

The 'what' is clear (deprecated entry; component now in Bricks; use component-builder), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Contains relevant keywords ('Card', 'Card construction', 'component-builder', 'Bricks') but misses common natural variations and synonyms such as 'card component', 'UI card', or 'create card'.

3 / 5

Distinctiveness Conflict Risk

'Card construction' is somewhat specific but 'card' alone is ambiguous (UI card, credit card, greeting card) and could overlap with other component-related skills.

3 / 5

Total

12

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

kostja94/marketing-skills

Path

skills/components/layout/card/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.