CtrlK
BlogDocsLog inGet started
Tessl Logo

amazon-documentdb

Manages Amazon DocumentDB end-to-end — serverless-on-8.0 cluster setup, TLS/VPC/driver config, flexible-schema and vector-search data modeling, MongoDB compatibility assessment, DMS-based migration, slow-query diagnosis, major version upgrades (4.0→5.0→8.0), Well-Architected reviews (41-check wa_review.py), cost estimation, and security hardening. Retrieve for every DocumentDB question and when the user asks to set up or migrate MongoDB to AWS — DocumentDB is AWS's MongoDB-compatible managed database. Triggers: JSON document store, document database, MongoDB on AWS, Nested fields, Lambda cannot connect, TLS handshake, VPC port 27017, IAM auth, Secrets Manager, encryption at rest, $graphLookup, flexible schema, COLLSCAN, compound index, DMS migration, CDC cutover, $vectorSearch, RAG, Global Clusters, DR replication, cost sizing, audit, health check, production-readiness.

74

Quality

92%

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

85%

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

A well-structured, highly actionable executor skill with clear workflows, validation checkpoints, and clean progressive disclosure into verified bundle files. The main weakness is conciseness — the body is long and several MUST/NEVER lists and critical-facts sections overlap material that already lives in the references.

Suggestions

Trim the 'Critical Facts to Always Surface' MUST-list-all-N-facts blocks, or move them into the matching reference files and keep only a one-line pointer plus the fact count in SKILL.md, to reduce overlap with references.

Collapse the repeated MUST/NEVER constraint phrasing in 'Common Tasks → Execute the Workflow' into a single compact constraint block; the same rules are restated across several sections.

Move the full 'Resource tagging' worked example into references/connection.md and keep only the --tags syntax template in the body.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes competence (exact CLI commands, no 'what is a database' filler), but at ~214 lines it is padded — the repeated 'MUST tell the user ALL of the following N facts' lists and restated MUST/NEVER constraints overlap with the bundled references and could be tightened.

2 / 3

Actionability

Fully executable, copy-paste-ready guidance throughout — exact 'aws docdb create-db-cluster' / 'create-db-instance' commands with '--serverless-v2-scaling-configuration', DMS endpoint '--ssl-mode verify-full --certificate-arn' flags, 'db.collection.find({...}).explain()', and RDS --tags syntax.

3 / 3

Workflow Clarity

Multi-step processes are clearly sequenced: a routing decision-guide table, explicit pipeline order, a numbered 'Common Tasks 1–4' flow, and validation/confirmation checkpoints for destructive ops ('MUST pause, state the consequence, and wait for explicit confirmation').

3 / 3

Progressive Disclosure

Clear overview with a well-signaled routing table pointing to one-level-deep references (connection.md, schema-advisor.md, migration.md, etc.), all of which exist, plus scripts/wa_review.py; content is appropriately split rather than nested.

3 / 3

Total

11

/

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, third-person description that states specific capabilities and gives explicit 'Use when' trigger guidance with a long list of natural keyword phrases. It is on the verbose/padded side but every trigger term is concrete and domain-relevant.

DimensionReasoningScore

Specificity

Lists many specific concrete actions — 'serverless-on-8.0 cluster setup, TLS/VPC/driver config, flexible-schema and vector-search data modeling, DMS-based migration, slow-query diagnosis, major version upgrades (4.0→5.0→8.0)' — matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both 'what' (the full capability list) and 'when' — 'Retrieve for every DocumentDB question and when the user asks to set up or migrate MongoDB to AWS' plus an explicit 'Triggers:' clause, so it is not capped at 2.

3 / 3

Trigger Term Quality

The 'Triggers:' list gives broad natural-phrase coverage a user would say — 'document database, MongoDB on AWS, Lambda cannot connect, TLS handshake, VPC port 27017, COLLSCAN, DMS migration, CDC cutover, $vectorSearch, RAG'.

3 / 3

Distinctiveness Conflict Risk

Clearly niched to DocumentDB ('DocumentDB is AWS's MongoDB-compatible managed database') with distinct, domain-specific triggers unlikely to fire for sibling skills (aurora, neptune, rds-* are listed as related).

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.