SKILLEMALL.ai
GitHub ↗ RU Sign in

AD lettuce-skill

Generates Lettuce BDD tests for Python with feature files and step definitions. Note: Lettuce is legacy/unmaintained; consider Behave for new projects. Use when user specifically mentions "Lettuce". Triggers on: "Lettuce", "lettuce test", "lettuce BDD".

LambdaTest/agent-skills Agent Skills author: LambdaTest 3 files body ≈ 769 tokens Open the sourcegithub.com↗ analyzed 34 h ago

Generates Lettuce BDD tests for Python with feature files and step definitions.

As a process D 37/100 · Unfinished process — weak spots: steps, result and completion, inputs and preconditions

GeneratorPlaywrightSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
88
Run on models
none yet
Process rating
D
37/100
Unfinished process
Steps w 15
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "languages"
    • note edit-residue the text marks something as outdated (lines 2): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 37/100

    • 0Steps. Prose only: no discrete steps
    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 60Tools and files. Uses tools (python) that frontmatter does not declare
    • 70When it triggers. States when to use, but not when not to
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 769 tokens
    • 100Running it twice. No mutating operations

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +4Description does not say when NOT to use the skill (false activations)
    • +3No numbered steps or checklist
    • +3Output format is not stated: the model decides each time
    • -2localhost URLs: will not work for another user
    • +2Single-language instructions
    • +5Description quotes 4 example trigger phrases
    • +3Description length 253: enough signal without eating the budget
    • +4Structure: 10 headings
    • +4Has examples (4 code blocks)
    • +4Reference files are cited in the instructions (1 of 2)
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.