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 opt...
Install with Tessl CLI
npx tessl i github:boisenoise/skills-collections --skill aws-serverless60
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
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 description excels at specificity and trigger term coverage with comprehensive AWS serverless terminology. However, it lacks an explicit 'Use when...' clause and appears truncated, which limits its completeness. Adding explicit trigger guidance would make this a strong skill description.
Suggestions
Add a 'Use when...' clause with trigger phrases like 'Use when building serverless apps, deploying to AWS Lambda, or working with API Gateway, DynamoDB, or event-driven architectures'
Complete the truncated text (currently ends with 'opt...') to ensure all capabilities are fully described
| 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 description appears truncated (ends with 'opt...') and provides no explicit guidance on when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'serverless', 'AWS', 'Lambda', 'API Gateway', 'DynamoDB', 'SQS', 'SNS', 'SAM', 'CDK', 'cold start'. These are terms developers naturally use when working with AWS serverless. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear AWS serverless niche. The specific combination of Lambda, API Gateway, DynamoDB, and SAM/CDK creates a unique fingerprint unlikely to conflict with general coding or other cloud provider skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
29%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has a solid foundation with real-world serverless patterns and SAM templates, but suffers from significant quality issues: truncated code examples that aren't copy-paste ready, a completely broken Sharp Edges table, and no deployment workflow or validation steps. The skill description promises coverage of SAM/CDK deployment and cold start optimization, but the content doesn't deliver on these topics.
Suggestions
Complete all truncated code examples - every code block should be fully executable and copy-paste ready
Fix the Sharp Edges table by replacing 'Issue' placeholders with actual issues (e.g., 'Cold start latency', 'Timeout errors') and provide proper solutions instead of just headers
Add a deployment workflow section with explicit steps: sam build -> sam local invoke (test) -> sam deploy -> verify in console
Split detailed patterns into separate reference files (e.g., SQS_PATTERNS.md, API_GATEWAY.md) and add a Quick Start section with the simplest possible Lambda deployment
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill provides useful code examples without excessive explanation of basic concepts, but includes some redundancy (both Node.js and Python versions for each pattern) and several code blocks are truncated mid-implementation, wasting tokens on incomplete content. | 2 / 3 |
Actionability | Contains concrete, executable code patterns and SAM templates, but multiple code examples are cut off mid-function (e.g., Python handler, get.js, processor.py), making them non-executable and incomplete. The Sharp Edges table has broken formatting with 'Issue' placeholders instead of actual issues. | 2 / 3 |
Workflow Clarity | No deployment workflow is provided - missing steps for how to actually deploy these templates (sam build, sam deploy). No validation checkpoints for testing Lambda functions locally or verifying deployments. The patterns are isolated without guidance on how they connect. | 1 / 3 |
Progressive Disclosure | Content is a monolithic wall of code with no references to external files for detailed topics like cold start optimization, CDK deployment, or SNS patterns mentioned in the description. No clear navigation structure or links to advanced materials. | 1 / 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 | |
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.