dynamodb-table-designer
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill dynamodb-table-designerDynamodb Table Designer - Auto-activating skill for AWS Skills. Triggers on: dynamodb table designer, dynamodb table designer Part of the AWS Skills skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%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 over others. The redundant trigger terms and lack of concrete actions make this description nearly useless for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Design DynamoDB table schemas, configure partition and sort keys, set up global secondary indexes, estimate capacity units'
Include a 'Use when...' clause with natural trigger terms like 'create DynamoDB table', 'NoSQL schema design', 'partition key strategy', 'AWS database setup'
Remove the duplicate trigger term and expand to include 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 'table designer' is vague enough that it could conflict with other database design or AWS skills without clearer capability boundaries. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual DynamoDB table design guidance. It lacks any concrete information about partition keys, sort keys, GSIs, access patterns, capacity modes, or single-table design - all critical topics for DynamoDB table design. The content would be useless for helping Claude perform actual DynamoDB table design tasks.
Suggestions
Add concrete examples of DynamoDB table designs with partition key and sort key patterns (e.g., PK=USER#<id>, SK=ORDER#<timestamp>)
Include a workflow for table design: 1) Document access patterns, 2) Design primary key, 3) Plan GSIs, 4) Validate with sample queries
Provide executable AWS CLI or SDK code for creating tables with specific configurations
Add guidance on single-table vs multi-table design decisions with concrete criteria
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no DynamoDB-specific commands, no table design patterns, no partition key strategies. The content describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. DynamoDB table design involves specific steps (access pattern analysis, key design, GSI planning) 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 resources, examples, or reference materials for DynamoDB table design. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 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.