aws-serverless

Proper Lambda function structure with error handling

Quality

46%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/aws-serverless/SKILL.md

The canonical home for this skill is aws-serverless in sickn33/agentic-awesome-skills

Quality

Content

43%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill offers concrete, domain-relevant code patterns but is undermined by malformed/truncated code blocks, a placeholder Sharp Edges table, and a generic When-to-Use boilerplate. Structure exists but there are no validation workflows or progressive file references.

Suggestions

Fix the code fences and complete the truncated blocks (Python Lambda handler, src/handlers/get.js, Python SQS handler) so every example is copy-paste executable.

Replace the Sharp Edges placeholder rows with real issue/severity/solution entries and write an explicit 'When to Use' section with concrete trigger conditions instead of generic boilerplate.

Move the bulk SAM templates and per-language handler examples into reference files (e.g. references/templates.md, references/handlers.md) and keep SKILL.md as a concise overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean code with brief 'When to use' notes, but wasted tokens appear in the broken Sharp Edges table (seven placeholder 'Issue' rows with header-fragment 'solutions') and duplicated/nested code fences, matching the 'mostly efficient but includes some unnecessary content that could be tightened' anchor.	3 / 5
Actionability	Concrete SAM templates and handler code are provided, but several blocks are truncated mid-statement (Python handler ends at '# Parse i', get.js at 'const item =', SQS Python at 'batch_ite') and fences are malformed, so guidance is incomplete rather than copy-paste ready, matching the 'some concrete guidance but incomplete' anchor.	3 / 5
Workflow Clarity	This is a patterns catalog with no real sequenced workflow or validation checkpoints, and the Sharp Edges guidance and 'When to Use' section ('This skill is applicable to execute the workflow or actions described in the overview') are placeholder/vague, matching the 'rough organization, many gaps, validation absent' anchor.	2 / 5
Progressive Disclosure	Sections (Lambda Handler, API Gateway, SQS, Anti-Patterns, Sharp Edges) provide structure, but all substantial code and templates are inlined in a single file with no one-level-deep references or bundle files, matching the 'some structure but content that should be separate is inline' anchor; the under-50-lines exception does not apply.	3 / 5
	Total	11 / 20 Passed

Description

48%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description names a specific domain and one concrete capability but lacks any 'Use when...' trigger guidance and natural synonyms, leaving completeness and trigger-term quality mid-range. It is distinct enough to avoid most conflicts but too thin to fully guide when Claude should invoke it.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when implementing AWS Lambda handlers, serverless API/event/scheduled functions, or when the user mentions Lambda, SAM, or serverless.'

Expand the action list beyond 'error handling' to concrete capabilities like building handlers, integrating API Gateway, and wiring SQS event sources.

Include common synonyms and file/runtime cues ('AWS Lambda', 'serverless', 'handler.js', 'Node.js/Python') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'Proper Lambda function structure with error handling' names the domain (Lambda functions) but the only named action is 'error handling'; 'structure' is generic rather than a concrete action, matching the anchor that names the domain with minimal/generic actions.	2 / 5
Completeness	It states a clear 'what' (Lambda function structure with error handling) but provides no 'when'/'Use when...' trigger guidance, so per the missing-trigger-clause cap it cannot exceed 3 and fits the 'clear what, missing when' anchor.	3 / 5
Trigger Term Quality	'Lambda function' is a natural term a user would say, but the description omits common variations and synonyms such as 'AWS', 'serverless', 'handler', or 'Node.js/Python', matching the anchor for some relevant keywords with missing synonyms.	3 / 5
Distinctiveness Conflict Risk	Being explicitly Lambda-specific gives it a clear niche with only minor overlap risk against a general AWS or error-handling skill, matching the 'mostly distinct; minor overlap risk' anchor rather than the fully distinct 5 which requires explicit trigger phrases.	4 / 5
	Total	12 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/aws-serverless/SKILL.md
Commit: debb2ec

Reviewed: 1 day 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.