AWS CloudFormation patterns for Amazon RDS databases. Use when creating RDS instances (MySQL, PostgreSQL, Aurora), DB clusters, multi-AZ deployments, parameter groups, subnet groups, 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-rds72
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 an excellent skill description that clearly defines its scope (CloudFormation patterns for RDS), lists comprehensive specific capabilities, and includes an explicit 'Use when' clause with abundant natural trigger terms. The description uses proper third-person voice and provides enough detail to distinguish it from both general CloudFormation skills and general database skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creating RDS instances with specific engines (MySQL, PostgreSQL, Aurora), DB clusters, multi-AZ deployments, parameter groups, subnet groups, and template structure elements (Parameters, Outputs, Mappings, Conditions, cross-stack references). | 3 / 3 |
Completeness | Clearly answers both what (CloudFormation patterns for RDS databases) and when (explicit 'Use when' clause listing specific scenarios like creating RDS instances, DB clusters, multi-AZ deployments, and template structure implementation). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'AWS CloudFormation', 'RDS', 'MySQL', 'PostgreSQL', 'Aurora', 'DB clusters', 'multi-AZ', 'parameter groups', 'subnet groups', 'Parameters', 'Outputs', 'Mappings', 'Conditions', 'cross-stack references'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically AWS CloudFormation + RDS databases. The combination of infrastructure-as-code tool and specific AWS service creates a narrow, well-defined scope unlikely to conflict with general database or general AWS skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive, actionable CloudFormation templates for RDS but suffers from severe verbosity - it reads more like exhaustive documentation than a focused skill. The content is technically accurate and executable, but the token cost is excessive given that Claude already understands CloudFormation fundamentals. The skill would benefit from aggressive condensation and better content organization across multiple files.
Suggestions
Reduce content by 60-70% by removing explanations of CloudFormation basics (template sections, parameter types, condition functions) that Claude already knows - focus only on RDS-specific patterns and gotchas
Move detailed reference content (all parameter types, all instance classes, all engine versions) to REFERENCE.md and keep only the most common patterns in the main skill
Add an explicit workflow section with validation checkpoints: 1) Write template → 2) cfn-lint validate → 3) Create change set → 4) Review changes → 5) Execute only if safe
Consolidate the many similar examples (MySQL, PostgreSQL, Aurora MySQL, Aurora PostgreSQL) into a single parameterized template pattern with engine-specific notes
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~1500+ lines, containing extensive explanations of CloudFormation concepts Claude already knows (template sections, parameter types, condition functions). Much content could be condensed to reference patterns rather than exhaustive documentation. | 1 / 3 |
Actionability | The skill provides fully executable, copy-paste ready CloudFormation YAML templates with complete resource definitions, proper syntax, and realistic configurations for MySQL, PostgreSQL, Aurora, and various RDS components. | 3 / 3 |
Workflow Clarity | While the skill covers many RDS operations, it lacks explicit validation checkpoints and feedback loops. The 'Validate Before Deployment' section mentions cfn-lint but doesn't integrate validation into a clear workflow sequence for template creation and updates. | 2 / 3 |
Progressive Disclosure | References to EXAMPLES.md and REFERENCE.md exist at the end, but the main document is a monolithic wall of content. Sections like Parameters, Mappings, Conditions, and detailed resource configurations could be split into separate reference files. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
62%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (1758 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 |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 10 / 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.