skills/playwright-check/SKILL.md
Browser-based verification using Playwright MCP or Claude-in-Chrome. Navigate pages, interact, screenshot, check console errors. Use when you need to check a page, verify UI, take screenshots, or test browser interactions.
npx skillsauth add RonanCodes/ronan-skills playwright-checkInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Browser verification. Navigate to pages, interact with UI, take screenshots, check for console errors.
/playwright-check http://localhost:3000
/playwright-check http://localhost:3000/settings --flow "click #save-btn, wait 1s, check .toast"
/playwright-check http://localhost:3000 --responsive
Try browser tools in priority order. Attempt to use each; if it errors, fall back:
mcp__playwright__ tools (navigate, screenshot, click)mcp__claude-in-chrome__ toolscurl -s -o /dev/null -w "%{http_code}" for basic HTTP checksState which tool is being used in the output.
Navigate to URL, wait for load, screenshot (unless --no-screenshot), check console for errors/warnings, verify HTTP 200.
Parse comma-separated actions: click <selector>, type <selector> "text", wait <duration>, check <selector>, submit <selector>. Screenshot after each action.
Screenshot at 375px (mobile), 768px (tablet), 1440px (desktop). Flag overlapping elements, horizontal scroll, or cut-off content.
Save to .playwright-checks/<feature>/ (e.g. desktop-1440.png, after-click-save.png). Add .playwright-checks/ to .gitignore if not already there.
## Browser Check: [url]
- Tool: Playwright MCP
- Status: 200 OK
- Console errors: none
| Check | Status | Notes |
|-------|--------|-------|
| Page load | Pass | Loaded in 1.2s |
| Console | Pass | No errors |
| Click #save-btn | Pass | Toast appeared |
--no-screenshot.playwright-checks/ to .gitignore if missingtesting
--- name: linear-pipeline description: The Fable orchestrator for a single dispatched Linear ticket. Holds almost no context itself; it receives `--issue <ID> --detached`, decides the stage sequence, and fans out a sub-agent per stage, passing forward only each stage's artifact (never re-derived, never inlined into its own context). Step zero, before any planning or stage routing, is a boundary triage against `canon/security-boundary.md` (#199): a match tags Ronan Connolly and stops the run, no
development
--- name: in-your-face description: Capture a chat-only answer into a durable artifact (markdown + HTML, PDF when cheap) and launch it automatically so the user cannot miss it. Use when user says "in your face", "don't let me lose this", "save that answer", "make that durable", or right after answering a substantive side question (a recipe, comparison, how-to, or generated prompt) that would otherwise die with the context. category: workflow argument-hint: [--no-open] [--vault <short>] [hint of
tools
One-shot headless OpenAI Codex CLI calls for background/admin AI tasks — summaries, classification, extraction, admin glue. The default engine for anything that runs AI constantly in the background (daemon-driven, per-event), because it bills the flat ChatGPT subscription instead of Claude usage or per-token API spend, and it keeps working while Claude is rate-limited. NEVER for coding — coding stays Claude. Use when a skill or daemon needs a cheap always-on AI call, when the user says "use codex", "ask codex", "codex as backup", or when building a background summarizer/classifier into a listener or loop. Reads auth from ~/.codex/auth.json (ChatGPT account, no API key).
research
Turn a warranty rejection, repair quote, or RMA email into a cited decision brief — legal read (NL/EU consumer law), is the part user-serviceable, live part and new-unit prices, repair-vs-DIY-vs-new economics, before-you-send-it checklist, deadlines. Use when the user pastes or screenshots a repair quote, warranty rejection, "not covered" email, onderzoekskosten fee, or asks "should I repair or replace this".