CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-admin-ui-extensions

Customizing the Webiny Admin UI -- white-labeling, custom data list columns, page-type forms, and Lexical editor plugins. Use this skill when the developer wants to change branding (logo, title, theme colors), add custom columns to content entry list views, create custom forms for Website Builder page types, or extend the Lexical rich text editor. Covers AdminConfig, ContentEntryListConfig, Browser.Table.Column, Bind, useForm, and form validation.

75

Quality

93%

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

87%

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

The body is concise and highly actionable with complete code examples and reference tables. Its only weak spot is workflow clarity: the build/deploy cycle lacks an explicit validation or feedback checkpoint despite warning about a build-failure footgun.

Suggestions

Add an explicit verification step after registration and before deploy (e.g., 'run yarn webiny watch admin and confirm no build errors before yarn webiny deploy admin') to close the feedback loop the build-failure warning implies.

Make the .tsx file-path rule a numbered checklist step in the registration flow rather than only a TL;DR warning, so the validation checkpoint is procedural rather than advisory.

DimensionReasoningScore

Conciseness

Lean and code-forward with no concept-explanation fluff; the TL;DR and reference tables assume Claude's competence and every section earns its tokens.

3 / 3

Actionability

Provides complete, executable .tsx examples with imports and registration snippets, plus dense prop/component reference tables that are copy-paste ready.

3 / 3

Workflow Clarity

Each category has a clear write-then-register sequence and build/deploy commands are listed, but there is no explicit validation or feedback checkpoint despite a build-failure footgun being flagged.

2 / 3

Progressive Disclosure

A single self-contained file organized into clear sections with no nested references, and cross-skill navigation via the Related Skills list.

3 / 3

Total

11

/

12

Passed

Description

100%

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 specific, trigger-rich, and complete, naming concrete actions and explicit 'Use when' guidance tied to a well-defined Webiny Admin UI niche. It distinguishes itself clearly via named APIs and a focused scope.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — white-labeling, custom data list columns, page-type forms, and Lexical editor plugins — with named APIs (AdminConfig, ContentEntryListConfig, Bind, useForm).

3 / 3

Completeness

Explicitly answers both what (the four customization categories) and when via the 'Use this skill when the developer wants to...' trigger clause.

3 / 3

Trigger Term Quality

Covers natural terms a Webiny developer would actually say — branding, logo, title, theme colors, content entry list views, Website Builder page types, Lexical rich text editor.

3 / 3

Distinctiveness Conflict Risk

Clear niche scoped to Webiny Admin UI extensions with named framework APIs, making it unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

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.