aws-serverless

Proper Lambda function structure with error handling

Quality

18%

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

14%Scale 1-3

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

This skill suffers from significant quality issues: multiple truncated code blocks that are not executable, a broken sharp edges table filled with placeholder text, no deployment workflow or validation steps, and excessive verbosity for patterns Claude already understands. The content reads like an incomplete draft rather than a polished skill file.

Suggestions

Complete all truncated code blocks or remove them entirely - half-finished examples are worse than no examples since they waste tokens and provide no actionable guidance.

Fix the sharp edges table by replacing placeholder 'Issue' text with actual issues and providing concrete solutions instead of bare section headers.

Add a clear deployment workflow with validation steps (e.g., 'sam build -> sam validate -> sam deploy -> verify endpoints') to guide Claude through the full process.

Split the three large patterns into separate referenced files (e.g., LAMBDA_HANDLER.md, API_GATEWAY.md, SQS_PATTERN.md) and keep SKILL.md as a concise overview with navigation links.

Dimension	Reasoning	Score
Conciseness	The content is very verbose with multiple large code blocks, many of which are incomplete/truncated. It includes patterns Claude already knows well (basic Lambda handler structure, API Gateway setup, SQS processing). The sharp edges table is broken with placeholder 'Issue' text repeated, wasting tokens on non-information.	1 / 3
Actionability	The code examples are mostly concrete and executable (SAM templates, handler code), but several are truncated mid-function (Python handler cuts off at 'Parse i', get.js cuts off at 'const item =', Python SQS handler cuts off). The sharp edges table has placeholder content ('Issue' repeated) with no actual solutions, just section headers.	2 / 3
Workflow Clarity	There is no clear workflow or sequence of steps. The content presents patterns as isolated code blocks without explaining how to set up, deploy, test, or validate a serverless application. No validation checkpoints exist for deployment or testing. The anti-patterns section lists problems but provides no concrete remediation steps.	1 / 3
Progressive Disclosure	The content is a monolithic wall of code blocks with no references to external files and no clear navigation structure. Multiple large patterns are inlined that could be split into separate reference files. The 'When to Use' section at the bottom is a meaningless placeholder sentence.	1 / 3
	Total	5 / 12 Passed

Description

22%Scale 1-3

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 reads like a topic heading rather than a functional skill description. It lacks concrete actions (e.g., 'generates', 'scaffolds', 'validates'), omits any 'Use when...' trigger guidance, and provides minimal detail for Claude to distinguish this skill from other coding or AWS skills.

Suggestions

Add explicit concrete actions, e.g., 'Scaffolds AWS Lambda handler functions with structured error handling, logging, and response formatting.'

Add a 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a Lambda function, write a serverless handler, or set up AWS Lambda with error handling.'

Include common keyword variations such as 'AWS Lambda', 'serverless', 'handler function', and relevant runtimes like 'Python Lambda' or 'Node.js Lambda' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description is vague — 'proper Lambda function structure with error handling' names a domain (Lambda functions) but describes no concrete actions. It reads more like a topic label than a capability description.	1 / 3
Completeness	The description weakly addresses 'what' (Lambda function structure) but completely lacks any 'when' clause or explicit trigger guidance. There is no 'Use when...' or equivalent.	1 / 3
Trigger Term Quality	'Lambda function' is a relevant keyword a user might say, and 'error handling' is somewhat natural. However, it misses common variations like 'AWS Lambda', 'serverless', 'handler', or file extensions like '.py'/'.js' that users might mention.	2 / 3
Distinctiveness Conflict Risk	'Lambda function' narrows the domain somewhat, but 'error handling' and 'proper structure' are generic enough to overlap with general coding best-practices skills or other AWS-related skills.	2 / 3
	Total	6 / 12 Passed

Validation

90%

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 — 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

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

Reviewed: ~10 hours 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.