CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

carousel

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

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

For a deprecation stub, the body is exemplary: it states the move, links the exact new location, gives an executable install command, and explicitly warns that no component rules live here. It is maximally concise, fully actionable, and cleanly organized. The mild wrinkle is the phrase "Ask the agent to use component-builder", which reads as addressed to a human user even though the skill executes inside the agent — cosmetic, not workflow ambiguity.

DimensionReasoningScore

Conciseness

Seven lean lines: a one-sentence redirect with the new location, a copy-paste install command, and one closing clarification ("This compatibility entry contains no component rules and is no longer maintained") that prevents wasted searching. No padding and no explanation of concepts Claude already knows — every token earns its place. Not a 4: there is no over-explanation to trim; even the "component layer for AI agents" descriptor is a single necessary contextual phrase.

5 / 5

Actionability

The body provides a fully executable, copy-paste-ready command (`npx skills add kostja94/bricks --skill component-builder`), a direct link to the carousel component reference that now holds the rules, and an unambiguous instruction for the one common case this skill exists for (build a new Carousel). Not a 4: there is no gap — the redirect action is complete and specific, which is all a compatibility entry should do.

5 / 5

Workflow Clarity

This is a simple, single-purpose skill under 50 lines: the single action (install and use component-builder instead) is stated twice and is unambiguous, so per the simple-skill scoring note workflow clarity can score 5. No destructive or batch operations are involved, so no validation checkpoints are required.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and none are needed; the only pointer is the clearly signaled, one-level-deep link to the carousel reference in Bricks. The body is well organized (title, location, command, closing note) — matching the guideline that skills under 50 lines with no need for external references can score 5 with well-organized sections. Not a 4: there is no content that should be split out and no buried or multi-level reference chain.

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.

The description is honest and appropriately scoped for a deprecation stub: it states what it is, where the component moved, and what to install instead. Its main gaps for the description rubric are the absent "Use when..." trigger clause (capping completeness) and the lack of carousel synonyms beyond the single keyword. As a redirect entry it communicates clearly, but it makes no effort to be discoverable through the terms users actually say.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to build a carousel or image slider" — this would raise completeness above its current cap of 3.

Include common user-facing synonyms such as "image slider", "gallery", or "scroller" alongside "Carousel" so the entry triggers on the phrases users naturally say.

State the redirect action in third-person capability form (e.g. "Redirects Carousel construction to the component-builder skill") rather than the imperative "install and use component-builder".

DimensionReasoningScore

Specificity

"Deprecated compatibility entry for Carousel construction" names the domain, and "install and use component-builder to build a new Carousel" gives 1-2 concrete redirect actions — matching the anchor for naming a domain with 1-2 concrete actions, but not comprehensive. Not a 4: it lists no multiple capability actions (the entry intentionally has none); not a 2: the actions given are concrete, not minimal/generic.

3 / 5

Completeness

The "what" is clear ("Deprecated compatibility entry... now maintained in Bricks; install and use component-builder"), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not a 4: both what and when are required; not a 2: the what is explicit, not vague.

3 / 5

Trigger Term Quality

"Carousel" / "Carousel construction" are the natural keyword a user would say, but common synonyms users also use for this component (image slider, gallery, scroller) are missing — the anchor for some relevant keywords missing common variations. Not a 4: coverage rests on a single keyword repeated, not good broad coverage; not a 2: "Carousel" is a specific, natural term, not generic filler.

3 / 5

Distinctiveness Conflict Risk

"Carousel construction" carves a clear niche unlikely to trigger the wrong skill, but the entry deliberately overlaps with its successor component-builder (which also triggers on carousel requests) — matching "mostly distinct; minor overlap risk with closely related skills". Not a 5: the intentional coexistence with component-builder is a real, if by-design, overlap; not a 3: the trigger is far more specific than generic document/file phrasing.

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