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.

1.01x

Quality

Does it follow best practices?

Impact

99%

1.01x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./planned-skills/generated/13-aws-skills/dynamodb-table-designer/SKILL.md

Quality

Discovery

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 severely underdeveloped, essentially just restating the skill name without explaining capabilities or usage triggers. It provides no actionable information for Claude to determine when to select this skill, and the duplicate trigger term suggests a template that wasn't properly filled out.

Suggestions

Add specific actions the skill performs, e.g., 'Designs DynamoDB table schemas, configures partition and sort keys, sets up global secondary indexes, and estimates capacity requirements.'

Include a 'Use when...' clause with natural trigger terms like 'create DynamoDB table', 'NoSQL schema design', 'partition key strategy', 'AWS database setup', or 'capacity planning'.

Remove the duplicate trigger term and expand with variations users would naturally say when needing DynamoDB table design help.

Dimension	Reasoning	Score
Specificity	The description only names the tool ('Dynamodb Table Designer') without describing any concrete actions. There are no verbs indicating what the skill actually does - no mention of creating tables, defining schemas, configuring indexes, etc.	1 / 3
Completeness	The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. The 'Triggers on' section just repeats the skill name rather than providing meaningful trigger scenarios.	1 / 3
Trigger Term Quality	The trigger terms are redundant ('dynamodb table designer' listed twice) and overly specific. Missing natural variations users would say like 'create dynamodb table', 'nosql schema', 'partition key', 'DynamoDB design', or 'AWS database'.	1 / 3
Distinctiveness Conflict Risk	The mention of 'DynamoDB' provides some specificity that distinguishes it from generic database skills, but 'AWS Skills' category is broad and the lack of specific capabilities could cause confusion with other AWS-related skills.	2 / 3
	Total	5 / 12 Passed

Implementation

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

This skill is essentially a placeholder with no actual DynamoDB table design content. It contains only generic auto-generated boilerplate that could apply to any skill topic. There are no concrete instructions, code examples, design patterns, or actionable guidance for designing DynamoDB tables.

Suggestions

Add concrete DynamoDB table design workflow: 1) Identify access patterns, 2) Choose partition/sort keys, 3) Design GSIs/LSIs, 4) Validate with sample queries

Include executable code examples for creating tables with boto3 or CloudFormation/CDK templates

Provide specific examples of single-table design patterns with sample entity schemas and access pattern mappings

Add guidance on capacity planning (on-demand vs provisioned) and cost optimization considerations

Dimension	Reasoning	Score
Conciseness	The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual DynamoDB-specific information.	1 / 3
Actionability	There is zero concrete guidance - no code, no commands, no specific DynamoDB table design patterns, no examples of partition keys, sort keys, GSIs, or access patterns. The content describes rather than instructs.	1 / 3
Workflow Clarity	No workflow is provided whatsoever. DynamoDB table design involves specific steps (identify access patterns, choose keys, design GSIs, etc.) but none are mentioned or sequenced.	1 / 3
Progressive Disclosure	The content is a monolithic block of generic text with no structure pointing to detailed materials, no references to examples, schemas, or advanced topics. There's nothing to disclose progressively because there's no substantive content.	1 / 3
	Total	4 / 12 Passed

Validation

81%

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 — 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

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: e9f9c93

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