aws-dynamodb-best-practices

AWS DynamoDB best practices for table design and data modeling. Use when designing DynamoDB schemas, choosing partition/sort keys, creating secondary indexes, modeling relationships, handling time series data, or optimizing query patterns. Triggers on tasks involving DynamoDB table creation, key design, GSI/LSI configuration, single-table design, adjacency lists, write sharding, or capacity planning. Does not cover DynamoDB SDK/API reference or CloudFormation/Terraform resource definitions.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

80%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-organized, token-efficient design reference with excellent progressive disclosure and a strong corrective 'Common Mistakes' section. Its main gap is the absence of explicit validation/verification checkpoints around the batch and transactional operations it covers.

Suggestions

Add a short validation/verification note near the Concurrency Control and Global Tables sections — e.g., a checklist for confirming transaction preconditions and verifying write-mode routing before bulk operations — to lift workflow clarity above the destructive/batch cap of 3.

Include one or two copy-paste-ready code snippets (e.g., a ConditionExpression for optimistic locking, a Query with begins_with) to move actionability from mostly-executable to fully copy-paste ready.

Consider an explicit numbered design workflow (enumerate access patterns → pick keys → choose indexes → validate against query patterns) to give the design process a clear sequence with checkpoints.

Dimension	Reasoning	Score
Conciseness	Lean and efficient — verdict tables and compact key-pattern examples assume Claude's competence and avoid restating what DynamoDB is; every section earns its tokens, matching the score-5 anchor.	5 / 5
Actionability	Mostly concrete and actionable — real PK/SK layouts, a clear GSI-vs-LSI decision rule, and a 'Common Mistakes' fix table — but design guidance rather than copy-paste executable code, leaving minor gaps versus the score-5 anchor.	4 / 5
Workflow Clarity	Content is topically sequenced rather than a multi-step workflow, and while the 'Common Mistakes' table offers corrective feedback, there are no explicit validation checkpoints for the batch/destructive operations (TransactWriteItems, BatchWriteItem) it discusses, consistent with the score-3 cap.	3 / 5
Progressive Disclosure	Clear overview in SKILL.md with five well-signaled one-level-deep references, each summarized inline and verified to exist as real files in references/, matching the score-5 anchor.	5 / 5
	Total	17 / 20 Passed

Description

100%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 model description: third-person, concrete, comprehensive, with both positive triggers and an explicit out-of-scope boundary. It tells Claude exactly what the skill covers and when to invoke it.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'designing DynamoDB schemas, choosing partition/sort keys, creating secondary indexes, modeling relationships, handling time series data, or optimizing query patterns' — with comprehensive coverage, matching the score-5 anchor.	5 / 5
Completeness	Explicitly answers both 'what' (table design and data modeling best practices) and 'when' via both 'Use when...' and 'Triggers on...' clauses with concrete trigger phrases, matching the score-5 anchor.	5 / 5
Trigger Term Quality	Comprehensive natural trigger terms including synonyms and acronyms users actually say — 'partition/sort keys', 'secondary indexes', 'GSI/LSI configuration', 'single-table design', 'adjacency lists', 'write sharding', 'capacity planning'.	5 / 5
Distinctiveness Conflict Risk	Clear DynamoDB-design niche with distinct triggers and an explicit negative boundary ('Does not cover DynamoDB SDK/API reference or CloudFormation/Terraform resource definitions'), minimizing conflict risk with adjacent skills.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: provectus/awos-recruitment
Path: registry/skills/aws-dynamodb-best-practices/SKILL.md
Commit: 556fe34

Reviewed: 14 days ago

Table of Contents

Discovery Implementation Validation

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.