CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-api-ai-powerups-catalog

api/ai-powerups — 1 abstractions.

44

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/ai-powerups/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 content is a lean, well-structured catalog entry: a short how-to, exact import and source pointers, and one-level-deep navigation to related pattern skills. Its main weakness is the absence of a concrete usage example and an explicit verification step after selecting an abstraction.

Suggestions

Add a minimal copy-pasteable usage example for CmsGenerateEntryContentUseCase so the guidance is fully executable without opening the source.

Add a verification checkpoint, e.g. confirm the chosen abstraction matches the task before importing, to lift workflow clarity.

Replace imperative 'You MUST' phrasing with neutral guidance to improve tone and token efficiency.

DimensionReasoningScore

Conciseness

The body is short and free of padding or explanations of concepts Claude already knows; every line carries information, with only minor over-direction ('You MUST read the source file') that could be trimmed.

4 / 5

Actionability

It gives concrete, executable guidance — a numbered procedure plus exact import strings and a source file path — with the minor gap that no usage example of the abstraction is shown.

4 / 5

Workflow Clarity

A clear four-step sequence is present, but it delegates real verification to reading the source file with no validation checkpoint of its own; this is acceptable for a lookup skill yet lacks explicit confirmation the right abstraction was chosen.

3 / 5

Progressive Disclosure

The body is a concise overview that points out to other skills ('webiny-use-case-pattern', 'webiny-event-handler-pattern') and to source files one level deep, with clear section headers; no bundle files exist to verify further.

4 / 5

Total

15

/

20

Passed

Description

25%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 catalog label rather than a purpose statement: it names the package and counts abstractions but states no actions or use-when triggers. It fails to answer what the skill does or when to invoke it.

Suggestions

Rewrite in third person with concrete verbs, e.g. 'Catalogs the api/ai-powerups abstractions and their import paths so you can locate the right use-case or event-handler abstraction.'

Add an explicit trigger clause such as 'Use when working in the webiny api/ai-powerups package and you need to find an abstraction, its import path, or source file.'

Replace the bare count ('1 abstractions') with the actual capability list so the description conveys what is offered rather than how many.

DimensionReasoningScore

Specificity

The description only names the domain ('api/ai-powerups') and a count ('1 abstractions') with no concrete actions or verbs describing what the skill does, matching the 'Names the domain but actions are minimal or generic' anchor.

2 / 5

Completeness

It provides an extremely vague 'what' (a count of abstractions) and no 'when' / 'Use when' trigger clause, which per the rubric caps completeness at 3 and lands at 2 given both halves are weak.

2 / 5

Trigger Term Quality

It offers only the technical path 'api/ai-powerups' as a keyword with no natural user-facing phrases or synonyms; generic and missing the natural terms users would say.

2 / 5

Distinctiveness Conflict Risk

The phrase is very broad and reads as an internal catalog label, giving high overlap risk with other api/* catalog skills and no distinct triggers.

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

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.