SKILLEMALL.ai

BC scrapeless-pro

Professional web scraping for OpenClaw — stealth Playwright automation with anti-bot bypass, JavaScript rendering, and structured data extraction from any modern website.

ClawHub Agent Skills author: showmemercy19-rgb v1.0.3 MIT-0 5 files body ≈ 935 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process C 50/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches

GeneratorPlaywrightSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
98
Quality 40%
75
Run on models
none yet
Process rating
C
50/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
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 Secrets in code secret-high-entropy-token package-lock.json:31
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…uWm+fFRcIOgKBMiOBP+eXiy…9ab+DDKA==",
    detector
  • low Dangerous commands cmd-privilege scraper.js:202
    Privilege escalation / world-writable permissions (string literal in code, not executed)
    '--disable-setuid-sandbox',
    code literal

Files scanned: 5. 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 "homepage"

Process rating: all ten parameters 50/100

  • 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
  • 20When it triggers. No condition that starts the skill
  • 40Consistency. Frontmatter name (scrapeless-pro) differs from the folder (scrapeless-pro-skill)
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 100Steps. 18 steps
  • 100Execution cost. Instruction body is 935 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

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +2Single-language instructions
  • +3Description length 170: enough signal without eating the budget
  • +4Structure: 16 headings
  • +3Step-by-step instructions: 18 items
  • +3Output format is stated explicitly
  • +4Has examples (7 code blocks)
  • +1License stated

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

External checks

ClawHub: suspicious
This appears to be a real scraping tool, but it combines stealth anti-bot automation with weak usage boundaries and prints the full license key to logs.
LLM: suspicious (high) · VirusTotal: · 29 May 2026