Name: webiny-api-website-builder-catalog
Rating: 47.2 (1 reviews)
Author: webiny

Blog Docs Log in Get started

webiny-api-website-builder-catalog

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

Quality

50%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The catalog is concise and uniformly structured with copy-pasteable imports and source paths, but it offers no executable usage examples and leaves several entries without descriptions. Its workflow lacks validation checkpoints for destructive operations, and 57 entries in one file would benefit from being split by concern.

Suggestions

Fill in the missing Description fields for entries like GetDeletedPageByIdUseCase, ListDeletedPagesUseCase, PageAfterRestoreEventHandler, PageAfterTrashEventHandler, PageBeforeRestoreEventHandler, PageBeforeTrashEventHandler, RestorePageUseCase, and TrashPageUseCase.

Add at least one short executable usage snippet (e.g. invoking a UseCase or registering an event handler) so the import lines become copy-paste runnable, and add a validation/check step for destructive operations in the How-to-Use workflow.

Split the monolithic list by concern (e.g. references/pages.md, references/redirects.md, references/scheduler.md) with the body acting as a concise overview linking one level deep.

Dimension	Reasoning	Score
Conciseness	The body is a lean, uniform catalog of Name/Import/Source/Description records with no conceptual padding and no explanation of things Claude already knows, matching the anchor 3 'lean and efficient; every token earns its place.'	3 / 3
Actionability	Each entry provides copy-pasteable import statements and source paths, but there are no executable usage examples and several entries (e.g. GetDeletedPageByIdUseCase, PageAfterRestoreEventHandler) lack any Description, leaving key details missing per anchor 2.	2 / 3
Workflow Clarity	A clear 4-step 'How to Use' sequence exists, but destructive operations (DeletePage, TrashPage, DeleteRedirect) have no validation checkpoints and step 2 is only an implicit manual-read check; the rubric caps destructive-op workflows without feedback loops at 2.	2 / 3
Progressive Disclosure	The 57 abstractions are all inlined in a single monolithic file that could be split by concern (page vs redirect vs scheduler); it points to sibling skills for patterns but keeps content inline, matching anchor 2 'content that should be separate is inline.'	2 / 3
	Total	9 / 12 Passed

Description

35%

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 identifies its domain and artifact types but is written in internal jargon ('abstractions') with no user-facing trigger terms and no 'Use when' clause. It is serviceable as a catalog label but weak as an autonomous trigger description.

Suggestions

Replace jargon ('abstractions') with concrete capabilities and add natural trigger terms a user would say, e.g. 'Create, publish, move, and delete pages and URL redirects; hook into page/redirect lifecycle events. Use when working with the Webiny Website Builder API.'

Add an explicit 'Use when...' clause so the skill triggers reliably and is distinct from sibling webiny-api catalog skills.

Keep third person (currently fine) but lead with the concrete actions (create/publish/move/delete pages and redirects) before the event-handler detail.

Dimension	Reasoning	Score
Specificity	Names the domain ('Website Builder') and concrete artifact types ('Page and redirect event handlers and use cases'), but the actions are generic ('57 abstractions') rather than multiple specific concrete actions, so it lands at anchor 2 rather than 3.	2 / 3
Completeness	It states what the skill contains but provides no 'Use when...' trigger, and the guideline caps completeness at 2 for a missing explicit trigger clause; not 3 (no when) and not 1 (what is present).	2 / 3
Trigger Term Quality	The description relies on technical jargon ('abstractions', 'event handlers and use cases') with no natural keywords a user would actually say, matching the anchor 1 example of jargon with no natural terms.	1 / 3
Distinctiveness Conflict Risk	Scoped to Website Builder pages and redirects, which is a niche, but the generic 'API — abstractions' framing risks overlap with sibling webiny-api catalog skills, matching anchor 2 'somewhat specific but could still overlap.'	2 / 3
	Total	7 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: webiny/webiny-js
Path: skills/user-skills/generated/api/website-builder/SKILL.md
Commit: 484553b

Reviewed: about 11 hours ago

Table of Contents

Discovery Implementation Validation

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.