SKILLEMALL.ai
GitHub ↗ RU Sign in

BB OpenClaw Native Browser

A stable native browser (WKWebView) for OpenClaw agents. Opens a visible window with tab management, URL bar, and login helpers — every website works, including Perplexity, Grok, Claude, and ChatGPT.

ClawHub Agent Skills author: KimY v0.1.0 2 files body ≈ 1 973 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process B 68/100 · Nearly there — weak spots: result and completion, when it triggers, consistency

ReferenceAI and agentsInfrastructuretype 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
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
66
Run on models
none yet
Process rating
B
68/100
Nearly there
Result and completion w 14
0
When it triggers w 12
20
Consistency w 8
40
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: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "read_when"

Process rating: all ten parameters 68/100

  • 0Result and completion. Does not say what the result is
  • 20When it triggers. No condition that starts the skill
  • 40Consistency. Frontmatter name (OpenClaw Native Browser) differs from the folder (openclaw-browser-2)
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 26 steps
  • 100Failures and branches. 1 branches, has a failure section
  • 100Execution cost. Instruction body is 1973 tokens
  • 100Running it twice. No mutating operations
  • 100Progress reporting. Reports progress
  • low 13 top-level sections: this looks like several domains in one skill

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 199: enough signal without eating the budget
  • +4Structure: 25 headings
  • +3Step-by-step instructions: 26 items
  • +4Has examples (11 code blocks)

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

External checks

ClawHub: suspicious
This is a real browser-automation skill with a coherent purpose, but it asks users to install external code and gives agents access to persistent logged-in web sessions without enough safety boundaries.
LLM: suspicious (high) · VirusTotal: suspicious · 28 May 2026