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 description excels at specificity and trigger term coverage, listing concrete AWS serverless technologies that developers would naturally reference. 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 to a clear niche, reducing conflict risk with other skills.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about building serverless applications on AWS, deploying Lambda functions, configuring API Gateway, or optimizing cold starts.'

Consider adding common user phrasings like 'serverless deployment', 'AWS Lambda timeout', 'event-driven architecture', or 'infrastructure as code' to broaden trigger term coverage.

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 technologies listed.	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 seeking help with serverless AWS applications.	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 unlikely to conflict with general cloud or coding 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 — it tries to be a comprehensive reference document rather than a concise skill file, explaining many concepts Claude already knows and duplicating examples across languages. The lack of progressive disclosure (no bundle files, no external references) and missing deployment validation workflows are significant weaknesses.

Suggestions

Split content into separate files: move Sharp Edges to SHARP_EDGES.md, Validation Checks to VALIDATION.md, and individual patterns (SQS, DynamoDB Streams, CDK) to their own files, with clear one-level-deep references from SKILL.md.

Remove duplicate language examples — pick one primary language per pattern and reference the alternative in a separate file, or note that the same pattern applies to Python/Node.js without full duplication.

Trim explanations of concepts Claude already knows (e.g., what cold starts are, what DynamoDB streams do, how API Gateway works) and focus only on the specific configuration values and gotchas.

Add explicit deployment validation workflows with feedback loops, e.g., 'sam build → sam validate → sam local invoke → verify output → sam deploy --guided → verify stack status'.

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 (API Gateway response format, basic error handling, how DynamoDB streams work) is knowledge Claude already possesses. The skill reads like a tutorial/reference manual rather than a concise skill file.	1 / 3
Actionability	The code examples are fully executable and copy-paste ready — complete SAM templates, working Lambda handlers with proper imports, specific CLI commands, and concrete configuration snippets. Every pattern includes real, runnable code rather than pseudocode.	3 / 3
Workflow Clarity	Individual patterns are well-structured with 'When to use' guidance and best practices, but there are no explicit validation checkpoints or feedback loops for deployment workflows. The SAM local development section lists commands but doesn't sequence them into a validate-then-deploy workflow with error recovery steps.	2 / 3
Progressive Disclosure	This is a monolithic wall of text with no references to external files despite being 700+ lines. The cold start optimization, sharp edges, validation checks, and each pattern could easily be split into separate referenced files. With no bundle files provided, all content is inlined in a single massive document.	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 (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: 431bfad

Reviewed: 2 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.