rds

AWS RDS relational database service for managed databases. Use when provisioning databases, configuring backups, managing replicas, troubleshooting connectivity, or optimizing performance.

Install with Tessl CLI

npx tessl i github:itsmostafa/aws-agent-skills --skill rds

What are skills?

Review — 77%

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/skill

Learn more

Evaluation — 89%

Agent success when using this skill

Validation — 10 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Discovery

89%

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 well-structured skill description that follows best practices with an explicit 'Use when...' clause and clear AWS RDS scoping. The trigger terms are natural and comprehensive. The main weakness is that the specific actions could be more concrete (e.g., 'create snapshots' vs 'configuring backups').

Dimension	Reasoning	Score
Specificity	Names the domain (AWS RDS) and lists several actions (provisioning, configuring backups, managing replicas, troubleshooting, optimizing), but these are somewhat general categories rather than highly specific concrete actions like 'create read replicas' or 'configure automated snapshots'.	2 / 3
Completeness	Clearly answers both what (AWS RDS relational database service for managed databases) and when (explicit 'Use when...' clause covering provisioning, backups, replicas, connectivity, and performance scenarios).	3 / 3
Trigger Term Quality	Includes natural keywords users would say: 'databases', 'backups', 'replicas', 'connectivity', 'performance', plus the specific service name 'AWS RDS'. These are terms users would naturally use when needing database help.	3 / 3
Distinctiveness Conflict Risk	Clearly scoped to AWS RDS specifically, which distinguishes it from general database skills, other cloud providers' database services, or non-managed database tools. The AWS RDS identifier creates a clear niche.	3 / 3
	Total	11 / 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 solid, actionable AWS RDS skill with excellent executable code examples covering common operations. The main weaknesses are verbosity in explanatory sections that Claude doesn't need, and missing validation checkpoints in multi-step workflows. The content would benefit from trimming definitional content and adding explicit verification steps after critical operations.

Suggestions

Remove introductory explanations of what RDS, Multi-AZ, and Read Replicas are - Claude knows these concepts. Keep only the actionable details.

Add explicit validation steps after create/modify operations, e.g., 'Verify: aws rds describe-db-instances --db-instance-identifier my-postgres --query DBInstances[0].DBInstanceStatus' and wait conditions.

Move the CLI Reference table and detailed troubleshooting sections to separate files (e.g., CLI_REFERENCE.md, TROUBLESHOOTING.md) with clear links from the main skill.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with good use of tables and code examples, but includes some unnecessary explanations Claude already knows (e.g., 'RDS handles provisioning, patching, backups, and failover' in the intro, basic descriptions of what Multi-AZ and Read Replicas are). The content could be tightened by removing definitional content.	2 / 3
Actionability	Excellent actionability with fully executable CLI commands and boto3 code examples that are copy-paste ready. Commands include all necessary parameters and cover the complete workflow from subnet groups to security groups to instance creation.	3 / 3
Workflow Clarity	The PostgreSQL instance creation shows a clear sequence (subnet group → security group → instance), but lacks explicit validation checkpoints. For operations like restore or modify, there's no guidance on verifying success before proceeding. Troubleshooting section provides debug steps but no feedback loops for error recovery.	2 / 3
Progressive Disclosure	Has a table of contents and logical section organization, but the document is quite long (~300 lines) with detailed CLI references and troubleshooting inline. The CLI Reference table and some troubleshooting content could be split into separate files with clear navigation links.	2 / 3
	Total	9 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Reviewed: about 1 hour 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.