CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-admin-ai-powerups-catalog

admin/ai-powerups — 1 abstractions.

52

Quality

65%

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/ai-powerups/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 an efficient, well-structured catalog that tells Claude exactly how to find and import an abstraction; the only gap is the absence of any usage example beyond the import line.

DimensionReasoningScore

Conciseness

The body is lean with no padding or over-explanation: a 3-step How to Use and a minimal abstraction entry, so every token earns its place and it assumes Claude's competence.

5 / 5

Actionability

It gives a concrete copy-paste import and the real source path, plus a template, but stops at import boilerplate with no usage example, leaving a minor gap.

4 / 5

Workflow Clarity

As a simple single-purpose skill, its 3-step sequence (find abstraction, read source, import) is clear and unambiguous, qualifying for the simple-skill exception.

5 / 5

Progressive Disclosure

Under 50 lines with no need for external bundle files, it is cleanly split into How to Use and Abstractions sections, satisfying the well-organized-sections bar for simple skills.

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 near-empty label: it identifies the module and counts its abstractions but states no capabilities and no trigger guidance, leaving Claude without a reason to invoke it.

Suggestions

State what the catalog provides, e.g. "Catalogs reusable AI powerup abstractions for the Webiny admin and shows their import paths and source files."

Add a trigger clause such as "Use when the user needs a Webiny admin AI abstraction or asks how to import an ai-powerup feature."

Include natural user-facing terms ("Webiny admin", "AI powerup", "reusable abstraction") instead of only the module path.

DimensionReasoningScore

Specificity

The phrase "admin/ai-powerups — 1 abstractions" names the module domain but describes no concrete actions beyond a count of abstractions, matching the anchor that names the domain with minimal/generic actions.

2 / 5

Completeness

It offers only a vague "what" (a catalog of abstractions) and provides no "Use when..." trigger guidance, fitting the anchor for a vague what and no when.

2 / 5

Trigger Term Quality

The only terms are technical jargon ("admin/ai-powerups", "abstractions") that a user would never naturally say when they need this skill, matching the anchor for no natural keywords.

1 / 5

Distinctiveness Conflict Risk

Naming a specific module (admin/ai-powerups) gives it a niche, but the description is too sparse to clearly distinguish it from related catalog skills, matching the somewhat-specific-but-overlapable anchor.

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.

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.