Use Playwright inside DecisionsAI — Hermes playwright_browser tool, workflow playwright steps, and local Chromium from bin/setup.py.
Scanned 9/10/2026
Install to Claude Code
Skills Directorynpx -y skills add tensology/decisionsai --skill decisions-playwright --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Decisions Playwright?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/tensology-decisions-playwright)More formats (shields.io, HTML) on the badges page.
---
name: decisions-playwright
description: Use Playwright inside DecisionsAI — Hermes playwright_browser tool, workflow playwright steps, and local Chromium from bin/setup.py.
---
# Decisions Playwright
DecisionsAI ships Playwright in its Python venv and installs Chromium during `bin/setup.py`.
## When to use
- Hermes workflow steps with `tool: playwright` or `playwright_browser`
- Ticket polish / ship loops that need screenshots or DOM checks
- Fallback when browser-use is unavailable
## Commands
```bash
# From Decisions venv (after bin/setup.py)
python -m playwright install chromium
```
## Workflow
1. Prefer the Hermes `playwright_browser` tool when the Decisions server is running.
2. For scripted checks, pair with ECC skills `browser-qa`, `webapp-testing`, or `e2e-testing`.
3. Attach screenshot paths or console excerpts in the workflow result packet.
## Related skills
- `browser-qa`, `webapp-testing`, `e2e-testing`
- `decisions-browser-stack` (full browser/content index)
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Practical guide to testing web applications with screen readers for comprehensive accessibility validation.
