CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

grid

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

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/grid/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 exemplar of a minimal deprecation stub: lean, unambiguous, and fully actionable for its single purpose of redirecting users to the maintained successor. The install command is copy-paste ready and the external reference is clearly signaled one level deep. No weaknesses were identified against any content dimension.

DimensionReasoningScore

Conciseness

The 5-line body contains no padding and no explanation of concepts Claude already knows: a heading, a one-sentence pointer to the successor reference, an install command, and a closing disposition note. Every token earns its place, matching the 'lean and efficient' anchor.

5 / 5

Actionability

The body provides a fully executable, copy-paste-ready command ('npx skills add kostja94/bricks --skill component-builder') plus a concrete follow-up instruction ('Ask the agent to use component-builder to build a new Grid'), covering the single common case this entry exists for. Nothing is vague or pseudocode, so it matches the anchor for fully executable guidance rather than the minor-gaps level of 4.

5 / 5

Workflow Clarity

This is a simple, single-task skill (redirect to the successor), and that single action is unambiguous: install via the given command, then use component-builder. Per the simple-skill guideline, workflow clarity scores 5 when the single action is unambiguous; there are no destructive or batch operations that would require validation checkpoints.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files (references/, scripts/, assets/ are absent) and no need for external ones; the body is well organized with a heading, a clearly signaled one-level-deep link to the successor reference, a command block, and a disposition note. This satisfies the under-50-line simple-skill criterion for a top structure score.

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 is honest, concise, and in third person, clearly communicating that this is a deprecated compatibility entry and naming its successor. However, it lacks any 'when to use' trigger guidance and only offers minimal keyword coverage, which caps completeness and trigger term quality. As a deprecation notice it functions adequately, but as a skill description for discovery it is incomplete.

Suggestions

Add a 'Use when...' clause or equivalent trigger guidance (e.g., 'Use when the user asks to build or modify a Grid component') so completeness is not capped at 3 and the skill triggers reliably for the right requests.

Broaden trigger term coverage with natural variations users would actually say, such as 'grid layout', 'grid component', or 'data grid', to raise trigger term quality above the 'some relevant keywords' level.

Sharpen distinctiveness by stating what kind of Grid this covers (UI/component grid vs. data or layout grid) to reduce overlap risk with other grid-related skills.

DimensionReasoningScore

Specificity

The description names its domain ('Deprecated compatibility entry for Grid construction') and gives one concrete action ('install and use component-builder to build a new Grid'), which matches the anchor for naming a domain with 1-2 concrete actions. It is not a 4 because it offers no broader capability coverage, and not a 2 because the actions given are concrete rather than generic.

3 / 5

Completeness

The 'what' is clear (deprecated compatibility entry, now maintained in Bricks), but there is no 'Use when...' clause or equivalent trigger guidance, so completeness is capped at 3 per the judging guidelines. It cannot score 4 because the 'when' is entirely missing rather than merely under-specified.

3 / 5

Trigger Term Quality

'Grid construction', 'Grid', and 'component-builder' are natural relevant keywords, but common variations a user might say (grid layout, data grid, grid component) are absent. This sits at 'some relevant keywords but missing common variations or synonyms', below the good-coverage anchor of 4.

3 / 5

Distinctiveness Conflict Risk

The scope ('Grid construction' in Bricks) is somewhat specific, but 'Grid' alone could plausibly collide with other grid-related skills (CSS grid, data grids, layout grids). It is more specific than the broad-overlap anchor of 2 but does not achieve the clear-niche distinctiveness of 4 or 5.

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