SKILLEMALL.ai

BD puppeteer-skill

Generates Puppeteer scripts for browser automation, scraping, and PDF generation. Triggers on: "Puppeteer", "headless Chrome", "page.goto", "scrape", "PDF generation".

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

Generates Puppeteer scripts for browser automation, scraping, and PDF generation.

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

GeneratorPlaywrightSoftware developmentInfrastructureData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
90/100
safety, quality, tests
Safety 60%
98
Quality 40%
78
Run on models
none yet
Process rating
D
44/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

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 2

✓ No critical or high findings

Medium and low: 2
  • low Dangerous commands cmd-privilege reference/playbook.md:13
    Privilege escalation / world-writable permissions (quoted — discussed, not commanded)
    '--disable-setuid-sandbox',
    quoted
  • low Dangerous commands cmd-privilege reference/playbook.md:64
    Privilege escalation / world-writable permissions (detector / deny-list definition)
    args: ['--no-sandbox', '--disable-setuid-sandbox'],
    detector

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

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "languages"

Process rating: all ten parameters 44/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
  • 70When it triggers. States when to use, but not when not to
  • 100Tools and files. No external tools needed
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 950 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 5 example trigger phrases
  • +3Description length 167: enough signal without eating the budget
  • +4Structure: 9 headings
  • +4Has examples (5 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: 78.