SKILLEMALL.ai

AC browser-healthcheck

Browser tool health check and auto-repair. Automatically checks browser status before each use and diagnoses/fixes issues. Use when: (1) preparing to use browser tool for screenshots/automation; (2) browser snapshot/start times out; (3) CDP connection fails; (4) user mentions "browser timeout", "CDP disconnected", "浏览器超时", "browser 失效".

ClawHub Agent Skills author: systiger v1.0.0 MIT-0 3 files body ≈ 1 105 tokens Open the sourceclawhub.ai analyzed 3 d ago

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

AnalyzerInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
80
Run on models
none yet
Process rating
C
52/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 · 0

    ✓ No critical or high findings

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

    Against the Agent Skills spec

    • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 3, column 14: description: Browser tool health check and auto-repair. Automatically checks br… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value

    Process rating: all ten parameters 52/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
    • 55Failures and branches. 1 branches
    • 60Tools and files. Uses tools (bash) that frontmatter does not declare
    • 100Steps. 14 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1105 tokens
    • 100Running it twice. No mutating operations

    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

    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • -2localhost URLs: will not work for another user
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 3 example trigger phrases
    • +3Description length 338: enough signal without eating the budget
    • +4Structure: 14 headings
    • +3Step-by-step instructions: 14 items
    • +4Has examples (11 code blocks)
    • +3All 1 scripts are documented

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

    External checks

    ClawHub: suspicious
    This browser troubleshooting skill is mostly coherent, but its repair path can forcibly stop local processes without enough safeguards.
    LLM: suspicious (medium) · VirusTotal: · 29 May 2026