CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

webiny-project-structure

Webiny project layout, webiny.config.tsx anatomy, and extension registration. Use this skill when the developer asks about folder structure, where custom code goes, how to register extensions, what webiny.config.tsx does, or how the project is organized. Also use when they need to understand the relationship between extensions/, webiny.config.tsx, and the different extension types (Api, Admin, Infra, CLI).

Quality

90%

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

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

A well-crafted reference skill: every section teaches Webiny-specific knowledge Claude would not know, code examples are executable and complete, and critical rules are stated with their failure consequences. The main improvement is splitting the detailed tables into a references/ file for better progressive disclosure and trimming minor redundancy.

Suggestions

Move the Extension Types and Infrastructure Components tables (plus the Build Parameters detail) into a references/ file and keep a one-line pointer in SKILL.md, improving progressive disclosure to a 5.

Trim the redundant "Key points" bullets that restate the layout-tree comments, and reduce the near-duplicate <Api.Extension src=…> lines in the config example to two or three that show distinct use cases.

Reconcile the path conventions shown in examples — "/extensions/…" in webiny.config.tsx vs "@/extensions/…" in the BuildParam example — or state when each is valid.

DimensionReasoningScore

Conciseness

The body is dense and Webiny-specific with no explanation of concepts Claude already knows, and the large config example earns its length by demonstrating every registration type. It is not a 5 because the "Key points" list partly restates the layout-tree annotations, and the config example includes several near-duplicate <Api.Extension src=…> lines that could be trimmed.

4 / 5

Actionability

Guidance is fully executable: a complete webiny.config.tsx example, exact JSX element tables, two capitalized MUST rules with the concrete failure mode ("Omitting the file extension will cause a build failure"), a working build-params pattern, and the copy-paste command "yarn webiny extension <extension-name>".

5 / 5

Workflow Clarity

This is a single-purpose reference skill with no multi-step or destructive/batch process, so no validation checkpoints are required; the single action (understanding and registering extensions in the project structure) is unambiguous, and sections flow logically from layout to registration to environment and build configuration.

5 / 5

Progressive Disclosure

Clear TL;DR and well-labeled sections make the ~170-line file easy to navigate, and the Related Skills section signals where to go next. It is not a 5 because no bundle files exist — the extension-types and infrastructure-component tables (and possibly the build-parameters detail) would fit naturally in a references/ file, keeping SKILL.md a leaner overview.

4 / 5

Total

18

/

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 names a specific niche, states what the skill covers, and gives an explicit, natural-language "Use when…" clause with multiple concrete triggers. The only weakness is that the what-clause lists topics rather than concrete actions and omits a couple of capabilities the body actually covers.

DimensionReasoningScore

Specificity

"Webiny project layout, webiny.config.tsx anatomy, and extension registration" names several specific, concrete items (the config file, the extensions/ folder, extension types Api/Admin/Infra/CLI), giving comprehensive coverage of the domain. It falls short of 5 because it states topics rather than concrete actions Claude performs, and misses capabilities the body covers (e.g., build parameters, installing pre-built extensions).

4 / 5

Completeness

The first sentence explicitly answers "what" ("Webiny project layout, webiny.config.tsx anatomy, and extension registration") and the explicit clause "Use this skill when the developer asks about…" answers "when" with multiple concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Phrases like "folder structure", "where custom code goes", "how to register extensions", "what webiny.config.tsx does", and "how the project is organized" are natural things a developer would say. Not 5 because common synonyms such as "directory structure" or "file organization" are absent; not 3 because coverage clearly goes beyond a couple of generic keywords.

4 / 5

Distinctiveness Conflict Risk

Webiny-specific artifacts ("webiny.config.tsx", "extensions/", "extension types (Api, Admin, Infra, CLI)") define a clear niche with distinct triggers, so it is unlikely to fire for unrelated skills.

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/project-structure/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.