Specialized skill for building production-ready serverless applications on AWS. Covers Lambda functions, API Gateway, DynamoDB, SQS/SNS event-driven patterns, SAM/CDK deployment, and cold start optimization.
54
62%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/aws-serverless/SKILL.mdQuality
Discovery
82%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 a strong description with excellent specificity and trigger term coverage across AWS serverless technologies. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know precisely when to select this skill. The description is well-scoped to a clear niche, making it highly distinguishable from other skills.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about building serverless apps on AWS, deploying Lambda functions, configuring API Gateway, working with DynamoDB, or optimizing cold starts.'
Consider adding file extension or framework triggers like '.yaml', 'template.yaml', 'serverless.yml', or 'cdk.json' to capture more natural user contexts.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and technologies: Lambda functions, API Gateway, DynamoDB, SQS/SNS event-driven patterns, SAM/CDK deployment, and cold start optimization. These are concrete, identifiable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific AWS serverless capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the domain context, which per the rubric caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'serverless', 'AWS', 'Lambda', 'API Gateway', 'DynamoDB', 'SQS', 'SNS', 'SAM', 'CDK', 'cold start', 'event-driven'. These cover a wide range of terms a user would naturally use when seeking help with AWS serverless development. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: AWS serverless applications specifically. The combination of Lambda, API Gateway, DynamoDB, SAM/CDK, and cold start optimization creates a very specific domain that is unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is comprehensive and highly actionable with excellent executable code examples across multiple AWS serverless patterns. However, it is severely over-long and monolithic — it tries to be an exhaustive reference document rather than a lean skill file. The lack of any progressive disclosure structure (no bundle files, no references to external documents) means all ~600+ lines load into context every time, wasting significant token budget on content Claude largely already knows.
Suggestions
Split content into separate files: keep SKILL.md as a concise overview (~50-80 lines) with links to PATTERNS.md, SHARP-EDGES.md, and VALIDATION.md for detailed content.
Remove redundant dual-language examples — pick one primary language per pattern and mention the other is analogous, or put the second language version in a referenced file.
Trim explanations of concepts Claude already knows (e.g., what cold starts are, what DynamoDB Streams do, basic error handling patterns) and focus only on AWS-specific gotchas and non-obvious configuration.
Add explicit validation checkpoints to the SAM deployment workflow (e.g., 'verify sam build succeeds before sam deploy', 'check sam local invoke output before deploying to production').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~600+ lines, with extensive code examples in multiple languages (Node.js AND Python) for the same patterns, full SAM/CDK templates, and numerous sharp edges sections that read like documentation rather than a concise skill. Much of this content (API Gateway response format, basic error handling, how DynamoDB streams work) is knowledge Claude already possesses. The validation checks section is essentially a linting ruleset that adds significant bulk. | 1 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code examples throughout — complete Lambda handlers, SAM templates, CDK stacks, CLI commands, and test event JSON. Every pattern includes concrete, runnable code with proper imports and configuration. | 3 / 3 |
Workflow Clarity | While individual patterns are well-structured, there are no explicit validation checkpoints or feedback loops for multi-step deployment workflows. The SAM local development section lists commands but doesn't sequence them with validation steps (e.g., 'verify build succeeded before deploying'). The sharp edges sections describe problems and fixes but lack structured verify-then-proceed workflows. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no references to external files despite being 600+ lines covering Lambda handlers, API Gateway, SQS, DynamoDB Streams, cold starts, SAM, CDK, sharp edges, and validation checks. The content desperately needs to be split into separate files (e.g., PATTERNS.md, SHARP-EDGES.md, VALIDATION.md) with the SKILL.md serving as a concise overview with navigation links. | 1 / 3 |
Total | 7 / 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 |
|---|---|---|
skill_md_line_count | SKILL.md is long (1344 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
f5dc9e3
Table of Contents
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.