dynamodb

AWS DynamoDB NoSQL database for scalable data storage. Use when designing table schemas, writing queries, configuring indexes, managing capacity, implementing single-table design, or troubleshooting performance issues.

1.00x

Quality

75%

Does it follow best practices?

Impact

93%

1.00x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/dynamodb/SKILL.md

Quality

Discovery

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description that clearly identifies the technology (AWS DynamoDB), explains its purpose, and provides explicit trigger conditions. The main weakness is that trigger terms could include more user-friendly variations and common DynamoDB-specific terminology that users might naturally mention.

Suggestions

Add common DynamoDB-specific terms users might mention: 'partition key', 'sort key', 'GSI', 'LSI', 'read/write capacity units', 'on-demand mode'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'designing table schemas, writing queries, configuring indexes, managing capacity, implementing single-table design, troubleshooting performance issues' - these are all distinct, actionable capabilities.	3 / 3
Completeness	Clearly answers both what ('AWS DynamoDB NoSQL database for scalable data storage') and when with explicit 'Use when...' clause listing six specific trigger scenarios.	3 / 3
Trigger Term Quality	Includes good technical terms like 'DynamoDB', 'table schemas', 'queries', 'indexes', 'single-table design', but missing common user variations like 'dynamo', 'NoSQL queries', 'partition key', 'sort key', 'GSI', 'LSI', or '.dynamodb'.	2 / 3
Distinctiveness Conflict Risk	Highly distinctive with 'AWS DynamoDB' as a clear niche identifier, plus DynamoDB-specific concepts like 'single-table design' and 'capacity' that wouldn't overlap with other database skills.	3 / 3
	Total	11 / 12 Passed

Implementation

64%

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

This is a solid DynamoDB reference skill with excellent actionable code examples covering common operations. The main weaknesses are some unnecessary introductory content that Claude already knows, and the monolithic structure that could benefit from splitting into focused sub-documents. Adding explicit validation workflows for operations like table creation and batch writes would improve reliability.

Suggestions

Remove the introductory paragraph explaining what DynamoDB is - Claude already knows this

Add validation steps after table creation (e.g., 'Verify table is ACTIVE: aws dynamodb describe-table --table-name Users')

Split CLI Reference and Troubleshooting sections into separate linked files to improve progressive disclosure

Add error handling and verification for batch operations (e.g., checking UnprocessedItems in batch_write response)

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with good use of tables and code examples, but includes some unnecessary explanations Claude already knows (e.g., 'Amazon DynamoDB is a fully managed NoSQL database service providing fast, predictable performance at any scale'). The core concepts section explains basic DynamoDB concepts that Claude is familiar with.	2 / 3
Actionability	Excellent executable code examples throughout - both AWS CLI and boto3 with complete, copy-paste ready snippets. CRUD operations, queries, batch operations, and troubleshooting all include concrete, runnable code.	3 / 3
Workflow Clarity	While individual operations are clear, there's no explicit validation workflow for multi-step processes. For example, table creation doesn't include verification steps, and batch operations lack error handling/retry guidance beyond the exponential backoff example.	2 / 3
Progressive Disclosure	The content is well-organized with a table of contents and clear sections, but it's a monolithic document (~300 lines) that could benefit from splitting detailed sections (like CLI Reference, troubleshooting) into separate files. References are external links only, not internal skill documentation.	2 / 3
	Total	9 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: itsmostafa/aws-agent-skills
Commit: 5df6da7

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