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.

Quality

62%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/antigravity-aws-serverless/SKILL.md

Quality

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 uses appropriate third-person voice and avoids vague language.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about AWS serverless architecture, Lambda functions, API Gateway setup, DynamoDB modeling, or deploying with SAM/CDK.'

Consider adding file extension or framework triggers like '.yaml SAM templates', 'serverless.yml', or 'template.yaml' 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' (building serverless apps with specific AWS services), but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the technology names. Per rubric guidelines, missing 'Use when...' 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 working with AWS serverless would naturally use.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche: AWS serverless 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 general coding skills or other cloud platform 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 demonstrates strong actionability with complete, executable code examples across multiple AWS serverless patterns and languages. However, it is severely over-long and monolithic — cramming handler patterns, deployment templates, sharp edges, validation rules, and collaboration info into one file without any progressive disclosure. Much of the content explains things Claude already knows (basic error handling patterns, what cold starts are, how to use axios), wasting significant token budget.

Suggestions

Split content into separate files: SKILL.md as a concise overview with links to PATTERNS.md, SHARP-EDGES.md, VALIDATION.md, and CDK.md for detailed content.

Remove redundant explanations Claude already knows (e.g., what cold starts are, why OOM happens, basic HTTP timeout concepts) and keep only the AWS-specific configuration details and gotchas.

Eliminate dual-language (Node.js + Python) examples for every pattern — pick one primary language per pattern and note the other is analogous, or move alternate language versions to a separate reference file.

Add explicit deployment workflow sequences with validation checkpoints, e.g., 'sam build → sam validate → sam local invoke → verify output → sam deploy --guided → verify stack status'.

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~700+ lines, providing full handler implementations in both Node.js and Python for multiple patterns, extensive sharp edges sections, and validation checks that largely restate common knowledge Claude already possesses. Much of this content (e.g., basic Lambda handler structure, API Gateway response format, how to use axios timeouts) doesn't need this level of detail.	1 / 3
Actionability	The code examples are fully executable and copy-paste ready — complete SAM templates, Lambda handlers in multiple languages, CDK stacks, CLI commands, and test event JSON files. Every pattern includes concrete, working code rather than pseudocode.	3 / 3
Workflow Clarity	While individual patterns are well-structured, there are no explicit validation checkpoints or feedback loops for deployment workflows. The SAM local development section lists commands but doesn't sequence them with validation steps (e.g., 'build → validate → test locally → deploy → verify'). The sharp edges sections describe fixes but lack verify-after-fix steps.	2 / 3
Progressive Disclosure	This is a monolithic wall of text with no references to external files. All patterns, sharp edges, validation checks, and collaboration notes are inlined in a single massive document. Content like the full sharp edges catalog, validation checks, and detailed CDK/SAM patterns should be split into separate referenced files.	1 / 3
	Total	7 / 12 Passed

Validation

81%

Warnings & errors only

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 (1340 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: f1697b6

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.