aws-serverless
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/antigravity-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 exactly when to select this skill. The description is well-scoped and distinctive, making it unlikely to conflict with 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.'
| 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.
The skill is highly actionable with excellent, executable code examples covering a broad range of AWS serverless patterns. However, it is severely over-long and monolithic — cramming what should be a multi-file reference into a single ~700-line document that explains many concepts Claude already knows. The lack of progressive disclosure and missing validation-oriented workflows significantly reduce its effectiveness as a skill file.
Suggestions
Split content into separate files: move Sharp Edges to SHARP_EDGES.md, Validation Checks to VALIDATION.md, CDK patterns to CDK.md, and keep SKILL.md as a concise overview with references to these files.
Remove duplicate language examples — pick one primary language per pattern (e.g., Node.js for handlers) and reference a separate file for alternative language versions.
Add explicit deployment workflows with validation checkpoints, e.g., 'sam build → sam validate → sam local invoke (verify output) → sam deploy --guided → verify stack outputs'.
Trim explanatory text that Claude already knows (e.g., what cold starts are, what DynamoDB Streams do, what OOM means) and focus only on the specific configurations and gotchas.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 700+ lines with extensive code examples in multiple languages (Node.js AND Python) for the same patterns, full SAM/CDK templates, and exhaustive sharp edges sections. Much of this content (basic Lambda handler structure, API Gateway response format, DynamoDB client initialization) is knowledge Claude already possesses. The skill reads like a tutorial/reference manual rather than a concise skill file. | 1 / 3 |
Actionability | All code examples are fully executable and copy-paste ready — complete SAM templates, working Lambda handlers in both Node.js and Python, CDK stacks in TypeScript, CLI commands, and test event JSON files. Specific configurations like VisibilityTimeout ratios and memory settings are concrete and immediately usable. | 3 / 3 |
Workflow Clarity | Individual patterns are well-structured with 'When to use' annotations and best practices, but there's no clear end-to-end workflow with validation checkpoints. The SAM local development section lists commands but doesn't sequence them into a validate-then-deploy workflow. The sharp edges sections describe problems and fixes but lack explicit feedback loops (e.g., 'verify the fix worked by checking X'). | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no bundle files and no references to external documents. All content — handler patterns, SAM templates, CDK stacks, 8 sharp edges, 10 validation checks, and collaboration delegation — is inlined in a single massive file. The cold start optimization, sharp edges, and validation checks sections could easily be split into separate referenced files. | 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 | |
- Repository
- boisenoise/skills-collections
- Commit
8ac11ab
- 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.