dynamodb-table-designer
Dynamodb Table Designer - Auto-activating skill for AWS Skills. Triggers on: dynamodb table designer, dynamodb table designer Part of the AWS Skills skill category.
36
3%
Does it follow best practices?
Impact
99%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/13-aws-skills/dynamodb-table-designer/SKILL.mdQuality
Discovery
7%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 description is extremely thin—it essentially repeats the skill name without describing any concrete capabilities, use cases, or trigger scenarios. It lacks both a 'what it does' explanation and a 'when to use it' clause, making it nearly useless for skill selection among multiple options.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Designs DynamoDB table schemas, defines partition and sort keys, configures global and local secondary indexes, sets read/write capacity modes.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about DynamoDB table design, NoSQL schema, partition keys, sort keys, GSIs, LSIs, or AWS database table configuration.'
Remove the duplicate trigger term ('dynamodb table designer' is listed twice) and expand with varied natural language terms users might actually say, such as 'DynamoDB schema', 'create DynamoDB table', 'key design', 'capacity planning'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Dynamodb Table Designer') but does not describe any concrete actions like creating tables, defining partition keys, configuring indexes, or setting capacity. It is essentially just a label repeated. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name and completely lacks a 'when should Claude use it' clause with explicit triggers. Both dimensions are very weak. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'dynamodb table designer' repeated twice. It misses natural user phrases like 'DynamoDB schema', 'partition key', 'sort key', 'GSI', 'create DynamoDB table', 'NoSQL table design', or 'AWS database'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'DynamoDB' and 'table designer' provides some specificity to a niche domain, but the lack of concrete actions or detailed triggers means it could overlap with other AWS or database-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template/placeholder with no actual content about DynamoDB table design. It contains only auto-generated boilerplate describing what the skill claims to do without providing any actionable guidance, code, patterns, or examples. It would provide zero value to Claude when attempting to help users with DynamoDB table design tasks.
Suggestions
Add concrete DynamoDB table design guidance: partition key selection strategies, GSI/LSI design patterns, single-table design examples with executable code (e.g., boto3 create_table calls with specific KeySchema and AttributeDefinitions).
Include a workflow for table design decisions: 1) Identify access patterns, 2) Choose partition/sort keys, 3) Design GSIs, 4) Validate with sample queries, 5) Set capacity mode — with specific examples at each step.
Add concrete code examples for common patterns (e.g., single-table design for an e-commerce app) with actual DynamoDB table definitions in CloudFormation YAML or boto3 Python.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill rather than teaching DynamoDB table design — these waste tokens on information Claude doesn't need.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains what triggers the skill and restates the title repeatedly but provides zero actual guidance on DynamoDB table design. Every token is wasted on meta-description rather than actionable content. | 1 / 3 |
Actionability | There are no concrete instructions, code examples, commands, or specific guidance on DynamoDB table design. Phrases like 'Provides step-by-step guidance' and 'Generates production-ready code' describe capabilities without demonstrating any of them. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. DynamoDB table design involves multi-step decisions (partition key selection, GSI design, capacity planning) but none are addressed or sequenced. | 1 / 3 |
Progressive Disclosure | No structure beyond boilerplate headings. No references to detailed guides, examples, or related documentation. The content is a shallow template with no depth or navigation to deeper resources. | 1 / 3 |
Total | 4 / 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 — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
4dee593
- 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.