lambda-function-generator
Lambda Function Generator - Auto-activating skill for AWS Skills. Triggers on: lambda function generator, lambda function generator Part of the AWS Skills skill category.
33
3%
Does it follow best practices?
Impact
81%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/13-aws-skills/lambda-function-generator/SKILL.mdQuality
Discovery
7%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 is extremely weak across all dimensions. It essentially just restates the skill name without describing concrete capabilities, lacks natural trigger terms users would actually say, and provides no explicit guidance on when Claude should select it. The repeated trigger term 'lambda function generator' suggests a template was filled in without thought.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates AWS Lambda function boilerplate code, configures event triggers, sets up IAM permissions, and creates deployment configurations.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a Lambda function, write a serverless handler, set up AWS Lambda, or generate Lambda boilerplate in Python/Node.js.'
Include natural keyword variations users would say: 'Lambda', 'AWS Lambda', 'serverless function', 'Lambda handler', 'create Lambda', '.py/.js handler'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Lambda Function Generator' but does not list any concrete actions like 'creates Lambda functions, configures triggers, sets IAM roles, generates deployment packages.' It merely names itself without describing what it actually does. | 1 / 3 |
Completeness | The description fails to clearly answer 'what does this do' beyond the name, and there is no explicit 'Use when...' clause explaining when Claude should select this skill. The 'Triggers on' line just repeats the skill name. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'lambda function generator' repeated twice. It misses natural user phrases like 'create a Lambda', 'AWS Lambda', 'serverless function', 'write a Lambda handler', or 'deploy Lambda'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Lambda Function' and 'AWS' provides some domain specificity that distinguishes it from generic coding skills, but the lack of detail about what specifically it generates versus other AWS-related skills creates potential overlap. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no actual content—it is entirely meta-description and boilerplate that repeats the skill name without providing any Lambda function generation guidance, code examples, or AWS-specific knowledge. It would be completely useless to Claude in performing any task, as it contains zero actionable information.
Suggestions
Add concrete, executable Lambda function code examples (e.g., Python/Node.js handler templates with proper event/context signatures, IAM role configurations, and deployment commands via AWS CLI or SAM).
Define a clear workflow for generating Lambda functions: choose runtime → write handler → configure IAM → deploy → validate with test event → check CloudWatch logs.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill rather than teaching how to generate Lambda functions—replace with actual technical content.
Include specific patterns for common Lambda use cases (API Gateway trigger, S3 event trigger, SQS consumer) with copy-paste-ready CloudFormation/SAM templates.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It repeats 'lambda function generator' numerous times without providing any actual guidance, code, or AWS Lambda-specific knowledge. Every token is wasted on generic boilerplate. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No Lambda function code, no AWS CLI commands, no CloudFormation templates, no deployment steps—nothing actionable whatsoever. The content only describes what the skill claims to do without actually doing it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains no steps at all. There are no validation checkpoints or any sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, shallow document with no meaningful structure. There are no references to detailed files, no examples section, and the headers present contain only generic placeholder text rather than organized, navigable content. | 1 / 3 |
Total | 4 / 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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
933cf26
- 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.