fec-e2e-testingUse when creating, maintaining, debugging, or reviewing real-browser end-to-end tests with Playwright or Cypress, including Page Object models, CI artifacts, traces, flaky tests, cross-page visual regression, and critical user journeys such as login, payment, permissions, or CRUD. For layer planning
Install via ClawdBot CLI:
clawdbot install bovinphang/fec-e2e-testingGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://github.com/bovinphang/frontend-craftAudited Jun 4, 2026 · audit v1.0
Generated Nov 18, 2026
Automate a real-browser journey from product selection through cart, checkout, and payment confirmation using Playwright. Verify order confirmation pages and payment gateway responses across browsers to catch integration issues. Use Page Objects for login and checkout steps, and CI traces to debug failures.
Test login, role-based access, and multi-tenant permission flows in a web application. Assert that restricted pages and actions are properly gated and that session handling works across pages. Include CI screenshots and network logs to diagnose authorization failures.
Cover critical financial journeys such as transfers, balance updates, and transaction history rendering. Use high-risk flow references for wallet and payment scenarios, and ensure trace capture for every failure. Validate that assertions rely on visible states and backend responses, not fixed sleeps.
Automate patient login, appointment booking, and medical record viewing across multiple pages. Ensure test data is seeded via API and cleaned up, and that sensitive flows are isolated in CI. Visual regression checks confirm key page states for appointment confirmation and record summaries.
Test decentralized application flows including wallet connection, network switching, and transaction signing in a real browser. Use special scenario references for wallet flows and mock services for repeatable seed data. Capture traces and videos in CI to debug signing failures and flaky wallet popups.
Offer a cloud platform that runs E2E tests with Playwright/Cypress, stores CI artifacts, and manages flaky test analytics. Teams pay monthly per seat or per test run volume. The skill's structured procedures and CI reporting templates become core product features.
Provide consulting to implement or rescue E2E test suites for enterprises, including Page Object refactoring, flaky test triage, and CI pipeline integration. Leverage the skill's expected output and constraints as delivery standards. Charge per project or via retainer.
Develop an open-source E2E testing framework or boilerplate aligned with the skill's patterns, then monetize through paid support, training, and enterprise features like advanced reporting and flaky test isolation. Build community adoption via GitHub and documentation.
💬 Integration Tip
Integrate this skill into CI pipelines early by uploading HTML reports, traces, and videos as artifacts, and enforce the constraints (no fixed sleeps, repeatable data, isolated flaky tests) via lint rules or pipeline checks to keep E2E suites stable and debuggable.
Scored Nov 12, 2026
Control desktop applications on Windows — launch, close, focus, resize, move windows, simulate keyboard/mouse input, manage processes, control VSCode, read clipboard, and capture screen info. Use when the user wants to interact with any running program, switch windows, type text, press shortcuts, open files in VSCode, manage running processes, or get system display information.
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.
Pragmatic coding standards for writing clean, maintainable code — naming, functions, structure, anti-patterns, and pre-edit safety checks. Use when writing new code, refactoring existing code, reviewing code quality, or establishing coding standards.
Claude Code integration for OpenClaw. This skill provides interfaces to: - Query Claude Code documentation from https://code.claude.com/docs - Manage subagents and coding tasks - Execute AI-assisted coding workflows - Access best practices and common workflows Use this skill when users want to: - Get help with coding tasks - Query Claude Code documentation - Manage AI-assisted development workflows - Execute complex programming tasks
Plan, draft, version, and refine written content with enforced versioning and quality audits.
Use when writing tests, creating test strategies, or building automation frameworks. Invoke for unit tests, integration tests, E2E, coverage analysis, performance testing, security testing.