CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sidebar-generator

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

Quality

77%

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/navigation/sidebar/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 does exactly what a deprecation stub should: states the move, links the successor's reference, gives the exact install command, and tells the agent what to do, all in a handful of lines. Its only weakness is slight redundancy around the deprecation status.

DimensionReasoningScore

Conciseness

The body is lean — a heading, one redirect sentence, a copy-paste install command, and a delegation instruction — but "the component layer for AI agents" and "This compatibility entry contains no component rules and is no longer maintained" repeat information already conveyed, making them minor trim candidates. This matches the anchor for efficient content with minor instances that could be trimmed, just short of the every-token-earns-its-place level.

4 / 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 successor's Sidebar reference, and an explicit instruction ("Ask the agent to use component-builder to build a new Sidebar"). For a redirect stub, this is complete executable guidance matching the top anchor.

5 / 5

Workflow Clarity

This is a simple, single-purpose skill under 50 lines with one unambiguous action: install component-builder and delegate to it. The rubric's simple-skill note allows a 5 when the single action is unambiguous, and no destructive or batch operations exist that would require validation checkpoints.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no external references needed (no references/, scripts/, or assets/ directories exist), and the body is well organized with a clear heading, link, and code block — meeting the rubric guideline for a top progressive-disclosure score in this case.

5 / 5

Total

19

/

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 accurate and honest about the skill's deprecated status and clearly identifies its successor, but as a redirect stub it lacks trigger guidance and keyword coverage. It answers "what" well but never answers "when" a user should invoke it.

Suggestions

Add an explicit trigger clause such as "Use when the user asks to build or modify a Sidebar, side panel, or navigation drawer" so invocation conditions are unambiguous.

Include natural user phrasings beyond the bare term "Sidebar" (e.g., side panel, navigation sidebar, left/right sidebar) to improve trigger-term coverage.

State directly what Claude should do when this entry is invoked (e.g., "When invoked, install and delegate to component-builder rather than following any legacy rules") so the intended runtime behavior is explicit.

DimensionReasoningScore

Specificity

The description names the domain ("Sidebar construction") and one concrete action pair ("install and use component-builder to build a new Sidebar"), matching the anchor for naming a domain with 1-2 concrete actions but not comprehensive coverage. It is above anchor 2 because the actions given are concrete rather than generic, but below anchor 4 because it does not list several specific actions.

3 / 5

Completeness

The "what" is clear (deprecated compatibility entry whose successor is component-builder in Bricks), but there is no "Use when..." clause or equivalent explicit trigger guidance; the "when" is only weakly implied by "to build a new Sidebar". Per the rubric guideline, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

"Sidebar" is the natural keyword a user would say, but the description offers no variations or synonyms (navigation, side panel, UI sidebar). This fits the anchor for some relevant keywords while missing common variations — above anchor 2 (keywords are domain-specific, not generic) but below anchor 4 (coverage beyond the single term is thin).

3 / 5

Distinctiveness Conflict Risk

The explicit redirect to component-builder gives the entry a clear niche, but "Sidebar" is a common UI term, leaving minor overlap risk with general sidebar/navigation UI skills — matching the anchor for mostly distinct with minor overlap risk. It is below anchor 5 because there are no distinct trigger phrases separating it from those skills.

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/navigation/sidebar/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.