SKILLEMALL.ai
RU Sign in

BC accessibility-tester

Accessibility Tester for AI Native Full-Stack Software Factory Layer 11 - specializes in WCAG 2.1 compliance testing, screen reader compatibility, keyboard navigation, color contrast, and ARIA validation. Ensures applications are accessible to all users.

ClawHub Agent Skills author: alshowse-tech v1.0.0 MIT-0 4 files body ≈ 7 380 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

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

AnalyzerSecurityInfrastructuretype 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
83/100
safety, quality, tests
Safety 60%
100
Quality 40%
57
Run on models
none yet
Process rating
C
52/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
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.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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: 4. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 7380 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "triggers"
  • note frontmatter-key unknown frontmatter key "role"
  • note frontmatter-key unknown frontmatter key "scope"
  • note frontmatter-key unknown frontmatter key "output-format"

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
  • 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
  • 70Execution cost. Instruction body is 7380 tokens
  • 100Tools and files. No external tools needed
  • 100Steps. 6 steps
  • 100Consistency. Name and required fields are in place
  • 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

  • +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
  • -2localhost URLs: will not work for another user
  • +1No license
  • +2Single-language instructions
  • +3Description length 254: enough signal without eating the budget
  • +4Structure: 19 headings
  • +3Step-by-step instructions: 6 items
  • +4Has examples (12 code blocks)

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

External checks

ClawHub: suspicious
The skill does not show data theft or system harm, but it substantially overstates real accessibility auditing and can produce compliance results for pages it never checks.
LLM: suspicious (high) · VirusTotal: · 29 May 2026