Browser & OS automation

Automate Web E2E Tests with AI

AI-powered end-to-end web testing via real browser interaction. Designs YAML scenarios, executes with Playwright, and diagnoses failures.

Without it

Piece it together by hand, every time.

With it

Execute AI-designed YAML test scenarios in a real browser using Playwright. This skill enables AI coding tools to perform end-to-end testing with human-like interaction, visual matching, and OCR.

What you get

  • Translate YAML test scenarios into executable Playwright scripts.
  • Perform end-to-end testing using visual matching and OCR.
  • Auto-detect platforms like Flutter, React, Vue, and Angular.
  • Diagnose and explain test failures with investigation checklists.

Add this skill

Antigravity Drive a browserWrite testsDebug

AWT — AI-Powered E2E Testing (Beta)

npx skills add ksgisang/awt-skill --skill awt -g

AWT gives AI coding tools the ability to see and interact with web applications through a real browser. Your AI designs YAML test scenarios; AWT executes them with Playwright.

When to Use

  • You need AI-assisted end-to-end testing through a real browser with declarative YAML scenarios.
  • The test flow depends on visual matching, OCR, or platform auto-detection instead of stable DOM selectors.
  • You want an E2E toolchain that can both execute tests and explain failures for AI coding workflows.

What works now

  • YAML scenarios → Playwright with human-like interaction
  • Visual matching: OpenCV template + OCR (no CSS selectors needed)
  • Platform auto-detection: Flutter, React, Next.js, Vue, Angular, Svelte
  • Structured failure diagnosis with investigation checklists
  • Learning DB: failure→fix patterns in SQLite
  • 5 AI providers: Claude, OpenAI, Gemini, DeepSeek, Ollama
  • Skill Mode: no extra AI API key needed

Links

Built with the help of AI coding tools — and designed to help AI coding tools test better.

Actively developed by a solo developer at AILoopLab. Feedback welcome!

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Comments (0)

Sign In Sign in to leave a comment.