aws-dynamodb

AWS DynamoDB single-table design, GSI patterns, SDK v3 TypeScript/Python

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/aws-dynamodb/SKILL.md

Quality

Content

65%

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

The content is highly actionable with comprehensive executable code across TypeScript, Python, and CLI, but it is verbose in places and ships as a single large file with no validation checkpoints around batch/transaction operations. Trimming known-concept explanations and splitting long reference material into separate files would improve the score-2 dimensions.

Suggestions

Remove the opening DynamoDB definition and the basic Key Concepts table (PK/SK/GSI/LSI/Item/Attribute) — Claude already knows these.

Add a validate-and-retry checkpoint pattern around BatchWrite and TransactWrite (e.g. check UnprocessedItems and re-submit) to satisfy the destructive/batch-operation feedback-loop guidance.

Move the Python (boto3) section and the detailed CRUD/transaction code into reference files (e.g. references/python.md, references/crud.md) linked from a concise overview.

Dimension	Reasoning	Score
Conciseness	The body is dominated by genuinely useful, executable code, but it opens with a redundant intro ("DynamoDB is a fully managed NoSQL database designed for single-digit millisecond performance…") and a Key Concepts table defining PK/SK/GSI/LSI that Claude already knows, fitting the score-2 "mostly efficient but includes some unnecessary explanation" anchor.	2 / 3
Actionability	It provides fully executable, copy-paste-ready TypeScript and Python code for CRUD, batch, transactions, GSI patterns, plus CLI and local-dev commands, matching the score-3 "fully executable code/commands; copy-paste ready" anchor.	3 / 3
Workflow Clarity	Sections are logically ordered but this is a reference catalog rather than a sequenced workflow, and the batch-write and TransactWrite operations include no validation/verification checkpoints, so per the scoring notes workflow clarity is capped at 2.	2 / 3
Progressive Disclosure	No bundle files exist and the ~660-line SKILL.md is a single monolithic file; sections are well-organized, but content that could be split out (the Python section, detailed CRUD/transaction examples) is all inline, matching the score-2 "some structure… content that should be separate is inline" anchor.	2 / 3
	Total	9 / 12 Passed

Description

57%

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

The description is specific and distinctive but reads as a noun-phrase topic list rather than an action statement, and it omits an explicit "Use when…" trigger clause from the description field. Adding verbs and natural trigger terms would raise the score-2 dimensions.

Suggestions

Lead with concrete action verbs, e.g. "Design DynamoDB single-table schemas, model GSI access patterns, and implement SDK v3 operations in TypeScript/Python."

Append an explicit trigger clause to the description, e.g. "Use when designing or querying DynamoDB tables, modeling NoSQL access patterns, or working with the AWS SDK."

Include common natural terms users say ("NoSQL", "tables", "AWS SDK") alongside "DynamoDB".

Dimension	Reasoning	Score
Specificity	Names the domain and concrete capability areas ("single-table design, GSI patterns, SDK v3 TypeScript/Python") but lists no action verbs, so it falls short of the score-3 "lists multiple specific concrete actions" anchor while remaining more concrete than vague score-1 examples.	2 / 3
Completeness	The description field answers "what" but contains no "Use when…" trigger clause — the when-guidance lives in a separate when-to-use field rather than the description itself, so per the judging guideline completeness is capped at 2.	2 / 3
Trigger Term Quality	"AWS DynamoDB" is a natural term a user would say, but common variations like "NoSQL", "tables", or "AWS SDK data operations" are absent, matching the score-2 "some relevant keywords but missing common variations" anchor.	2 / 3
Distinctiveness Conflict Risk	"AWS DynamoDB single-table design, GSI patterns, SDK v3" carves out a clear, specific niche with distinct triggers that is unlikely to fire for unrelated skills, matching the score-3 anchor.	3 / 3
	Total	9 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (670 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: alinaqi/claude-bootstrap
Path: skills/aws-dynamodb/SKILL.md
Commit: bb6195f

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