AWS CloudFormation patterns for VPC infrastructure. Use when creating VPCs, Subnets, Route Tables, NAT Gateways, Internet Gateways, and implementing template structure with Parameters, Outputs, Mappings, Conditions, and cross-stack references.
Install with Tessl CLI
npx tessl i github:giuseppe-trisciuoglio/developer-kit --skill aws-cloudformation-vpc80
Quality
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Discovery
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.
This is a strong skill description that clearly defines its scope (AWS CloudFormation VPC patterns), lists specific capabilities (VPCs, Subnets, Route Tables, etc.), and includes explicit 'Use when' guidance with natural trigger terms. The description uses proper third-person voice and provides enough detail to distinguish it from other AWS or infrastructure skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and components: 'creating VPCs, Subnets, Route Tables, NAT Gateways, Internet Gateways' and template features like 'Parameters, Outputs, Mappings, Conditions, and cross-stack references'. | 3 / 3 |
Completeness | Clearly answers both what ('AWS CloudFormation patterns for VPC infrastructure' plus specific components) and when ('Use when creating VPCs, Subnets, Route Tables...') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'CloudFormation', 'VPC', 'Subnets', 'Route Tables', 'NAT Gateways', 'Internet Gateways', 'Parameters', 'Outputs', 'cross-stack references' - all terms AWS users naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically AWS CloudFormation for VPC infrastructure. The combination of CloudFormation + VPC + specific networking components creates a unique, non-conflicting scope. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive CloudFormation VPC skill with excellent actionability through complete, executable templates and CLI commands. However, it's verbose for a skill document, including explanatory content Claude already knows and lacking integrated validation workflows. The content would benefit from being split across multiple files with a leaner main skill.
Suggestions
Add an explicit workflow section at the top showing the sequence: 1) Write template → 2) Validate with cfn-lint → 3) Create change set → 4) Review changes → 5) Execute, with validation checkpoints
Move the 'Template Structure' and 'Best Practices' sections to separate reference files (TEMPLATE-STRUCTURE.md, BEST-PRACTICES.md) and link to them
Remove the 'When to Use' section and 'Template Sections Overview' explanations - Claude knows when to use VPC templates and what CloudFormation sections are
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary sections like 'When to Use' that Claude can infer, and the 'Template Structure' section explains concepts Claude already knows. The extensive code examples are valuable but could be more condensed. | 2 / 3 |
Actionability | Excellent actionability with fully executable CloudFormation templates, specific CLI commands for validation, drift detection, and change sets. All code is copy-paste ready with complete resource definitions. | 3 / 3 |
Workflow Clarity | While individual operations are clear, the skill lacks explicit validation checkpoints in the main VPC creation workflows. The 'Validate Before Deployment' section exists but isn't integrated into a clear sequence with feedback loops for the template creation process. | 2 / 3 |
Progressive Disclosure | References to EXAMPLES.md and REFERENCE.md are present, but the main document is quite long (~700 lines) with content that could be split out. The Template Structure section and Best Practices could be separate files to keep the main skill leaner. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
68%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (1190 lines); consider splitting into references/ and linking | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 11 / 16 Passed | |
Table of Contents
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.