CtrlK
BlogDocsLog inGet started
Tessl Logo

rds

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

82

1.03x
Quality

77%

Does it follow best practices?

Impact

89%

1.03x

Average score across 3 eval scenarios

SecuritybySnyk

Risky

Do not use without reviewing

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/rds/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

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 good trigger term coverage. The main weakness is that the capability descriptions are somewhat categorical rather than listing specific concrete actions. Overall, it should effectively enable Claude to select this skill when users need AWS RDS assistance.

DimensionReasoningScore

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 with five specific trigger scenarios: provisioning, backups, replicas, connectivity, performance).

3 / 3

Trigger Term Quality

Includes natural keywords users would say: 'databases', 'backups', 'replicas', 'connectivity', 'performance', 'RDS', 'provisioning'. These cover common terms users would naturally use when needing database help.

3 / 3

Distinctiveness Conflict Risk

AWS RDS is a specific service with clear boundaries. The combination of 'AWS RDS' with database-specific triggers like 'replicas', 'backups', and 'managed databases' creates a distinct niche unlikely to conflict with general database or other AWS skills.

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 and comprehensive coverage of common operations. The main weaknesses are the lack of validation checkpoints in multi-step workflows and the monolithic structure that could benefit from splitting into separate reference files. Some introductory content explains concepts Claude already knows.

Suggestions

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')

Split CLI Reference and Best Practices into separate files (CLI_REFERENCE.md, BEST_PRACTICES.md) with clear links from the main skill

Remove the opening paragraph explaining what RDS is - Claude already knows this

Add a feedback loop for the restore workflow: verify instance status before connecting

DimensionReasoningScore

Conciseness

The skill is mostly efficient with good use of tables and code examples, but includes some unnecessary explanations (e.g., 'RDS handles provisioning, patching, backups, and failover' and basic concept definitions that Claude already knows). The opening paragraph and some section headers could be trimmed.

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 flags, and the troubleshooting section provides specific debug commands.

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 verification step to confirm success before proceeding. Missing feedback loops for potentially destructive operations.

2 / 3

Progressive Disclosure

Good table of contents and section organization, but the document is quite long (~300 lines) with all content inline. The CLI Reference and Best Practices sections could be split into separate files with clear navigation. References section is appropriate but could be better integrated.

2 / 3

Total

9

/

12

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
itsmostafa/aws-agent-skills
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.