CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-api-catalog

api — 21 abstractions.

42

Quality

42%

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

Quality

Content

85%

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 efficient, well-organized abstraction catalog with concrete import paths and a clear usage workflow. Its only gap is the absence of executable usage examples, which keeps actionability from the top level.

DimensionReasoningScore

Conciseness

The body is a lean reference catalog: each abstraction is a compact name/import/source/one-line-description block with no padding and no explanations of concepts Claude already knows, so every token earns its place.

3 / 3

Actionability

It provides concrete, copy-paste import statements and exact source paths, but stops short of executable usage examples — the guidance is actionable for locating and importing, yet incomplete for actually using an abstraction.

2 / 3

Workflow Clarity

The "How to Use" section gives an unambiguous three-step sequence (find abstraction, read source, import) for a simple single-purpose skill, which the rubric allows to score 3 when the action is clear and no destructive/batch validation is needed.

3 / 3

Progressive Disclosure

The content is a flat, one-level-deep catalog of well-organized per-abstraction entries with no nested references; no bundle files exist, so the self-contained, clearly navigable structure is appropriate.

3 / 3

Total

11

/

12

Passed

Description

0%

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 frontmatter description is far too sparse: a single generic noun and an abstraction count with no actions, no trigger terms, and no use-when guidance. It fails to tell Claude what the skill does or when to invoke it.

Suggestions

Rewrite the description to list concrete actions, e.g. "Look up Webiny API abstractions (Ai, Encryption, EventPublisher, KeyValueStore, Result, ...), get their import paths and source file locations. Use when working with the webiny/api package or when you need the import path or source of a Webiny abstraction."

Add an explicit "Use when..." clause naming natural trigger terms users would say ("webiny api", "webiny abstraction", "import path for a Webiny export").

Replace the generic word "api" with the distinctive package name "webiny/api" to reduce conflict risk with other API-related skills.

DimensionReasoningScore

Specificity

The description "api — 21 abstractions" names a domain and a count but describes no concrete actions a user can take, matching the vague/abstract anchor rather than the score-2 anchor which requires some named actions.

1 / 3

Completeness

It states neither what the skill concretely does (only an abstraction count) nor when Claude should use it — there is no "Use when..." trigger, so both what and when are effectively missing.

1 / 3

Trigger Term Quality

"api" is generic technical jargon with no natural keywords a user would actually say when needing this skill; there is no coverage of common variations.

1 / 3

Distinctiveness Conflict Risk

"api" is extremely generic and would conflict with many other skills; nothing distinguishes this skill's niche or narrows the trigger.

1 / 3

Total

4

/

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.