Name: webiny-infrastructure-extensions
Rating: 68 (1 reviews)
Author: webiny

webiny-infrastructure-extensions

Modifying AWS infrastructure using Pulumi handlers and declarative Infra components. Use this skill when the developer wants to customize AWS infrastructure, add Pulumi handlers, configure OpenSearch, VPC, resource tags, regions, custom domains, blue-green deployments, environment-conditional config, or manage production vs development infrastructure modes. Covers CorePulumi.Interface, all <Infra.*> declarative components, and <Infra.Env.Is>.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

65%

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

The body is highly actionable with complete, executable TypeScript/TSX examples and is well organized, but it carries redundant reference material that could be tightened and lacks validation checkpoints for risky infrastructure-deployment workflows. With no bundle files, all content lives inline in a single ~200-line file rather than being progressively disclosed.

Suggestions

Add an explicit validation/preview checkpoint before deployment (e.g., run 'pulumi preview' / verify the handler before 'yarn webiny deploy core') to support the feedback loop the workflow_clarity rubric expects for risky infrastructure operations.

Tighten conciseness by either removing the duplicated 'All Infrastructure Components Reference' table and 'Quick Reference' block, or moving them into a dedicated references file so the inline examples are not restated.

Split the detailed per-component examples and reference table into a bundled reference file (e.g., references/components.md) linked from a concise SKILL.md overview to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Code examples are lean and avoid explaining concepts Claude already knows, but the 'All Infrastructure Components Reference' table and 'Quick Reference' largely restate the inline examples and imports above; not level 3 because that duplication could be tightened.	2 / 3
Actionability	Provides complete, copy-paste-ready TypeScript/TSX with imports, props, and concrete props values, plus the specific 'yarn webiny deploy core' command; not level 2 because the examples are executable rather than pseudocode or incomplete.	3 / 3
Workflow Clarity	A loose sequence exists (write handler -> export -> register via <Infra.Core.Pulumi> -> deploy) but there are no validation or verification checkpoints for risky infrastructure deployments, which caps the score per the guidelines; not level 1 because steps are present, not level 3 because checkpoints are missing.	2 / 3
Progressive Disclosure	Sections are well organized (not a wall of text), but the ~200-line file is monolithic with all reference material inline and no external bundle references; the <50-line simple-skill leniency does not apply, so it is not level 3, and it is not level 1 because organization is clear with no nested references.	2 / 3
	Total	9 / 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, complete, and distinctive: it enumerates concrete infrastructure actions, provides an explicit 'Use this skill when...' trigger covering both what and when, and occupies a clear Webiny infrastructure niche. Third-person voice is used throughout.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions such as 'configure OpenSearch, VPC, resource tags, regions, custom domains, blue-green deployments, environment-conditional config', matching the anchor for listing multiple specific concrete actions; not level 2 because it is comprehensive rather than naming only some actions.	3 / 3
Completeness	Explicitly answers both what ('Modifying AWS infrastructure using Pulumi handlers and declarative Infra components' plus 'Covers CorePulumi.Interface, all <Infra.*> declarative components') and when via the 'Use this skill when the developer wants to customize AWS infrastructure...' clause; not level 2 because the trigger is explicit, not implied.	3 / 3
Trigger Term Quality	Covers natural domain terms a Webiny developer would actually say ('custom domains', 'blue-green deployments', 'resource tags', 'regions', 'production vs development'); not level 2 because the term coverage is broad rather than missing common variations.	3 / 3
Distinctiveness Conflict Risk	A clear niche (Webiny AWS infra customization via Pulumi handlers and declarative Infra components) with distinctive triggers unlikely to fire for unrelated skills; not level 2 because it is tightly scoped rather than broadly overlapping.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: webiny/webiny-js
Path: skills/user-skills/infrastructure-extensions/SKILL.md
Commit: 484553b

Reviewed: about 11 hours ago

Table of Contents

Discovery Implementation Validation

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.