SKILLEMALL.ai
GitHub ↗ RU Sign in

AC chrome-devtools-mcp

Standard browser automation for agents via Chrome DevTools MCP — official Google project giving AI agents full Chrome DevTools access. 29 tools for input automation, navigation, performance traces, Lighthouse audits, network inspection, debugging, and emulation. Replaces cloud-hosted browser tools (Browserbase, browser_*) as the primary browser automation standard. Use when you need to automate or inspect web pages, take screenshots, run performance audits, analyze network traffic, debug JS, fill forms, or emulate mobile viewports.

ClawHub Agent Skills author: Luis Calderon v1.0.0 MIT-0 2 files body ≈ 1 620 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

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

ReferenceGitHubAI and agentsSoftware developmenttype 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
A
93/100
safety, quality, tests
Safety 60%
100
Quality 40%
83
Run on models
none yet
Process rating
C
56/100
Has gaps
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

    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

    • note frontmatter-key unknown frontmatter key "keywords"

    Process rating: all ten parameters 56/100

    • 0Result and completion. Does not say what the result is
    • 20When it triggers. No condition that starts the skill
    • 40Consistency. Frontmatter name (chrome-devtools-mcp) differs from the folder (chrome-devtools-mcp-standard)
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (node) that frontmatter does not declare
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 54 steps
    • 100Execution cost. Instruction body is 1620 tokens
    • 100Running it twice. No mutating operations
    • 100Progress reporting. Reports progress

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

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

    External checks

    ClawHub: suspicious
    This is a coherent Chrome browser automation skill, but it gives agents broad control over real web pages without enough privacy, containment, or approval boundaries.
    LLM: suspicious (high) · VirusTotal: · 29 May 2026