CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

81%

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

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

The body is a dense, accurate configuration reference with executable TSX for every component and a critical registration gotcha called out. Its weakest area is workflow clarity: the handler path (write → register → deploy) is never sequenced explicitly and lacks any validation or post-deploy verification for potentially destructive infrastructure changes. Secondary gaps are the placeholder handler body and structural duplication between the TL;DR, component table, and Quick Reference.

Suggestions

Add an explicit ordered workflow for the handler path (create the extension file → register it in webiny.config.tsx with the .ts extension → preview changes → deploy → verify), including a validation/verification checkpoint such as previewing Pulumi changes or confirming deploy output before considering the change done; this addresses the workflow_clarity cap for destructive infrastructure operations.

Replace the placeholder execute() body with one worked example of reading and modifying a provisioned resource via app.resources (e.g., bumping a Lambda's memory or adding a tag), so the Pulumi handler pattern is fully copy-paste executable rather than scaffolding-only.

Reduce structural duplication: either drop the TL;DR (the frontmatter description already covers it) or drop the inline component examples in favor of the reference table, and consider moving the full component reference into a references/ file to shorten the main SKILL.md.

DimensionReasoningScore

Conciseness

Efficient throughout: no explanations of concepts Claude already knows, and all prose is Webiny-specific. Minor trims are possible — the TL;DR restates the frontmatter description nearly verbatim, and the component reference table plus Quick Reference partially duplicate the per-section examples — so it does not reach the lean-every-token-earns-its-place anchor.

4 / 5

Actionability

Mostly executable: complete TSX for every declarative component with realistic props, a full handler scaffolding with imports and registration, a deploy command ("yarn webiny deploy core"), and a flagged build-failure gotcha ("YOU MUST include the `.ts` file extension in the `src` prop"). It falls short of fully copy-paste-ready because the handler's execute() body is a placeholder ("Access and modify Pulumi resources here") with no worked example of actually modifying a resource.

4 / 5

Workflow Clarity

The Quick Reference implies a sequence (import → implement Interface → export via createImplementation → register → deploy), but it is never presented as an ordered workflow and there are no validation or verification checkpoints (e.g., previewing changes or confirming deploy success) for operations that can tear down infrastructure. Because infrastructure changes are potentially destructive (disabling OpenSearch, changing region) and no verification step exists, workflow clarity is capped at 3. Not 2 because the handler pattern and registration steps are each clearly and correctly delineated in their sections.

3 / 5

Progressive Disclosure

A single-file skill (no references/, scripts/, or assets/ directories exist) with well-organized sections, a summary table, and no broken or dangling file references. At ~220 lines, the full component reference table and per-component examples are candidates for a one-level-deep references file, which keeps it at 'good structure with minor organization gaps' rather than the ideal split.

4 / 5

Total

15

/

20

Passed

Description

83%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 states concrete capabilities in third person, gives an explicit and detailed 'Use this skill when...' trigger clause, and anchors itself with product-specific component names. The main improvement opportunities are naming Webiny explicitly and tightening action phrasing so every listed item reads as a capability rather than a topic.

DimensionReasoningScore

Specificity

Lists several concrete actions ("add Pulumi handlers, configure OpenSearch, VPC, resource tags, regions, custom domains, blue-green deployments, environment-conditional config"), matching the anchor for several specific actions with minor gaps. Not 5 because several items are topic nouns rather than actions and coverage of the body's capabilities (e.g., backups/PITR, resource name prefixes, custom domains for Admin) is incomplete.

4 / 5

Completeness

Explicitly answers both what ("Modifying AWS infrastructure using Pulumi handlers and declarative Infra components") and when ("Use this skill when the developer wants to customize AWS infrastructure, add Pulumi handlers, ...") with concrete trigger phrases, matching the top anchor. It is not 4 because the 'when' clause is already explicit and enumerates specific triggers rather than being generic.

5 / 5

Trigger Term Quality

Contains natural phrases a developer would actually say: "customize AWS infrastructure", "Pulumi handlers", "OpenSearch", "VPC", "resource tags", "custom domains", "blue-green deployments", "production vs development". Good coverage but a few natural terms are missing (webiny.config.tsx, "deploy", backups/PITR/versioning), so it falls short of the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Webiny-specific identifiers (CorePulumi.Interface, <Infra.*> declarative components, <Infra.Env.Is>) carve out a clear niche with distinct triggers. Minor overlap risk remains because "Webiny" is never named, so a generic Pulumi/AWS infrastructure request could plausibly match, keeping it below the minimal-conflict anchor.

4 / 5

Total

17

/

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/infrastructure-extensions/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.