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.
61
52%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent/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 for AWS serverless development. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill over others. The technical depth is appropriate and the scope is well-defined.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when building serverless applications on AWS, deploying Lambda functions, or optimizing serverless architecture'
Consider adding user-facing trigger phrases like 'serverless API', 'Lambda deployment', or 'event-driven AWS architecture' to capture more natural user requests
| 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, actionable 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 through the technology names. | 2 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'serverless', 'AWS', 'Lambda', 'API Gateway', 'DynamoDB', 'SQS', 'SNS', 'SAM', 'CDK', 'cold start'. Good coverage of terms developers naturally use when working with AWS serverless. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche focused specifically on AWS serverless architecture. The combination of Lambda, API Gateway, DynamoDB, and deployment tools creates a clear, non-conflicting scope that wouldn't overlap with general coding or other cloud skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is essentially an empty shell - a table of contents without any actual instructional content. While it correctly delegates to sub-skills, the main SKILL.md fails to provide any overview, quick start guidance, decision framework for choosing patterns, or concrete examples. A user reading this file learns nothing about AWS serverless development without clicking through to every sub-skill.
Suggestions
Add a Quick Start section with a minimal working Lambda + API Gateway example that demonstrates the core pattern
Include a decision matrix or flowchart explaining when to use each pattern (e.g., 'Use SQS pattern when: async processing needed, decoupling required')
Add brief 1-2 line descriptions next to each sub-skill link explaining what problem it solves
Include at least one concrete, executable code example in the main file to make it immediately actionable
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is extremely brief with no unnecessary explanation, but it's so minimal that it's essentially just a table of contents with no actual instructional content in the main file. | 2 / 3 |
Actionability | The skill provides zero concrete guidance, code, or commands - it's purely a list of links to sub-skills with no executable content or examples in the main file itself. | 1 / 3 |
Workflow Clarity | There is no workflow, sequence, or process described. The content is just a flat list of links with no indication of how to use them, when to apply each pattern, or how they relate to each other. | 1 / 3 |
Progressive Disclosure | The structure attempts progressive disclosure by linking to sub-skills, but the main file provides no overview, quick start, or context to help navigate which sub-skill to use when. The references are one-level deep but poorly signaled. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
90%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 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
332e58b
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.