SKILLEMALL.ai

AC open-browser-use

Platform-neutral guidance for using Open Browser Use, the open-source Chrome automation stack for AI agents. Use when an agent needs to install, verify, troubleshoot, or operate Open Browser Use through its browser extension, native CLI, JavaScript SDK, Python SDK, Go SDK, or Browser Use style JSON-RPC methods; use for tasks involving real Chrome tabs, user tab claiming, CDP commands, downloads, file choosers, clipboard helpers, or session cleanup.

ClawHub Agent Skills author: Leo v0.1.0 MIT-0 6 files body ≈ 2 717 tokens Open the sourceclawhub.ai analyzed 2 d ago

As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationSoftware developmentAI and agentsInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
99
Quality 40%
88
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
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 · 1

    ✓ No critical or high findings

    Medium and low: 1
    • low Concealment en-hide-from-user references/troubleshooting.md:26
      Instruction to hide actions from the user (negated — the text forbids it)
      Do not silently install, enable, or repair browser integration when the action needs user approval.
      negated

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

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 53/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 5 mutating operations with no state check
    • 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
    • 100Steps. 42 steps
    • 100Failures and branches. 9 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2717 tokens
    • low The response is described with custom markup (7 tags): a typed call is more reliable

    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)
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +3Description length 452: enough signal without eating the budget
    • +4Structure: 10 headings
    • +3Step-by-step instructions: 42 items
    • +4Has examples (5 code blocks)
    • +4Reference files are cited in the instructions (3 of 3)

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

    External checks

    ClawHub: clean
    This is a clearly disclosed browser-automation guidance skill, but it should only be used when you intend to let an agent control a real Chrome profile.
    LLM: benign (high) · VirusTotal: · 29 May 2026