CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-api-website-builder-catalog

API — Website Builder — 58 abstractions. Page and redirect event handlers and use cases.

54

Quality

60%

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

Quality

Content

71%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 well-structured, actionable catalog with lean per-entry data and a clear usage workflow, but it monolithically inlines all 58 abstractions instead of using progressive disclosure to keep SKILL.md an overview.

Suggestions

Move the bulk abstraction catalog into a reference file (e.g. references/abstractions.md) and keep SKILL.md as a concise overview/index with category summaries and a link, so the full list is loaded only when needed.

Group the flat alphabetical list by domain (pages, redirects, scheduler, rendering configs) with sub-headers or separate reference files to improve navigability.

Fill in the missing 'Description' fields for entries like GetDeletedPageByIdUseCase, ListDeletedPagesUseCase, PageAfterRestoreEventHandler, and TrashPageUseCase so every entry is self-describing.

DimensionReasoningScore

Conciseness

Entries are lean one-liners with no over-explanation of concepts Claude already knows, though the repeated '**Name:**/**Import:**/**Source:**/**Description:**' label structure across 58 entries could be tightened into a table.

4 / 5

Actionability

Each entry provides a copy-paste-ready import statement and an exact source file path, plus a concrete 4-step How-to-Use; the minor gap is the absence of usage examples (deferred to pattern skills).

4 / 5

Workflow Clarity

The How-to-Use section is a clear 4-step sequence with an explicit 'You MUST read the source file' checkpoint, but there is no validation feedback loop; this is a lookup skill so no destructive-operation cap applies.

4 / 5

Progressive Disclosure

Section headers exist and pattern-skill references are signaled, but the 380-line flat abstraction catalog is inlined in SKILL.md rather than split into reference files, and no bundle files (references/scripts/assets) exist to offload it.

3 / 5

Total

15

/

20

Passed

Description

48%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 names a clear domain and categories but lacks concrete actions and any 'Use when' trigger guidance, capping completeness. It is reasonably distinctive within the webiny ecosystem.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill (e.g., 'Use when working with Webiny Website Builder pages or redirects, or implementing page/redirect use cases and lifecycle hooks').

Replace the categorical 'event handlers and use cases' phrasing with a few concrete actions (e.g., 'create, publish, move, and delete pages and redirects').

Include natural trigger synonyms users might say (e.g., 'URL redirects', 'page lifecycle hooks', 'publishing pages').

DimensionReasoningScore

Specificity

Names the domain ('Website Builder', 'Page and redirect') and two categories ('event handlers and use cases') but lists no concrete actions like create, delete, or publish; actions are minimal and categorical.

2 / 5

Completeness

Has a clear 'what' (page and redirect event handlers and use cases) but no 'Use when...' trigger clause, so per the rubric guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

Contains relevant keywords ('Website Builder', 'Page', 'redirect') a user might say, but 'event handlers' and 'use cases' are technical jargon and common synonyms/variations are missing.

3 / 5

Distinctiveness Conflict Risk

'Website Builder' is a clear niche with minimal conflict risk, though 'Page and redirect event handlers and use cases' could minorly overlap with sibling webiny-api catalog skills.

4 / 5

Total

12

/

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.