SKILLEMALL.ai
GitHub ↗ RU Sign in

AC chrome-devtools

Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests.

ClawHub Agent Skills author: Adin v1.0.0 MIT-0 4 files body ≈ 494 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, inputs and preconditions

AnalyzerSoftware developmentAI 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
A
91/100
safety, quality, tests
Safety 60%
99
Quality 40%
80
Run on models
none yet
Process rating
C
56/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

The same skill appears in 1 more place: ClawHub

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 Dangerous commands cmd-privilege skill.json:9
      Privilege escalation / world-writable permissions (detector / deny-list definition; string literal in code, not executed)
      "--chrome-arg=--disable-setuid-sandbox"
      detectorcode literal

    Files scanned: 4. 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 56/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. 2 mutating operations with no state check
    • 40Consistency. Frontmatter name (chrome-devtools) differs from the folder (xiaopi-chrome-devtools)
    • 100Tools and files. No external tools needed
    • 100Steps. 12 steps
    • 100Failures and branches. 3 branches, has a failure section
    • 100Execution cost. Instruction body is 494 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)
    • +3Output format is not stated: the model decides each time
    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +3Description length 211: enough signal without eating the budget
    • +4Structure: 7 headings
    • +3Step-by-step instructions: 12 items

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

    External checks

    ClawHub: suspicious
    This is a coherent Chrome DevTools automation skill, but it should be reviewed because it runs a mutable npm package with Chrome sandbox-disabling flags and persistent browser state.
    LLM: suspicious (high) · VirusTotal: · 29 May 2026