CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

list

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

Quality

80%

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/list/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.

The body is an exemplary deprecation stub: it states the move, gives an exact install command, tells the agent exactly what to do next, and honestly declares that no component rules live here. It wastes zero tokens and leaves no ambiguity about the single action required.

DimensionReasoningScore

Conciseness

The body is four short statements and one command — every token earns its place, with no over-explanation of what a List or Bricks is beyond the minimal 'the component layer for AI agents' context. It matches anchor 5 ('lean and efficient; assumes Claude's competence') and is clearly better than anchor 4's 'minor instances of over-explanation'.

5 / 5

Actionability

The guidance is fully executable: a copy-paste-ready command ('npx skills add kostja94/bricks --skill component-builder') plus a direct one-line instruction ('Ask the agent to use component-builder to build a new List'). For a redirect stub whose single case is 'move the user to the successor', this matches anchor 5; it exceeds anchor 4 because there are no execution gaps at all.

5 / 5

Workflow Clarity

This is a simple, single-purpose skill (under 50 lines, one task), and the single action — install the new skill, use it instead — is unambiguous with a clear heading ('List construction has moved'). Per the simple-skill guideline this scores 5; no destructive or batch operations are involved, so no validation cap applies.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for bundle files (none exist in references/, scripts/, or assets/), and the content is well-organized with a clear heading and a single clearly-signaled, one-level-deep external link to the successor's List reference. Per the simple-skill guideline this matches anchor 5; nothing is inlined that belongs in a separate file.

5 / 5

Total

20

/

20

Passed

Description

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

This is a well-executed deprecation notice: it clearly states what it is, where the functionality moved, and what to do instead. Its weakness is the absent trigger guidance and sparse natural keywords, which limit its ability to route list-construction requests correctly.

Suggestions

Add an explicit trigger clause such as 'Use when the user asks to build, style, or configure a List component' to raise completeness.

Include natural trigger variations users would actually say ('list component', 'list UI', 'bulleted list widget') to improve trigger term coverage.

Briefly name what component-builder covers for lists (layout, styling, behavior) to sharpen the capability description without adding fluff.

DimensionReasoningScore

Specificity

The description names the domain ("List construction") and 1-2 concrete actions ("install and use component-builder to build a new List"), but lists no specific component capabilities. It fits anchor 3 ('names domain and 1-2 concrete actions') rather than 4, which requires several specific actions — none of the List's actual capabilities are described.

3 / 5

Completeness

The 'what' is clear ("Deprecated compatibility entry for List construction... install and use component-builder"), but there is no 'Use when...' clause or equivalent explicit trigger guidance; per the judging guidelines this caps completeness at 3. It fits anchor 3 ('clear what, when missing or only weakly implied') rather than 4, which requires both.

3 / 5

Trigger Term Quality

"List" and "List construction" are relevant, natural terms, but common variations a user would say ("list component", "list UI", "make/build a list") are missing. This matches anchor 3 ('some relevant keywords but missing common variations or synonyms') — better than 2 (only generic keywords) but short of 4's broader coverage.

3 / 5

Distinctiveness Conflict Risk

The description is scoped to a specific niche (List component construction, successor "kostja94/bricks/component-builder") and clearly labels itself deprecated, making confusion with active skills unlikely. It fits anchor 4 ('mostly distinct; minor overlap risk') rather than 5, since "List" alone is generic enough that queries about lists in general could still land here.

4 / 5

Total

13

/

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/list/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.