Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill lambda-function-generatorLambda Function Generator - Auto-activating skill for AWS Skills. Triggers on: lambda function generator, lambda function generator Part of the AWS Skills skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just restating the skill name without explaining capabilities or providing useful trigger guidance. It lacks any concrete actions, has redundant and narrow trigger terms, and would be nearly impossible for Claude to correctly select from a pool of skills. The description reads more like a placeholder than a functional skill description.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Generates AWS Lambda function boilerplate code, configures triggers, sets up IAM permissions, and creates deployment packages').
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks to create a lambda, build a serverless function, set up AWS functions, or needs Node.js/Python lambda templates').
Remove the redundant trigger term and expand to include variations like 'serverless', 'AWS function', 'create lambda', 'lambda boilerplate', and supported runtimes.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('Lambda Function Generator') but provides no concrete actions. It doesn't explain what the skill actually does - no mention of creating, deploying, configuring, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is just a repetition of the skill name rather than meaningful trigger guidance. No explicit 'Use when...' clause with actionable triggers. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('lambda function generator' listed twice) and overly specific. Missing natural variations users would say like 'create lambda', 'AWS function', 'serverless function', 'deploy lambda', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Lambda Function Generator' is somewhat specific to AWS Lambda, the lack of detail about what it generates or how it differs from other AWS-related skills creates potential overlap with general AWS or serverless skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder with no actionable information. It describes what the skill supposedly does without providing any actual guidance, code examples, or concrete steps for generating Lambda functions. The content fails on all dimensions by being verbose yet empty of substance.
Suggestions
Add executable Python/Node.js code examples showing how to create a basic Lambda function with proper handler structure
Include a concrete workflow: 1) Define handler, 2) Configure runtime settings, 3) Set IAM permissions, 4) Deploy with specific CLI commands or CloudFormation template
Provide specific Lambda configuration examples (memory, timeout, environment variables) rather than generic claims about 'best practices'
Remove all meta-description content ('This skill provides...', 'When to use...') and replace with actual Lambda function templates and patterns
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no specific commands, no actual instructions on how to generate Lambda functions. The entire content describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, sequences, or validation checkpoints for Lambda function creation. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure pointing to detailed materials. No references to examples, templates, or detailed documentation are provided. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
Reviewed
Table of Contents
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.