SKILLEMALL.ai
GitHub ↗ RU Sign in

BF browsectl

WebDriver automation CLI for AI-driven browser control. Provides session management, tab control, element interaction, screenshots, batch execution, and an interactive REPL.

ClawHub Agent Skills author: yorelog v0.1.1 MIT-0 13 files body ≈ 913 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process F 24/100 · Will not run — weak spots: steps, result and completion, when it triggers

IntegrationInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw 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) Goose OpenCode
JSON
Technical rating
B
85/100
safety, quality, tests
Safety 60%
100
Quality 40%
62
Run on models
none yet
Process rating
F
24/100
Will not run
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 · 0

✓ No critical or high findings

Files scanned: 13. 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 "requires"
  • note frontmatter-key unknown frontmatter key "cliHelp"
  • note frontmatter-key unknown frontmatter key "repository"
  • note frontmatter-key unknown frontmatter key "install"

Process rating: all ten parameters 24/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
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 7 mutating operations with no state check
  • 40Consistency. Frontmatter name (browsectl) differs from the folder (browserctl)
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 100Execution cost. Instruction body is 913 tokens

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)
  • +3No numbered steps or checklist
  • +3Output format is not stated: the model decides each time
  • -2localhost URLs: will not work for another user
  • -32 of 2 scripts are never mentioned in SKILL.md
  • +2Single-language instructions
  • +3Description length 173: enough signal without eating the budget
  • +4Structure: 11 headings
  • +4Has examples (1 code blocks)
  • +1License stated

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

External checks

ClawHub: suspicious
BrowseCTL appears to be a real browser automation tool, but it needs review because it can copy logged-in browser cookies and extensions into agent-controlled sessions and keeps browser state on disk.
LLM: suspicious (high) · VirusTotal: · 29 May 2026