CtrlK
BlogDocsLog inGet started
Tessl Logo

rds-oss

Advises on Amazon RDS open-source engines (MySQL, MariaDB, PostgreSQL) for instance creation, upgrade planning, commitment pricing, proxy evaluation, and Blue/Green deployments. Handles any RDS MySQL, MariaDB, or PostgreSQL question, including create a production-ready RDS MySQL instance, provision an RDS PostgreSQL database, run the RDS upgrade advisor for my RDS MySQL instance, what are my upgrade options, upgrade RDS MariaDB from 10.6 to the latest version, should I buy reserved instances or a savings plan for db.r7g.2xlarge RDS MySQL, change a VARCHAR to INT column on RDS MySQL 8.0 with Blue/Green, and does RDS Proxy help when PgBouncer already runs in transaction mode. Covers instance creation with production best practices, describe-db-instances and describe-db-engine-versions upgrade-target workflow, live prechecks via SSM or direct connection, RI versus DSP commitment pricing, RDS Proxy versus PgBouncer, and Blue/Green lifecycle with binlog replay compatibility.

69

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-engineered advisory skill body: highly actionable CLI guidance, strong destructive-operation safeguards, and an exemplary one-level-deep progressive disclosure structure backed by real bundle files. The main weakness is verbosity in the repeated per-scenario "Critical Facts" blocks, which inflate token cost without adding proportional signal.

Suggestions

Consolidate the five "Critical Facts to Always Surface" scenario blocks: factor the repeated patterns (engine detection via describe-db-instances, advisory-only stance, no-Data-API-for-MariaDB) into a shared "Critical Facts" reference and keep only scenario-unique facts inline to reduce token cost.

Tighten the Security Considerations list where it overlaps with the Production Instance Creation defaults (TLS, Secrets Manager, audit logging) to avoid restating the same guidance in two places.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes Claude's knowledge of RDS/AWS (it does not explain basic concepts), but the five "Critical Facts to Always Surface" blocks repeat similar guidance across scenarios and the RDS-vs-Aurora table plus the Security Considerations list restate several points, leaving room to tighten.

3 / 5

Actionability

Provides fully executable, copy-paste-ready CLI commands with exact flags for the common cases — e.g. the full `aws rds create-db-instance` block and the parameter-group/TLS configuration steps — and names specific commands like `create-blue-green-deployment` and `switchover-blue-green-deployment` rather than generic descriptions.

5 / 5

Workflow Clarity

Multi-step workflows are clearly sequenced with explicit validation checkpoints — prerequisite validation ("binlog_format=ROW, automated backups enabled"), a hard confirmation gate before the destructive switchover, and the "DO NOT bail out" rule that forces the full advisor workflow — satisfying the destructive-op validation requirement, with only minor gaps in some workflow references.

4 / 5

Progressive Disclosure

SKILL.md is a clear overview that routes via a Decision Guide table to four well-signaled one-level-deep workflow references (upgrade, commitment-pricing, proxy, bluegreen), each of which in turn points to engine-specific sub-references that exist as real files in ./references; navigation is easy and nesting stays one level deep from each main workflow.

5 / 5

Total

17

/

20

Passed

Description

91%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, highly specific description with comprehensive natural trigger terms and a clear niche carved out from Aurora and proprietary engines. Its only weakness is mild verbosity and the absence of an explicit "Use when..." trigger clause, relying instead on an embedded examples list to convey when to invoke it.

Suggestions

Add a short explicit trigger sentence such as "Use when the user asks about RDS MySQL, MariaDB, or PostgreSQL" to make the invocation condition unambiguous rather than implied via the example list.

Trim the long run-on keyword/workflow list; the verbatim user phrases already carry the trigger signal, so the parenthetical enumeration of covered workflows adds length without proportional value.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across five decision areas — "instance creation", "upgrade planning", "commitment pricing", "proxy evaluation", and "Blue/Green deployments" — plus concrete tooling like "describe-db-instances and describe-db-engine-versions upgrade-target workflow" and "RI versus DSP commitment pricing", giving comprehensive coverage.

5 / 5

Completeness

Clearly states the "what" ("Advises on Amazon RDS open-source engines...") and answers "when" via "Handles any RDS MySQL, MariaDB, or PostgreSQL question, including..." with concrete examples, but lacks an explicit "Use when..." clause, so the "when" is strong yet not as crisp as a dedicated trigger sentence.

4 / 5

Trigger Term Quality

Embeds verbatim natural user phrases users would actually say — "run the RDS upgrade advisor for my RDS MySQL instance", "should I buy reserved instances or a savings plan", "does RDS Proxy help when PgBouncer already runs" — plus synonyms (RI/DSP, create/provision).

5 / 5

Distinctiveness Conflict Risk

Explicitly scoped to RDS open-source engines (MySQL, MariaDB, PostgreSQL) and names adjacent skills ("For Aurora, use amazon-aurora"), carving a clear niche with minimal conflict risk against engine-specific skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
aws/agent-toolkit-for-aws
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.