Content
88%Weight 40%Scale 1-5Reviews 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.
| Dimension | Reasoning | Score |
|---|---|---|
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 |