CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-admin-configs-catalog

admin/configs — 1 abstractions.

54

Quality

68%

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/configs/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 is a lean, well-structured catalog with executable import guidance and a clear lookup workflow. Its only weakness is the absence of any usage example for the single listed abstraction.

DimensionReasoningScore

Conciseness

The ~20-line body contains zero padding and no explanations of concepts Claude already knows; every line (import pattern, catalog entry) earns its place.

5 / 5

Actionability

Concrete, copy-paste-ready import lines ('import { AdminConfig } from "webiny/admin/configs"') and an exact source path are given, but there is no usage example showing how AdminConfig is actually applied — a minor gap.

4 / 5

Workflow Clarity

This is a simple single-task skill under 50 lines; the 3-step sequence (find abstraction → read source for exact interface → import) is unambiguous, and no destructive or batch operations require validation checkpoints.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references (no bundle files exist), and its sections ('How to Use', 'Abstractions') are well organized with the source-file pointer clearly signaled.

5 / 5

Total

19

/

20

Passed

Description

28%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 catalog label rather than a capability description: it names the domain and a count but states no actions, no use-when triggers, and no natural keywords. It would rarely be selected from a description alone.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g. 'Use when configuring the Webiny Admin app or extending admin functionality via AdminConfig'.

State what the skill provides, e.g. 'Catalogs the AdminConfig abstraction for Webiny admin (app-admin) configuration: import path, source file location, and interface lookup'.

Include natural keywords and synonyms users would say (e.g. 'webify admin config', 'app-admin', 'admin extension') to improve trigger matching.

DimensionReasoningScore

Specificity

The description only states 'admin/configs — 1 abstractions.', naming a domain but containing zero concrete actions or capabilities, which sits between the purely vague anchor and the 'minimal or generic actions' anchor.

2 / 5

Completeness

The 'what' is extremely vague (just a count of abstractions, no capability statement) and there is no 'when'/'Use when' clause at all, exactly matching the 'vague what and no when' anchor.

2 / 5

Trigger Term Quality

Only the keywords 'admin/configs' and 'abstractions' appear; there are no natural trigger phrases or synonyms a user would actually say, matching the 'one or two generic keywords' anchor.

2 / 5

Distinctiveness Conflict Risk

'admin/configs' is somewhat specific to the Webiny admin-config domain, but the bare path with no verbs or context could still overlap with other config/catalog skills.

3 / 5

Total

9

/

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.