SKILLEMALL.ai

AC browser-qa

Run automated post-deploy UI verification with a browser automation MCP (claude-in-chrome, Playwright, or Puppeteer): console-error and Core Web Vitals smoke checks, form and auth-flow interaction tests, screenshot visual regression across three breakpoints, and axe-core accessibility audits ending in a SHIP / DO-NOT-SHIP verdict. Use when testing a deployed feature on staging or preview, before shipping frontend changes, reviewing a frontend PR, or checking responsive layout and accessibility.

The skillemall take

This skill runs browser automation post-deploy: checks console errors, measures Core Web Vitals, tests forms and auth flows, captures screenshots across three breakpoints, and runs axe-core accessibility audits. Outputs a SHIP or DO-NOT-SHIP verdict.

Single file, no scripts, 872 tokens. Quality score 87, safety 100. No critical findings, linter clean. Works across all major platforms from Claude to DeepSeek. Process score of 59 suggests streamlined logic, but that's fine for smoke tests before shipping.

Install if you're testing frontend on staging or reviewing PRs. Does exactly what it says without bloat.

affaan-m/ECC Agent Skills author: affaan-m MIT 1 file body ≈ 872 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Run automated post-deploy UI verification with a browser automation MCP (claude-in-chrome, Playwright, or Puppeteer): console-error and Core Web Vitals smoke…

As a process C 59/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches

AnalyzerPlaywrightSoftware developmentInfrastructureData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
87
Run on models
none yet
Process rating
C
59/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: browser-qa (affaan-m/everything-claude-code)

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: 1. 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 59/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 3 mutating operations with no state check
    • 60Result and completion. Output format stated, no completion criterion
    • 100Tools and files. No external tools needed
    • 100Steps. 8 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 872 tokens
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

    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)
    • +1No license
    • +2Single-language instructions
    • +3Description length 499: enough signal without eating the budget
    • +4Structure: 10 headings
    • +3Step-by-step instructions: 8 items
    • +3Output format is stated explicitly
    • +4Has examples (5 code blocks)

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