SKILLEMALL.ai

BF geb-skill

Generates Geb browser automation tests in Groovy with Spock integration. jQuery-like content DSL and page object pattern. Use when user mentions "Geb", "Groovy test", "GebSpec", "Browser.drive". Triggers on: "Geb", "GebSpec", "Groovy browser test", "Browser.drive".

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

Generates Geb browser automation tests in Groovy with Spock integration.

As a process F 26/100 · No process to follow — References files that are not bundled: ../shared/testmu-cloud-reference.md

IntegrationData and analyticsSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
B
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
84
Run on models
none yet
Process rating
F
26/100
No process to follow
References files that are not bundled: ../shared/testmu-cloud-reference.md
Tools and files w 18
0
Steps w 15
0
Result and completion w 14
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
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: 4. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../shared/testmu-cloud-reference.md
  • note frontmatter-key unknown frontmatter key "languages"

Process rating: all ten parameters 26/100

Will not run. References files that are not bundled: ../shared/testmu-cloud-reference.md
  • 0Tools and files. 1 referenced file(s) missing: ../shared/testmu-cloud-reference.md
  • 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
  • 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 904 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
  • +2Single-language instructions
  • +5Description quotes 6 example trigger phrases
  • +3Description length 265: enough signal without eating the budget
  • +4Structure: 10 headings
  • +4Has examples (4 code blocks)
  • +4Reference files are cited in the instructions (2 of 3)
  • +1License stated

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