y3-auto-test

Automate Y3 UI testing with deterministic control detection and click actions.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/WindXRan/y3td --skill y3-auto-test-windxran
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: y3-auto-test
Source: https://github.com/WindXRan/y3td/tree/main/maps/EntryMap/.y3maker/skills/y3-auto-test
Command: npx skills add https://github.com/WindXRan/y3td --skill y3-auto-test-windxran

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires npm, @cool-mcp/desktop-automation.

What problem does it solve?

This skill removes the need for manual, error-prone UI clicking during Y3 regression testing by automatically locating UI controls and triggering clicks via MCP toolchains.

Core Features & Use Cases

  • Safe automated UI interaction: Executes UI operations by preferring runtime event triggering (UI path-based) and falling back to coordinate-based desktop clicking.
  • MCP-rule guarded execution: Loads MCP safety and auto-test execution rules before performing automation, respecting timeouts and failure-stop behavior.
  • Game-runtime workflow: Verifies the game is running, obtains UI canvas/control paths when needed, then performs click actions reliably.

Quick Start

Use the y3-auto-test skill to run an automated plan that clicks the target Y3 UI control(s) by control path and validates outcomes without manual mouse operation.

Frequently Asked Questions about y3-auto-test

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

FAQPage Schema
How do I automate Y3 UI regression testing without manual clicking?

Automate Y3 UI regression testing by using MCP toolchains to locate UI controls and trigger click actions. This removes manual mouse operations by executing multi-step automated test plans that interact with UI buttons directly through deterministic control detection.

How does MCP desktop automation handle UI control path detection for automated clicking?

MCP desktop automation handles UI control path detection by preferring the y3runtime trigger_ui_touch_event_by_path function for runtime event triggering. It falls back to y3-helper get_ui_center_in_windows combined with desktop-automation bot_click for coordinate-based clicking.

Do I need npm to run automated UI test plans on a running Y3 game instance?

Yes, you need npm to install the required @cool-mcp/desktop-automation dependency for running automated UI test plans. The workflow verifies the Y3 game is running, obtains UI canvas control paths, and then performs reliable click actions.

What safety rules are loaded before executing multi-step automated click actions?

MCP safety and auto-test execution rules are loaded before executing multi-step automated click actions. These rules govern the automation workflow by respecting configured timeouts and enforcing failure-stop behavior to prevent uncontrolled UI interactions.

Why does my Y3 UI automation fall back to coordinate-based desktop clicking instead of runtime events?

Y3 UI automation falls back to coordinate-based desktop clicking using bot_click when the preferred runtime event triggering via trigger_ui_touch_event_by_path fails. This ensures click actions still execute reliably by obtaining UI centers through get_ui_center_in_windows.

What is the best way to execute deterministic UI button activation during Y3 regression workflows?

The best way to execute deterministic UI button activation during Y3 regression workflows is through MCP-rule guarded execution. This approach automatically locates target panels and controls using UI paths, validating outcomes without manual mouse operation.