CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

webiny-page-settings-extensions

Extending the Website Builder page settings with custom settings groups and modifiers. Use this skill when the developer wants to add a new tab/group to the page settings drawer (e.g., Publishing, Analytics, Access Control), or modify an existing settings group (e.g., add fields to General or SEO). Covers PageSettingsGroup, PageSettingsGroupModifier, and the doc.extensions data model. For field types, renderers, and layout details, see the webiny-form-model skill.

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 strong, example-driven reference: both extension workflows are fully executable end-to-end, critical pitfalls (doc.properties writes, missing .tsx extension) are called out with correct/incorrect contrasts, and field-level detail is properly delegated to the sibling skill. Remaining improvements are modest: deduplicate the doc.extensions warnings and add a post-registration verification step.

Suggestions

State the doc.extensions-vs-doc.properties rule once in a dedicated section and drop the repeats in the TL;DR and the 'Reminder' paragraph of 'The Page Document Model' to tighten conciseness.

Add a short verification step after registration (e.g., rebuild/run the admin and confirm the new tab or injected field appears in the page settings drawer) to strengthen the workflow's validation checkpoint.

Consider moving the per-group built-in field-name listings and the IPageDocument model into a small reference file if the skill grows, keeping SKILL.md as a leaner overview.

DimensionReasoningScore

Conciseness

The body is efficient — compact member tables, two purposeful complete code examples, no explanation of concepts Claude already knows. However, the doc.extensions rule is stated three times (TL;DR "Always store custom data in doc.extensions — never write to doc.properties", the entire "Where to Store Data" section, and the "Reminder" paragraph in "The Page Document Model"), which is minor over-explanation that could be trimmed — anchor 4 rather than 5.

4 / 5

Actionability

Fully executable, copy-paste-ready guidance: two complete TypeScript examples with imports and exports (PublishingSettingsGroup, GeneralSettingsModifier), the index.tsx feature-registration component, the webiny.config.tsx registration snippet, concrete import paths ("webiny/admin/website-builder/page/editor"), and per-group built-in field lists for .after() positioning. The examples cover both common cases (new tab, modify existing tab), matching anchor 5.

5 / 5

Workflow Clarity

The sequence — implement the class, wrap in createImplementation, register via createFeature/RegisterFeature, add to webiny.config.tsx — is clear through section order and the registration example importing both prior artifacts. The ".tsx extension... will cause a build failure" warning and the CORRECT/WRONG code contrast act as checkpoints, but there is no explicit verification step (e.g., confirm the new tab renders in the drawer), leaving a minor validation gap at anchor 4 rather than 5. The workflow is additive, not destructive or batch, so the workflow-clarity cap does not apply.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and the body is well organized with clear section headers, tables, and clearly signaled deferral to the webiny-form-model skill ("For field types, renderers, layout, validation, and all other form builder APIs, refer to the webiny-form-model skill" plus a Related Skills section). At ~200 lines with everything inline (built-in field listings, page document model), placement is good with minor organization gaps — anchor 4 rather than 5, which expects appropriately split content across well-signaled reference files.

4 / 5

Total

17

/

20

Passed

Description

87%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.

A strong description: it states concrete capabilities with named APIs, gives an explicit "Use this skill when..." trigger clause with realistic tab examples, and cleanly bounds its scope against the sibling webiny-form-model skill. The only improvement space is broader natural-language variation in trigger terms.

DimensionReasoningScore

Specificity

Quotes several concrete actions — "add a new tab/group to the page settings drawer", "modify an existing settings group (e.g., add fields to General or SEO)" — and names the specific APIs ("Covers PageSettingsGroup, PageSettingsGroupModifier, and the doc.extensions data model"). It lists several specific actions with minor gaps in coverage, matching anchor 4 rather than 5 because it does not comprehensively enumerate the skill's operations beyond the two main capability areas.

4 / 5

Completeness

Explicitly answers both questions: "what" via "Extending the Website Builder page settings with custom settings groups and modifiers... Covers PageSettingsGroup, PageSettingsGroupModifier, and the doc.extensions data model" and "when" via "Use this skill when the developer wants to add a new tab/group to the page settings drawer... or modify an existing settings group", with concrete trigger examples. It also adds a scope boundary ("For field types, renderers, and layout details, see the webiny-form-model skill"), and uses third-person voice throughout — a clear anchor 5.

5 / 5

Trigger Term Quality

Natural phrases a developer would say are present: "page settings drawer", "tab/group", "Publishing, Analytics, Access Control", "add fields to General or SEO". Keyword coverage is good with the tab/group synonym pair and concrete tab names, but a few natural variants (e.g., "settings panel", "extend page settings") are missing, keeping it below anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche (Webiny Website Builder page settings drawer) with distinct triggers, and explicitly defers adjacent territory to the webiny-form-model skill ("For field types, renderers, and layout details, see the webiny-form-model skill"), minimizing conflict risk. Not 4 because the overlap with the closest sibling skill is actively resolved by the deferral clause rather than merely minor.

5 / 5

Total

18

/

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

Path

skills/user-skills/admin/website-builder/page-settings/SKILL.md

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.