click-around

Name: click-around
Availability: InStock
Author: stella

Automate browser-based QA and UX testing with structured reports.

163|43|Updated May 3, 2026

Search Tags:#automation #qa #reporting #browser #ux-testing #web-app

Ready to run

npx skills add https://github.com/stella/stella --skill click-around

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: click-around
Source: https://github.com/stella/stella/tree/main/.agents/skills/click-around
Command: npx skills add https://github.com/stella/stella --skill click-around

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Autonomous browser-based QA and UX smoke testing for a feature area, starting the dev server, taking control of Chrome, walking through user stories, monitoring the console, and producing a structured report on what works, what breaks, and what feels wrong.

Core Features & Use Cases

Autonomous setup and navigation across a feature area.
Real-time error monitoring and logging during test runs.
End-to-end user story execution with a consolidated test report.

Quick Start

Provide the feature area and run the click-around skill to automatically perform QA, monitor the page, and generate a report.

Frequently Asked Questions about click-around

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

FAQPage Schema

How do I automate end-to-end browser QA for a web app feature area?▼

Automate end-to-end browser QA by running the click-around skill against a feature area on your dev server. It handles setup, navigates Chrome, executes user stories, and logs errors to produce a structured report.

Can I run UX testing and monitor console errors on a local dev server?▼

Yes, UX testing and real-time console error monitoring are supported on a local dev server. The skill takes control of a Chrome automation environment to walk through user stories and capture errors.

What do I need to set up before running autonomous browser-based smoke tests?▼

You need a running local dev server, a Chrome automation environment, and a reporting mechanism. These prerequisites allow the skill to navigate web applications and export consolidated test results.

What is included in the structured report after a web app test run?▼

The structured report details what works, what breaks, and what feels wrong during the test run. It consolidates error monitoring logs and story-driven interaction results across the feature area.

How does story-driven interaction work for web application testing?▼

Story-driven interaction executes end-to-end user stories across web applications during the test run. The skill navigates the feature area autonomously, logging real-time errors and page behavior into a final report.

Are there limitations when using autonomous Chrome automation for QA reporting?▼

Limitations include requiring a running local dev server and a configured Chrome automation environment. The skill focuses on a specific feature area and relies on a reporting mechanism to export test results.