Generate, migrate, and debug Playwright tests from specs or existing Cypress/Selenium suites, sync results with TestRail, run on BrowserStack, and enforce test quality with automated reviews and flakiness fixes.
Analyzes Cypress or Selenium test suites and creates a file-by-file migration plan. Invoked by /pw:migrate before conversion starts.
Plans test strategy for complex applications. Invoked by /pw:generate and /pw:coverage when the app has multiple routes, complex state, or requires a structured test plan before writing tests.
Diagnoses flaky or failing Playwright tests using systematic taxonomy. Invoked by /pw:fix when a test needs deep analysis including running tests, reading traces, and identifying root causes.
Run tests on BrowserStack. Use when user mentions "browserstack", "cross-browser", "cloud testing", "browser matrix", "test on safari", "test on firefox", or "browser compatibility".
Analyze test coverage gaps. Use when user says "test coverage", "what's not tested", "coverage gaps", "missing tests", "coverage report", or "what needs testing".
Fix failing or flaky Playwright tests. Use when user says "fix test", "flaky test", "test failing", "debug test", "test broken", "test passes sometimes", or "intermittent failure".
Generate Playwright tests. Use when user says "write tests", "generate tests", "add tests for", "test this component", "e2e test", "create test for", "test this page", or "test this feature".
Set up Playwright in a project. Use when user says "set up playwright", "add e2e tests", "configure playwright", "testing setup", "init playwright", or "add test infrastructure".
Admin access level
Server config contains admin-level keywords
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Modifies files
Hook triggers on file write and edit operations
Modifies files
Hook triggers on file write and edit operations
Requires secrets
Needs API keys or credentials to function
Requires secrets
Needs API keys or credentials to function
Uses power tools
Uses Bash, Write, or Edit tools
Uses power tools
Uses Bash, Write, or Edit tools
248 production-ready Claude Code skills, plugins, and agent skills for 11 AI coding tools.
The most comprehensive open-source library of Claude Code skills and agent plugins — also works with OpenAI Codex, Gemini CLI, Cursor, and 7 more coding agents. Reusable expertise packages covering engineering, DevOps, marketing, compliance, C-level advisory, and more.
Works with: Claude Code · OpenAI Codex · Gemini CLI · OpenClaw · Cursor · Aider · Windsurf · Kilo Code · OpenCode · Augment · Antigravity
5,200+ GitHub stars — the most comprehensive open-source Claude Code skills & agent plugins library.
Claude Code skills (also called agent skills or coding agent plugins) are modular instruction packages that give AI coding agents domain expertise they don't have out of the box. Each skill includes:
One repo, eleven platforms. Works natively as Claude Code plugins, Codex agent skills, Gemini CLI skills, and converts to 8 more tools via scripts/convert.sh. All 332 Python tools run anywhere Python runs.
| Skills | Agents | Personas | |
|---|---|---|---|
| Purpose | How to execute a task | What task to do | Who is thinking |
| Scope | Single domain | Single domain | Cross-domain |
| Voice | Neutral | Professional | Personality-driven |
| Example | "Follow these steps for SEO" | "Run a security audit" | "Think like a startup CTO" |
All three work together. See Orchestration for how to combine them.
# Clone the repository
git clone https://github.com/alirezarezvani/claude-skills.git
cd claude-skills
# Run the setup script
./scripts/gemini-install.sh
# Start using skills
> activate_skill(name="senior-architect")
# Add the marketplace
/plugin marketplace add alirezarezvani/claude-skills
# Install by domain
/plugin install engineering-skills@claude-code-skills # 24 core engineering
/plugin install engineering-advanced-skills@claude-code-skills # 25 POWERFUL-tier
/plugin install product-skills@claude-code-skills # 12 product skills
/plugin install marketing-skills@claude-code-skills # 43 marketing skills
/plugin install ra-qm-skills@claude-code-skills # 12 regulatory/quality
/plugin install pm-skills@claude-code-skills # 6 project management
/plugin install c-level-skills@claude-code-skills # 28 C-level advisory (full C-suite)
/plugin install business-growth-skills@claude-code-skills # 4 business & growth
/plugin install finance-skills@claude-code-skills # 2 finance (analyst + SaaS metrics)
# Or install individual skills
/plugin install skill-security-auditor@claude-code-skills # Security scanner
/plugin install playwright-pro@claude-code-skills # Playwright testing toolkit
/plugin install self-improving-agent@claude-code-skills # Auto-memory curation
/plugin install content-creator@claude-code-skills # Single skill
npx agent-skills-cli add alirezarezvani/claude-skills --agent codex
# Or: git clone + ./scripts/codex-install.sh
bash <(curl -s https://raw.githubusercontent.com/alirezarezvani/claude-skills/main/scripts/openclaw-install.sh)
git clone https://github.com/alirezarezvani/claude-skills.git
# Copy any skill folder to ~/.claude/skills/ (Claude Code) or ~/.codex/skills/ (Codex)
Convert all 156 skills to 7 AI coding tools with a single script:
npx claudepluginhub alirezarezvani/claude-skills --plugin pwConvert a rambling description of a desired outcome into one polished, autonomous /goal prompt ready to paste into a fresh session. Use when the user says '/fable-goal', 'turn this into a goal prompt', 'write me a fable prompt', or rambles about something they want made and asks for the prompt that makes it happen. Extracts deliverable/quantity/stakes/tools/destination, asks at most one question batch, verifies every named resource against the live environment, writes a 150-350 word prose prompt with the seven-part anatomy (desire + stakes, quality bar, tool inventory + discovery mandate, creative-freedom grant, medium-matched verification loop, delivery, goal line + autonomy directive), and self-checks six binary criteria before delivering. The output is a single copy-paste prompt, never the build itself.
Run a GTD-style weekly review that actually closes loops. Walks David Allen's three-phase ritual — GET CLEAR (collect, process inboxes to zero, empty your head), GET CURRENT (next actions, previous + upcoming calendar, waiting-for, project lists), GET CREATIVE (someday/maybe, new ideas) — backed by three deterministic stdlib scripts: an open-loop scanner that inventories unchecked checkboxes, TODO/FIXME markers, and stale files; a checklist gate that computes completion, names every missing step, and refuses a COMPLETE verdict while any GET CURRENT step is unaccounted for; and a commitment auditor that flags STALLED, NO-NEXT-ACTION, and SOMEDAY-CANDIDATE projects with a 0-100 commitment-health score. The periodic-review counterpart to capture (intake) and reflect (per-conversation reflection).
Personal meeting hygiene, end to end. Before the meeting: a cost gate that prices the meeting in real dollars (attendees x minutes x rate, optionally + the 23-minute refocus overhead per attendee) and refuses to let it exist without a decision, an agenda, and a named owner — verdicts are ASYNC / NOT-READY / MEET, never a shrug. Then a timeboxed agenda builder that rejects any topic without a desired outcome, orders decision topics first, enforces a 5-minute closing actions-recap buffer, and refuses overflowing agendas by name. After the meeting: a deterministic action-item extractor that turns raw notes into an owner + due-date checklist and flags ORPHAN (no owner) and NO-DUE items, because an action item without an owner and a date is theater. Built on the Rogelberg / HBR / Grove meeting-science canon with stdlib-only scripts.
Plan a deep work day the Cal Newport way: time-block planning + shallow-work budgeting + focus-session tracking. Classifies every task deep vs shallow (recent-graduate heuristic, explicit override wins), audits the shallow share against a 30-50% budget with a WITHIN-BUDGET / OVER-BUDGET verdict, then builds an energy-first time-blocked day — deep blocks of at least 90 minutes in the earliest hours, a hard 4-hour deep ceiling the planner refuses to exceed, shallow work batched into at most two windows, 10-minute attention-residue buffers, a fixed lunch, and a hard stop that never silently extends. A JSON-backed focus-session logger tracks weekly deep hours vs target and consecutive-day streaks, and an end-of-day shutdown ritual closes every open loop. Deterministic stdlib scripts do the arithmetic; refusals (exit 2) name exactly what to cut or defer.
Nightly offline self-evolution for this repo's Claude agent: harvests past Claude Code sessions (read-only), mines recurring tasks, replays them offline on your own API budget, and consolidates what it learns into validated CLAUDE.md memory and SKILL.md skills behind a held-out validation gate, staged for review (nothing live changes without /skillopt-sleep adopt). Default backend is mock (no API spend); vendored from microsoft/SkillOpt with safety-hardening patches -- see attribution.derivation_note. Use when the user wants their agent to learn from how this repo's skills are actually used, asks about a nightly/offline sleep or dream cycle, memory/skill consolidation, or invokes /skillopt-sleep.
Production-grade Playwright testing toolkit. Generate tests from specs, fix flaky failures, migrate from Cypress/Selenium, sync with TestRail, run on BrowserStack. 55+ ready-to-use templates, 3 specialized agents, smart reporting that plugs into your existing workflow.
End-to-end test automation with Playwright, Cypress, and Selenium for browser-based testing
Browser automation and E2E testing with Playwright. Auto-detects dev servers, writes clean test scripts. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use for cross-browser testing, visual regression, API testing, component testing in TypeScript/JavaScript and Python projects.
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
End-to-end test execution and recording for web applications
Playwright E2E test debugging and interactive browser exploration. Runs tests with action capture (DOM snapshots, network, console, screenshots), diagnoses failures, and provides browser tools for navigating, clicking, and inspecting pages through ARIA snapshots.