BC accessmind
Enterprise WCAG 2.2/2.1/EN 301 549 accessibility audit platform. OpenClaw Browser Tool ile entegre çalışan, güvenli ve profesyonel erişilebilirlik denetim sistemi. Özellikler: - WCAG-EM 5-step metodoloji - ACT Rules 50+ atomik kural - Klavye navigasyon testi (Tab simülasyonu) - Focus trap detection - Screen reader simülasyonu - Form etkileşim testleri - ARIA live region testi - OpenClaw browser tool entegrasyonu (güvenli tarama) - Innovative metrics (Focus Efficiency, SR Friendliness scores) - Profesyonel HTML/JSON raporlama Kullanım: (1) "https://example.com için erişilebilirlik denetimi yap" (2) "WCAG uyumluluk raporu oluştur" (3) "WCAG-EM değerlendirmesi gerçekleştir" (4) "Klavye navigasyon testi yap" (5) "Focus tuzaklarını tespit et" (6) "Screen reader simülasyonu yap" (7) "Erişilebilirlik metrikleri hesapla"
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Dangerous commands
cmd-privilegescripts/accessmind-deep-crawler.py:127Privilege escalation / world-writable permissions (string literal in code, not executed)'--disable-setuid-sandbox',
code literal
A further 1 matches are quotations in this security skill's documentation and are not counted as findings.
Files scanned: 42. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 53/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
- 100Tools and files. No external tools needed
- 100Steps. 27 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2721 tokens
- 100Running it twice. No mutating operations
- low 11 top-level sections: this looks like several domains in one skill
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)
- +3Description length 827: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -4Absolute local paths (C:\Users, /home/…): not portable
- -253 emoji in the instructions: noise for the model
- -312 of 17 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +4Structure: 27 headings
- +3Step-by-step instructions: 27 items
- +4Has examples (8 code blocks)
- +4Reference files are cited in the instructions (7 of 11)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.