CtrlK
BlogDocsLog inGet started
Tessl Logo

amazon-aurora-mysql

Amazon Aurora MySQL — creates, modifies, and advises on Aurora MySQL clusters specifically (MySQL-compatible engine, Aurora serverless, parallel query). Trigger for Aurora MySQL cluster operations, ACU sizing, I/O-Optimized storage, commitment pricing, or MySQL upgrade planning. Aurora MySQL uses full (VPC-based) configuration — express configuration is PostgreSQL-only. For Aurora PostgreSQL, use amazon-aurora-postgresql instead. Contains safety guardrails and response templates that override defaults.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

An excellent router-style SKILL.md: a tight registry table, fully executable commands and verbatim safety templates, explicit validation and feedback loops for risky database operations, and a clean one-level-deep reference structure that keeps the body to routing and guardrails. The only improvement space is minor repetition (express-config caveat, reference-loading rule) that could be trimmed for token efficiency.

DimensionReasoningScore

Conciseness

Nearly every line is operational (CLI flags, tag syntax, refusal templates, IAM actions) with no basic-concept padding, but there are minor instances that could be trimmed: the express-configuration caveat is repeated three times (router intro, `create` row, Tier 1) and reference loading is stated both in Operating procedure step 2 and Global rule 5 — efficient with minor over-explanation, matching anchor 4 rather than the lean anchor 5.

4 / 5

Actionability

Guidance is fully executable: exact script invocations with all flags ("python3 scripts/acu_calculator.py estimate --instance <type> --cpu-p95 <val>..."), literal tag syntax ("--tags Key=created_by,Value=aurora-skill..."), verbatim two-paragraph refusal templates, specific IAM policy actions for AccessDenied, and a concrete requirements.json handoff procedure — copy-paste ready across the common cases.

5 / 5

Workflow Clarity

The Operating procedure is a clearly sequenced 5-step router with edge cases (multi-sub-skill requests, no match, script/MCP failure), and despite being a destructive-capable database skill it has explicit validation checkpoints: confirmation-before-mutation, Tier 2 risk-stating before confirm, Tier 3 refuse-and-redirect, and feedback loops ("show the error and suggest a fix before retrying", Throttling retry-once, sanity-check the handoff artifact before using it).

5 / 5

Progressive Disclosure

The body is a concise router over 5 sub-skills, each with a real one-level-deep references/{id}-instructions.md (all five verified present in references/), bulk material (pricing tables, worked examples, checklists) correctly pushed to bundle files, and scripts documented with a pointer to read --help on demand — clear overview with well-signaled references and easy navigation.

5 / 5

Total

19

/

20

Passed

Description

87%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 description: it states concrete capabilities, gives explicit trigger guidance across all five sub-domains, and proactively disambiguates against the sibling PostgreSQL skill. The only gaps are a handful of missing natural synonyms (RI, Savings Plan) and the slightly generic "advises on" verb.

DimensionReasoningScore

Specificity

"creates, modifies, and advises on Aurora MySQL clusters specifically" plus the enumerated domains ("ACU sizing, I/O-Optimized storage, commitment pricing, or MySQL upgrade planning") list several concrete actions with only minor gaps — "advises on" is somewhat generic and "parallel query" names a feature rather than an action, so it falls just below the comprehensive anchor 5.

4 / 5

Completeness

It explicitly answers both: what ("creates, modifies, and advises on Aurora MySQL clusters") and when ("Trigger for Aurora MySQL cluster operations, ACU sizing, I/O-Optimized storage, commitment pricing, or MySQL upgrade planning"), with concrete trigger phrases matching the anchor-5 example.

5 / 5

Trigger Term Quality

"Aurora MySQL cluster operations, ACU sizing, I/O-Optimized storage, commitment pricing, or MySQL upgrade planning" are natural phrases users would say, with common synonyms like "Reserved Instance", "Savings Plan", or "cost savings" absent — good coverage, a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

"For Aurora PostgreSQL, use amazon-aurora-postgresql instead" and "express configuration is PostgreSQL-only" explicitly disambiguate the closest competing skill, giving a clear niche with minimal conflict risk.

5 / 5

Total

18

/

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.

Validation — 15 / 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.