playwright-cli-agent
Playwright CLI for Agents
Drive a real browser from the CLI to inspect, explore, and reproduce UI behavior. This skill is not the same as playwright-test. Use it when the goal is to operate a web app live — not to write a *.spec.ts test.
When to Use
Trigger this skill for:
- Live UI exploration of a running web app.
- Reproducing a UI bug end-to-end before writing a fix or a test.
- Capturing screenshots for bug reports, before/after comparisons, or responsive checks.
- Validating a flow manually (login, checkout, a multi-step form).
- Discovering stable selectors before authoring a Playwright test.
- Inspecting visual state, layout regressions, or Redis Insight plugin iframes.
If the goal is to author or fix *.spec.ts files, switch to the playwright-test skill.
Installation Check
Confirm Playwright CLI is available:
More from fcenedes/redis_sa_skills
redis-brand-ui
Apply Redis official brand guidelines to frontend UI implementations. Use this skill when building Redis-branded web interfaces, creating marketing pages, styling dashboards, or implementing any UI that must follow the Redis visual identity. Covers colors, typography, components, and dark mode.
10redis-presentation-decks
Create Redis-focused Reveal.js presentation decks for solution architecture, customer briefings, technical workshops, product narratives, QBRs, and sales engineering storytelling. Use when a user asks for Redis-branded slides, decks, or presentations that need Reveal.js HTML, speaker notes, charts, architecture flows, screenshot review, and overflow validation.
2redis-excalidraw-diagrams
Create Redis-focused Excalidraw architecture diagrams for caching, vector search, Redis Query Engine, Streams, replication, clustering, observability, and Redis Cloud systems. Use when a user asks for a Redis technical diagram, architecture visual, workflow sketch, or .excalidraw file that must be accurate, branded, and visually validated.
2playwright-test
Use when creating, fixing, reviewing, or debugging Playwright Test E2E/UI tests, playwright.config files, fixtures, auth state, selectors, traces, CI failures, flaky UI tests, browser tests, or test runner workflows.
1