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

100%

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

100%

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

A well-structured, token-efficient reference that pairs concrete decision guidance with one-level-deep pointers to verified bundle files. It assumes Claude's competence and avoids padding while remaining highly actionable.

Dimension	Reasoning	Score
Conciseness	Lean, opinionated prose using tables and tight code blocks; it assumes Claude's competence and avoids explaining NoSQL basics beyond a single pointed reminder. Every section earns its tokens.	3 / 3
Actionability	Concrete decision tables (partition-key verdicts, GSI-vs-LSI conditions, MREC-vs-MRSC), specific thresholds (10 GB, 400 KB, ~100 KB, 100 items/4 MB, 2x WCU), and copy-ready PK/SK layouts give directly applicable guidance.	3 / 3
Workflow Clarity	This is a design-conventions skill with no multi-step destructive workflow; its decision guidance (when to use LSI, which global-table mode, which large-item strategy) is unambiguous and the Common Mistakes table provides clear fixes.	3 / 3
Progressive Disclosure	Each major section ends with a well-signaled one-level-deep 'See references/...' pointer, all five referenced files exist, and a consolidated Reference Files index closes the document for easy navigation.	3 / 3
	Total	12 / 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 precise, third-person description with concrete capabilities, natural trigger terms, and explicit when-to-use plus out-of-scope guidance. It cleanly satisfies all four dimensions.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions — 'designing DynamoDB schemas, choosing partition/sort keys, creating secondary indexes, modeling relationships, handling time series data' plus 'GSI/LSI configuration, single-table design, adjacency lists, write sharding, or capacity planning' — matching the multi-action anchor.	3 / 3
Completeness	Explicitly answers both 'what' ('AWS DynamoDB best practices for table design and data modeling') and 'when' ('Use when designing...', 'Triggers on tasks involving...'), plus a negative-scope clause.	3 / 3
Trigger Term Quality	Natural terms a user would say are well covered: 'partition/sort keys', 'secondary indexes', 'GSI/LSI', 'single-table design', 'capacity planning', with explicit 'Use when...' and 'Triggers on...' phrasing.	3 / 3
Distinctiveness Conflict Risk	Clear DynamoDB-design niche with distinct triggers and an explicit 'Does not cover DynamoDB SDK/API reference or CloudFormation/Terraform resource definitions' boundary, making wrong-skill conflicts unlikely.	3 / 3
	Total	12 / 12 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: c97cd8e

Reviewed: 4 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.