CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-admin-lexical-catalog

admin/lexical — 17 abstractions.

49

Quality

53%

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/lexical/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 that delivers exact import paths and source locations for all 17 abstractions with a clear usage workflow. It is a model of lean, actionable reference content.

DimensionReasoningScore

Conciseness

The body is extremely lean — three lines (Name/Import/Source) per entry plus a three-step usage block — with no concept explanations or padding; every token earns its place.

3 / 3

Actionability

Each of the 17 abstractions ships a concrete, copy-paste-ready import statement and an exact source file path, and the usage block gives an executable import template — fully actionable for a catalog skill.

3 / 3

Workflow Clarity

The "How to Use" block lays out a clear find → read-source → import sequence, and because this is a simple, non-destructive lookup skill the simple-skill allowance applies; the "MUST read the source" step serves as the explicit checkpoint.

3 / 3

Progressive Disclosure

The content is a flat, one-level catalog with clear "How to Use" and "Abstractions" sections and a consistent per-entry format; no bundle files exist to verify, and nothing is nested or monolithic.

3 / 3

Total

12

/

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 terse label-plus-count that fails to convey what the skill does or when to invoke it, relying on jargon rather than natural trigger terms. It is distinctive only by virtue of its module path, not its wording.

Suggestions

Rewrite the description in third person to state concrete actions, e.g. "Catalogs and imports the admin/lexical editor abstractions (hooks, components, types) from the webiny lexical-editor package."

Add an explicit trigger clause such as "Use when working with the webiny admin lexical editor and you need the correct import path or source file for a hook, component, or type."

Include natural keywords users would actually say (e.g. "lexical editor", "rich text editor", "webiny editor hooks/components") instead of the generic term "abstractions".

DimensionReasoningScore

Specificity

The description "admin/lexical — 17 abstractions." names a domain and a count but describes zero concrete actions, falling below the level-2 anchor which requires "some actions."

1 / 3

Completeness

It barely answers "what" (only a count of abstractions, not what they do) and entirely omits any "Use when..." trigger guidance, leaving both halves weak or missing.

1 / 3

Trigger Term Quality

Terms like "admin/lexical" and "abstractions" are technical jargon a user would not naturally say; they are not the natural keywords (e.g. "lexical editor", "rich text editor components") someone would utter when needing this skill.

1 / 3

Distinctiveness Conflict Risk

"admin/lexical" points to a fairly specific niche, but the description is too thin and generic ("17 abstractions") to clearly differentiate it from sibling catalog skills, so overlap risk remains.

2 / 3

Total

5

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

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.