CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-admin-catalog

admin — 28 abstractions.

42

Quality

53%

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/user-skills/generated/admin/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 catalog is a genuinely actionable index: exact imports, exact source paths, and a clear find-read-import workflow. Its weaknesses are token redundancy from repeating the identical import path 28 times and the lack of grouping or disambiguation for similarly named abstractions.

Suggestions

Collapse the per-entry '**Import:**' line into the 'How to Use' template (all 28 share 'webiny/admin') and keep only Name + Source per entry, roughly halving the token cost.

Group entries under feature-area subheadings (command palette, providers/hooks, tools, bulk actions, build params) to make the flat 190-line list navigable.

Add a one-line disambiguation note for confusable pairs such as BuildParam vs BuildParams and createProvider vs createProviderPlugin vs Provider.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence (pointing to source files instead of restating interfaces), but the '**Import:** import { X } from "webiny/admin"' line is repeated verbatim across all 28 entries even though the import path is identical, which is systematic redundancy that could be trimmed rather than a minor instance.

3 / 5

Actionability

Every entry gives an exact import statement and exact source path, and the instruction 'You MUST read the source file to get the exact interface and types' is concrete and executable; the minor gap is that no entry includes a usage example.

4 / 5

Workflow Clarity

The three-step workflow (find the abstraction, read the source file, import) is unambiguous for this simple single-purpose catalog, but there is no disambiguation guidance for near-duplicate names such as BuildParam/BuildParams or createProvider/createProviderPlugin/Provider, leaving a minor gap rather than a fully clear sequence.

4 / 5

Progressive Disclosure

No bundle files exist, and the inline catalog is itself the index with each 'Source:' acting as a clearly signaled one-level-deep pointer; however, roughly 190 lines of flat entries with no grouping by feature area (command palette, providers, tools, bulk actions) leaves a minor organization gap.

4 / 5

Total

15

/

20

Passed

Description

16%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 a bare title rather than a capability description: it identifies the domain and entry count but provides no actions, no trigger guidance, and no distinguishing detail. It would rarely be selected over more descriptive sibling skills.

Suggestions

State concrete capabilities in third person, e.g. 'Catalogs 28 Webiny admin-area abstractions (AdminConfig, CommandPalettePresenter, createProvider, ...) with import paths and source file locations.'

Add an explicit trigger clause such as 'Use when working with the Webiny admin app, extending app-admin features, or importing from webiny/admin.'

Include natural trigger terms and synonyms (Webiny admin, admin area, admin plugins, command palette, providers) so the skill is discoverable for the situations it covers.

DimensionReasoningScore

Specificity

The description 'admin — 28 abstractions.' names the domain and a count but states no concrete actions or capabilities, matching the anchor for domain-named with minimal/generic action content rather than entirely vague language.

2 / 5

Completeness

Neither 'what does this do' (the text is a label, not a capability statement) nor 'when should Claude use it' is present or even weakly implied, matching the missing-both anchor.

1 / 5

Trigger Term Quality

The only keyword present is the generic 'admin'; no natural phrases, synonyms, or specific terms a user would say when needing this catalog, matching the one-or-two-generic-keywords anchor.

2 / 5

Distinctiveness Conflict Risk

'admin' is an extremely broad term that would overlap with almost any admin-related skill; there is no niche signal beyond the abstraction count.

2 / 5

Total

7

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.