CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

masonry

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

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/masonry/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: maximally concise, fully actionable with a copy-paste install command and a direct link to the successor, and unambiguous about the single redirect workflow. Nothing is padded and no structure is missing for a skill of this size and purpose.

DimensionReasoningScore

Conciseness

The body is ~5 lean lines: a heading, one sentence with links, one install command, and one closing instruction ('This compatibility entry contains no component rules and is no longer maintained'). It assumes Claude's competence, explains nothing it already knows, and every token earns its place — a clear anchor 5.

5 / 5

Actionability

It provides a copy-paste-ready command ('npx skills add kostja94/bricks --skill component-builder'), a direct link to the masonry reference, and a concrete next step ('Ask the agent to use component-builder to build a new Masonry'). For the single case this skill exists for (redirecting to the successor), the guidance is fully executable.

5 / 5

Workflow Clarity

This is a simple, single-purpose skill and its one action is unambiguous: where the content moved, how to install the replacement, and what to ask for. There are no destructive or batch operations, so the validation cap does not apply and the simple-skill exception grants a 5.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files (no references/, scripts/, or assets/ directories exist), and the only reference is a clearly signaled, one-level-deep external link to the Masonry reference. Per the simple-skill note, well-organized short content with no needed external files scores 5.

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 clear and honest about the skill's deprecated, moved status and gives a concrete redirect action, but it functions as a tombstone rather than a trigger: it lacks any 'Use when...' guidance and offers no description of what Masonry construction actually covers. A user or agent searching for masonry capabilities would find it, but only by luck of the single keyword.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks for Masonry construction or mentions masonry components', so the entry reliably fires when needed and completeness can rise.

Include natural keyword variations users might say (e.g. 'masonry wall', 'brick layout', 'masonry component') to broaden trigger term coverage beyond the single term 'Masonry'.

State in one short phrase what Masonry construction actually does (the capability now living in Bricks), so the 'what' is functional rather than purely identity-based.

DimensionReasoningScore

Specificity

The description names the domain ('Masonry construction') and 1-2 concrete actions ('install and use component-builder to build a new Masonry'), matching anchor 3. It does not reach anchor 4 because it lists no construction capabilities, and it sits above anchor 2 because the actions given are specific rather than generic.

3 / 5

Completeness

The 'what' is explicit for a stub ('Deprecated compatibility entry for Masonry construction. This component is now maintained in Bricks'), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the what and where are clearly stated rather than vague.

3 / 5

Trigger Term Quality

'Masonry construction' and 'Masonry' are relevant natural keywords a user would say, but no variations or synonyms are included ('build a masonry wall', 'brick layout', etc.), which matches anchor 3 ('some relevant keywords but missing common variations') rather than anchor 4's fuller keyword coverage.

3 / 5

Distinctiveness Conflict Risk

'Masonry' is a distinctive niche term and the entry names its successor ('kostja94/bricks/component-builder'), making it mostly distinct with minimal conflict risk. It stays at anchor 4 rather than 5 because it deliberately overlaps with the closely related 'component-builder' skill it redirects to, and lacks explicit trigger phrases.

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