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 — it essentially just restates the skill name without describing any concrete capabilities, use cases, or meaningful trigger terms. It reads like auto-generated boilerplate rather than a useful skill description. It would be nearly impossible for Claude to reliably select this skill over others based on this description alone.
Suggestions
Add concrete actions the skill performs, e.g., 'Generates AWS Lambda function boilerplate code, configures event triggers, sets up IAM roles, and creates deployment packages.'
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.'
Replace the duplicated trigger term with diverse natural language variations users might say, such as 'Lambda', 'serverless function', 'AWS Lambda', 'create Lambda', 'Lambda handler'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Lambda Function Generator' but does not describe any concrete actions like 'creates Lambda functions', 'generates boilerplate code', 'configures triggers', etc. It merely names itself without explaining what it actually does. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and there is no explicit 'when to use' guidance. The 'Triggers on' line is just the skill name repeated, not meaningful trigger conditions. | 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 it generates or when to use it could cause overlap with other AWS-related skills. | 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 essentially a placeholder template with no actual instructional content. It contains no executable code, no concrete guidance for generating Lambda functions, and no workflow steps. Every section merely restates that the skill is about 'lambda function generator' without providing any actionable information.
Suggestions
Add concrete, executable Lambda function code examples (e.g., a Python handler template with event/context parameters, SAM/CloudFormation deployment YAML).
Define a clear workflow: e.g., 1) Choose runtime, 2) Generate handler code, 3) Configure IAM role, 4) Deploy with SAM/CDK, 5) Validate with test invocation.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill abstractly and replace with actual technical content.
Include specific AWS CLI commands or IaC templates for deploying Lambda functions, with validation steps like checking CloudWatch logs or running test events.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Every section restates the same vague idea ('lambda function generator') without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific AWS Lambda configurations, no example function templates, no deployment steps. The content only describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints. The bullet 'Provides step-by-step guidance' is a claim without any actual steps provided. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of vague descriptions with no references to detailed files, no structured navigation, and no separation of overview from detailed 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
4dee593
- 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.