aws-cloudformation-dynamodb
AWS CloudFormation patterns for DynamoDB tables, GSIs, LSIs, auto-scaling, and streams. Use when creating DynamoDB tables with CloudFormation, configuring primary keys, local/global secondary indexes, capacity modes (on-demand/provisioned), point-in-time recovery, encryption, TTL, and implementing template structure with Parameters, Outputs, Mappings, Conditions, cross-stack references.
Install with Tessl CLI
npx tessl i github:giuseppe-trisciuoglio/developer-kit --skill aws-cloudformation-dynamodb72
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
100%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 an excellent skill description that comprehensively covers specific capabilities, includes abundant natural trigger terms that users would actually use, explicitly states both what the skill does and when to use it, and occupies a clear niche at the intersection of CloudFormation and DynamoDB. The description uses proper third-person voice and avoids vague language or buzzwords.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'creating DynamoDB tables', 'configuring primary keys', 'local/global secondary indexes', 'capacity modes', 'point-in-time recovery', 'encryption', 'TTL', and 'implementing template structure with Parameters, Outputs, Mappings, Conditions, cross-stack references'. | 3 / 3 |
Completeness | Clearly answers both what ('AWS CloudFormation patterns for DynamoDB tables, GSIs, LSIs, auto-scaling, and streams') and when ('Use when creating DynamoDB tables with CloudFormation, configuring primary keys...') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'CloudFormation', 'DynamoDB', 'GSIs', 'LSIs', 'auto-scaling', 'streams', 'primary keys', 'secondary indexes', 'on-demand', 'provisioned', 'point-in-time recovery', 'encryption', 'TTL', 'Parameters', 'Outputs', 'Mappings', 'Conditions', 'cross-stack references'. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche combining AWS CloudFormation specifically with DynamoDB; the combination of these two technologies plus specific features like GSIs, LSIs, and CloudFormation template elements makes it highly distinctive and unlikely to conflict with general AWS or database skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive, production-ready CloudFormation templates for DynamoDB but suffers from severe verbosity. The actionable code is excellent and copy-paste ready, but the document is bloated with repetitive patterns and lacks a clear quick-start path. The skill would benefit significantly from condensing common patterns and moving detailed examples to referenced files.
Suggestions
Reduce to a single comprehensive base template with inline comments showing variations (e.g., '# For on-demand: remove ProvisionedThroughput, set BillingMode: PAY_PER_REQUEST') instead of multiple full templates
Add a 'Quick Start' section at the top with a minimal working template (10-20 lines) before the comprehensive examples
Move detailed examples (auto-scaling, streams, encryption) to EXAMPLES.md as referenced, keeping only pattern summaries in the main file
Add an explicit deployment workflow section: 'aws cloudformation validate-template -> create-stack -> wait -> describe-stack-events -> verify resources'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 700+ lines with extensive repetition. Multiple complete templates repeat similar patterns (SSESpecification, ProvisionedThroughput, etc.). The 'When to Use' section lists obvious use cases Claude would infer. Much content could be condensed to patterns with variations noted. | 1 / 3 |
Actionability | Provides fully executable CloudFormation YAML templates that are copy-paste ready. Includes complete resource definitions, proper intrinsic functions, IAM roles, and all required properties. Code examples are production-quality, not pseudocode. | 3 / 3 |
Workflow Clarity | Templates are well-structured but lack explicit deployment workflows with validation steps. No guidance on 'validate template -> deploy -> verify -> rollback if needed' sequences. The drift detection section shows commands but doesn't integrate into a validation workflow. | 2 / 3 |
Progressive Disclosure | References REFERENCE.md and EXAMPLES.md at the end, but the main file is a monolithic wall of templates. Content that should be in separate files (auto-scaling, streams, encryption patterns) is all inline. The overview section doesn't provide quick-start guidance before diving into extensive templates. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
62%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (1155 lines); consider splitting into references/ and linking | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
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 |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 10 / 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.