explorer-agent

Explore web and mobile UIs to map screens, journeys, and element state transitions.

1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/swongsuddee/windflu-test --skill explorer-agent-swongsuddee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explorer-agent
Source: https://github.com/swongsuddee/windflu-test/tree/main/.agents/toolkit/explorer-agent
Command: npx skills add https://github.com/swongsuddee/windflu-test --skill explorer-agent-swongsuddee

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

It eliminates guesswork in test design by systematically discovering screens, user journeys, element states, and transitions before you write assertions.

Core Features & Use Cases

  • Evidence-first exploration: produces transition tables, element state inventory tables, and required diagrams to document observable behavior.
  • Multi-skill discovery coverage: supports web UI exploration, native mobile app exploration, diagram creation, and screenshot capture in a coordinated workflow.
  • Requirement conflict detection: checks observed behavior against requirement specs and writes mismatches to a dedicated clarification file.

Quick Start

Use explorer-agent to explore the target app or website, then generate evidence tables and Mermaid diagrams for every observable state and transition.

Frequently Asked Questions about explorer-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map app behavior and element state transitions for test design?

To map app behavior for test design, systematically explore web and mobile interfaces to document screens, user journeys, and element state transitions. This approach generates evidence-first outputs like transition tables and Mermaid diagrams before writing assertions.

Can I use Playwright and Appium together for website and mobile UI exploration?

Yes, Playwright and Appium can be used together for coordinated UI exploration. This multi-tool discovery coverage supports exploring both web and native mobile apps to map platform-specific behavior differences across auth entry points and multi-step flows.

What's the best way to generate Mermaid flow diagrams from observed app states?

The best way to generate Mermaid flow diagrams from app states is to systematically explore user interfaces and map transitions. This produces evidence-first documentation including transition tables, element state inventories, and required diagrams for every observable state.

Does this approach detect mismatches between requirement specs and observed app behavior?

Yes, this approach detects requirement conflicts by checking observed behavior against requirement specs. It identifies mismatches during the UI exploration process and writes them to a dedicated clarification file to resolve ambiguities before test design.

How do I capture screenshots and create an element state inventory for QA discovery?

To capture screenshots and create an element state inventory, perform evidence-first exploration of the target application. This documents observable behavior across CRUD, search, and upload journeys by generating inventory tables complete with screenshot references.