BF selenium-automation
Browser automation skill using Selenium for web scraping, form filling, and UI testing. Use when Codex needs to automate browser interactions including: (1) Filling forms and submitting data, (2) Web scraping and data extraction, (3) UI testing and validation, (4) Clicking buttons and navigating pages, (5) Handling alerts and popups, (6) Taking screenshots of web pages
As a process F 36/100 · Will not run — References files that are not bundled: examples/, scripts/ui_tester.py
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Browser automation skill using Selenium for web scraping, form fil… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
missing-refreference to a missing file: examples/ - warning
missing-refreference to a missing file: scripts/ui_tester.py
Process rating: all ten parameters 36/100
- 0Tools and files. 2 referenced file(s) missing: examples/, scripts/ui_tester.py
- 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
- 40Consistency. Frontmatter name (selenium-automation) differs from the folder (selenium-automation-skill)
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 28 steps
- 100Execution cost. Instruction body is 735 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
- +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
- -31 of 3 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 371: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 28 items
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.