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.
Install with Tessl CLI
npx tessl i github:itsmostafa/aws-agent-skills --skill dynamodbOverall
score
77%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 terminology users might mention: 'partition key', 'sort key', 'GSI', 'LSI', 'DDB', or 'dynamo'
| 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 conflict 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, actionable DynamoDB reference with excellent code examples covering common operations. The main weaknesses are verbosity in introductory sections, missing validation/error handling in workflows (especially for batch operations), and a monolithic structure that could benefit from splitting advanced topics into separate files.
Suggestions
Remove the introductory paragraph explaining what DynamoDB is - Claude already knows this
Add explicit error handling and validation for batch operations (check UnprocessedItems in response, implement retry logic)
Split advanced topics (single-table design patterns, DAX setup, transactions) into separate reference files with clear links
Add a validation step after table creation showing how to verify the table is ready and has correct configuration
| 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 could be more condensed. | 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 | Individual operations are clear, but multi-step workflows lack explicit validation checkpoints. For example, table creation doesn't verify success beyond wait_until_exists(), and batch operations don't include error handling for partial failures or retry logic for unprocessed items. | 2 / 3 |
Progressive Disclosure | Good internal structure with table of contents and clear sections, but the document is quite long (~300 lines) with all content inline. Advanced topics like single-table design, DAX configuration, and transaction patterns could be split into separate reference files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
- 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.