Lean body that assumes competence: no padding about what Webiny, Lambda, or bytes are, and each section (TL;DR, byte table, How It Works, Quick Reference) earns its place. The Quick Reference table duplicates a couple of values already shown in code, but that redundancy serves as a useful lookup rather than filler.

Fully executable TSX with exact byte expressions, the verbatim build error output to recognize, and copy-paste-ready snippets in the Quick Reference table.

A simple single-action config skill where the action (add the extension with a byte size) is unambiguous; per the rubric's simple-skill guidance this scores 3, and it even includes the build error message as the implicit feedback signal.

A self-contained, well-sectioned skill with no external bundle files needed; organized into clear navigable sections (TL;DR, Default Behavior, Raising/Lowering the Limit, Quick Reference, Related Skills), satisfying the rubric's no-references-needed criterion.

Names multiple concrete actions ('extension syntax, byte calculations, and interpreting the build error message') and the exact extension/file, which would normally score 3, but the second-person phrasing 'when you want to enforce a stricter limit' triggers the rubric's voice penalty reducing specificity by 1.

Explicitly answers both 'what' ('Covers how to configure the maximum allowed size... using the Infra.Api.MaxBundleSize extension') and 'when' via an explicit 'Use when' clause.

Natural user-facing triggers are present — 'API bundle exceeds the default 4.5 MB limit', 'enforce a stricter limit', and 'build error message' — matching what a developer would actually say.

Targets a narrow niche — the Webiny API Lambda bundle size limit via a named extension in a specific config file — making conflict with other skills very unlikely.