CtrlK
BlogDocsLog inGet started
Tessl Logo

creating-amazon-aurora-db-cluster-with-instances

Creates a complete Amazon Aurora database cluster with instances, handling cluster creation, instance provisioning, and Secrets Manager password management in the proper sequence. Use when setting up new Aurora MySQL or PostgreSQL clusters with production-ready configuration.

70

Quality

86%

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

72%

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

Well-structured, token-efficient overview that delegates detail to a real reference file — strong progressive disclosure and conciseness. Weaker on actionability and workflow clarity at the body level, where guidance is directional and troubleshooting is vague rather than concrete.

Suggestions

Add one or two concrete commands to the Troubleshooting section (e.g., `aws rds describe-db-engine-versions --engine aurora-mysql` for engine-version checks) instead of bare "Verify..." / "Check that..." phrasing.

Surface an explicit validation checkpoint in the body — e.g., a short "Wait for cluster `available` status before adding the instance" step — so the database feedback loop is visible without opening the reference.

Trim the mild redundancy between the Overview and the Create section (both restate cluster-creation/instance-provisioning/Secrets-Manager) to tighten the body further.

DimensionReasoningScore

Conciseness

Lean body (~30 lines) that delegates the procedure to a reference rather than restating it; no explanation of concepts Claude already knows. Minor redundancy between Overview and the Create section keeps it just at 3.

3 / 3

Actionability

The body gives directional guidance ("follow the procedure exactly. See [reference]") and vague troubleshooting ("Verify the engine version...", "Check that the instance class is compatible...") with no concrete commands at the body level; executable detail lives only in the reference.

2 / 3

Workflow Clarity

High-level sequence is present ("creates an empty Aurora cluster first, then adds a database instance") and retry logic is mentioned, but explicit validation checkpoints are not shown in the body; for a database operation the rubric caps this at 2 without visible feedback loops.

2 / 3

Progressive Disclosure

Clean overview pointing to a single one-level-deep reference ("See [Aurora cluster creation procedure](references/...)") that exists as a real file, with well-organized Overview / Create / Troubleshooting sections and easy navigation.

3 / 3

Total

10

/

12

Passed

Description

100%

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: third-person voice, specific multi-action capability list, explicit "Use when" trigger covering both engines, and a distinctive niche. It would naturally surface when a user asks to set up an Aurora cluster.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "cluster creation, instance provisioning, and Secrets Manager password management" — rather than vague language.

3 / 3

Completeness

Explicitly answers both what ("Creates a complete Amazon Aurora database cluster with instances, handling...") and when ("Use when setting up new Aurora MySQL or PostgreSQL clusters...").

3 / 3

Trigger Term Quality

Covers natural terms users would say — "Amazon Aurora database cluster with instances", "Aurora MySQL or PostgreSQL clusters", "production-ready configuration".

3 / 3

Distinctiveness Conflict Risk

A clear niche — Aurora cluster/instance provisioning with Secrets Manager — unlikely to trigger for unrelated skills.

3 / 3

Total

12

/

12

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.