testdriver:locating-elements

Locate UI elements from natural language descriptions and return their properties.

238|34|Updated Aug 25, 2024
One-click install
npx skills add https://github.com/testdriverai/testdriverai --skill testdriver-locating-elements
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testdriver:locating-elements
Source: https://github.com/testdriverai/testdriverai/tree/main/ai/skills/testdriver%3Alocating-elements
Command: npx skills add https://github.com/testdriverai/testdriverai --skill testdriver-locating-elements

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Locating and identifying UI elements across web and desktop interfaces can be brittle when relying on static selectors or coordinates alone. This skill uses natural language descriptions to specify the target element, enabling more robust and adaptable automation.

Core Features & Use Cases

  • Describe elements in plain language to locate them reliably across UI changes.
  • Support single and multiple element discovery with rich debugging metadata for troubleshooting.
  • Cache found elements for faster subsequent lookups and stable automation.

Quick Start

Ask it to locate the search input and return its coordinates and properties.

Frequently Asked Questions about testdriver:locating-elements

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

FAQPage Schema
How do I locate UI elements using natural language for automation?

To locate UI elements with natural language, you provide a plain text description of the target control. The skill identifies the matching element on web and desktop interfaces and returns its coordinates and properties for automation.

Can I find multiple UI elements at once with a natural language description?

Yes, you can find multiple UI elements simultaneously using a single natural language description. The skill supports both single and multiple element discovery across web and desktop interfaces while returning rich debugging metadata for troubleshooting.

Does natural language element locating work for both web and desktop interfaces?

Yes, natural language element locating works for both web and desktop interfaces. The skill identifies on-screen controls across different environments by applying plain language descriptions to satisfy clear element identification requirements.

Why use natural language to locate UI elements instead of static selectors?

Using natural language to locate UI elements instead of static selectors prevents brittle automation scripts. Plain language descriptions adapt to UI changes more reliably, providing robust element identification and returning properties for deterministic matching.

How do I get debugging data for UI elements located with natural language?

You get debugging data for UI elements located with natural language by requesting the element's properties and coordinates. The skill returns rich debugging metadata for troubleshooting and supports caching found elements for faster subsequent lookups.