rds-instance-setup
Rds Instance Setup - Auto-activating skill for AWS Skills. Triggers on: rds instance setup, rds instance setup Part of the AWS Skills skill category.
36
3%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/13-aws-skills/rds-instance-setup/SKILL.mdQuality
Discovery
7%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 very weak skill description that essentially just repeats the skill name without providing any meaningful detail about capabilities, actions, or usage triggers. It lacks concrete actions (e.g., configure, provision, set up security groups), natural user keywords, and an explicit 'Use when...' clause. The description would be nearly useless for Claude to differentiate this skill from other AWS-related skills.
Suggestions
Add specific concrete actions like 'Provisions and configures AWS RDS database instances, sets up security groups, configures parameter groups, manages backups and snapshots, and handles multi-AZ deployments.'
Add an explicit 'Use when...' clause with natural trigger terms: 'Use when the user needs to create a database on AWS, set up RDS, provision MySQL/PostgreSQL/Aurora instances, or configure relational database infrastructure.'
Remove the duplicate 'rds instance setup' in the triggers line and replace with diverse natural language variations users might actually say, such as 'create RDS', 'AWS database', 'provision database', 'set up MySQL on AWS'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'rds instance setup' without describing any concrete actions like creating databases, configuring security groups, setting up parameter groups, or managing backups. It's essentially just a name repeated. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and there is no explicit 'when to use' clause. The 'Triggers on' line just repeats the skill name rather than providing meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms are 'rds instance setup' repeated twice. Missing natural variations users would say like 'create database', 'provision RDS', 'MySQL/PostgreSQL setup', 'AWS database', 'database instance', or 'relational database service'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'RDS' and 'instance setup' provides some specificity to AWS RDS provisioning, which narrows the domain somewhat. However, it could overlap with other AWS database skills or general AWS infrastructure skills due to lack of detail. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no actual content about RDS instance setup. It consists entirely of auto-generated boilerplate that describes what the skill would do without providing any actionable guidance, code, commands, or configuration examples. It adds zero value beyond what Claude already knows.
Suggestions
Add concrete AWS CLI commands or CloudFormation/Terraform templates for creating an RDS instance (e.g., `aws rds create-db-instance --db-instance-identifier mydb --db-instance-class db.t3.micro --engine postgres ...`)
Include a step-by-step workflow covering: 1) VPC/subnet group setup, 2) security group configuration, 3) parameter group selection, 4) instance creation, 5) connection validation with explicit verification commands
Remove all boilerplate sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actual technical content—specific configuration options, best practices for Multi-AZ, encryption, backup retention, etc.
Add concrete examples showing common RDS configurations (e.g., production PostgreSQL with Multi-AZ, dev MySQL single instance) with copy-paste ready code
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, contains no actual technical content about RDS instance setup, and wastes tokens on meta-descriptions like 'Provides step-by-step guidance' without providing any such guidance. | 1 / 3 |
Actionability | There are zero concrete instructions, no code, no CLI commands, no configuration examples, and no specific steps for setting up an RDS instance. The content describes rather than instructs, offering only vague promises of capability. | 1 / 3 |
Workflow Clarity | There is no workflow whatsoever—no steps, no sequence, no validation checkpoints. RDS setup involves multiple steps (VPC/subnet configuration, security groups, parameter groups, instance creation, connection testing) and none are mentioned. | 1 / 3 |
Progressive Disclosure | No bundle files exist and no references are provided. The content is a monolithic block of boilerplate with no structure pointing to detailed materials. There is nothing to progressively disclose because there is no substantive content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.