CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-admin-ui-catalog

admin/ui — 99 abstractions.

46

Quality

50%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/user-skills/generated/admin/ui/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-organized, token-efficient catalog providing copy-paste-ready imports and exact source paths with a clear lookup workflow. Its main weakness is structural: 99 entries are inlined in one monolithic file rather than progressively disclosed via reference files.

DimensionReasoningScore

Conciseness

Each entry is a tight three-line block (Name/Import/Source) with no concept explanations Claude already knows and no padding; the lean 'How to Use' adds only the essential import pattern.

3 / 3

Actionability

Every abstraction ships a copy-paste-ready import statement plus an exact source path, and the documented 'import { Name } from "<importPath>"' pattern is fully executable.

3 / 3

Workflow Clarity

The 3-step How to Use sequence is clear and unambiguous with an explicit guard ('You MUST read the source file to get the exact interface and types!'); as a simple lookup skill with no destructive/batch operations, no validation loop is required.

3 / 3

Progressive Disclosure

Entries are consistently formatted and the file has a clear How-to-Use header, but ~600 lines of catalog are inlined monolithically in SKILL.md with no bundle reference files, so content that could be split out is inline.

2 / 3

Total

11

/

12

Passed

Description

7%

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 a bare label ('admin/ui — 99 abstractions.') that names a domain and count but states no concrete capabilities, omits any usage trigger, and leans on jargon rather than natural user terms. It is distinguishable only by its narrow domain, not by clear invocation cues.

Suggestions

Rewrite the description to state concrete actions, e.g. 'Discover and import Webiny admin UI components (Button, Dialog, DataTable, ...); read each source file for its exact props and types.'

Add an explicit 'Use when...' trigger clause naming natural terms users would say, such as 'building or extending a Webiny admin app's UI' or 'needing a webiny/admin/ui component'.

Replace the jargon 'abstractions' with plain language ('reusable UI components and hooks') and drop the raw count so the description reads as a capability statement rather than a label.

DimensionReasoningScore

Specificity

The description 'admin/ui — 99 abstractions.' only names a domain and a count; it lists no concrete actions (e.g. 'render', 'compose', 'import UI components'), matching the 'vague or no actions' anchor.

1 / 3

Completeness

The 'what' is only weakly implied (a catalog of UI exports) and the 'when' is entirely missing with no 'Use when...' clause, so both halves are very weak.

1 / 3

Trigger Term Quality

'admin/ui' and 'abstractions' are technical jargon; a user would not naturally say 'I need 99 abstractions', and no common natural-language trigger terms are present.

1 / 3

Distinctiveness Conflict Risk

The 'admin/ui' domain names a somewhat specific niche, but with no distinct trigger terms it could still overlap with sibling Webiny admin skills; it is not so generic as the score-1 anchor.

2 / 3

Total

5

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (613 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
webiny/webiny-js
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.