CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-api-languages-catalog

api/languages — 2 abstractions.

52

Quality

56%

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/languages/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 tight, well-structured catalog that gives concrete imports and source pointers with a clear usage workflow. Its only gap is the absence of an invocation example, which keeps actionability just short of perfect.

DimensionReasoningScore

Conciseness

The body is lean with no concept re-explanation: a 4-step usage list and two terse entries (name/import/source/one-line description), matching the score-5 anchor of assuming Claude's competence with every token earning its place.

5 / 5

Actionability

It gives copy-paste-ready import statements and explicit source-file paths to read, fitting the score-4 anchor of mostly executable guidance with minor gaps; the gap is that no example shows how to actually instantiate or invoke a use case.

4 / 5

Workflow Clarity

The numbered 'How to Use' sequence (find -> read source -> import -> consult pattern skills) is explicit and unambiguous for this simple catalog lookup, qualifying for the score-5 simple-skill exception; no validation checkpoint is needed because the operation is non-destructive.

5 / 5

Progressive Disclosure

Under 50 lines with well-organized sections (How to Use, Abstractions) and clearly signaled one-level references (source paths and sibling pattern skills), matching the score-5 anchor; no bundle files exist to verify, but the structure is appropriately thin.

5 / 5

Total

19

/

20

Passed

Description

21%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 terse technical label that identifies the domain but provides no actions, no natural trigger terms, and no usage guidance. It is distinct enough by module path yet too sparse to reliably surface when needed.

Suggestions

Add concrete actions, e.g. 'Get a language by code and list all languages via the webiny api/languages use cases.'

Append a 'Use when...' clause naming natural triggers (e.g. 'Use when working with Webiny languages, language codes, or multilingual content').

Replace the abstraction count with what the abstractions do so the description stands alone from the body.

DimensionReasoningScore

Specificity

The description names the domain ("api/languages") and a count ("2 abstractions") but states no concrete actions; it sits between the score-1 anchor (pure abstract language) and score-3 (names 1-2 concrete actions), closer to the score-2 anchor that names a domain with minimal actions.

2 / 5

Completeness

It offers only a vague 'what' (a catalog of 2 abstractions) and no 'when'/trigger guidance at all, matching the score-2 anchor of a vague 'what' with no 'when'; the missing 'Use when' clause also caps completeness at 3 per the guidelines, and this is below that.

2 / 5

Trigger Term Quality

The text "api/languages — 2 abstractions" is pure technical jargon (a module path and an abstraction count) with no natural keywords a user would actually say, matching the score-1 anchor; it does not rise to score-2 because it lacks even generic keywords.

1 / 5

Distinctiveness Conflict Risk

The explicit module path "api/languages" gives it a recognizable niche, but the terse phrasing and generic '2 abstractions' could overlap with sibling webiny api/X catalog skills, fitting the score-3 anchor of somewhat specific with overlap risk.

3 / 5

Total

8

/

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.

Validation16 / 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.