desktop-wait

Wait for UI elements or windows to appear in desktop automation tasks.

9|2|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/AllBeingsFuture/AllBeingsFuture --skill desktop-wait-allbeingsfuture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: desktop-wait
Source: https://github.com/AllBeingsFuture/AllBeingsFuture/tree/main/electron/embedded-assets/skills/system/desktop-wait
Command: npx skills add https://github.com/AllBeingsFuture/AllBeingsFuture --skill desktop-wait-allbeingsfuture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Wait for UI elements or windows to appear before proceeding, ensuring subsequent actions have the correct context and state.

Core Features & Use Cases

  • Wait for dialogs to open
  • Wait for loading to complete
  • Synchronize application state before next action

Quick Start

Wait for a specific UI element or window to appear before continuing.

Frequently Asked Questions about desktop-wait

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

FAQPage Schema
How do I wait for a UI element to appear before proceeding in desktop automation?

To wait for a UI element in desktop automation, use a synchronization function that pauses execution until the target element is found. This ensures subsequent actions execute only when the correct application state and context are present.

Does this desktop UI wait functionality support Electron apps?

Yes, this desktop UI wait functionality supports synchronization across desktop environments including Electron apps. It can reliably wait for dialogs, loading indicators, and state transitions to appear before triggering the next action.

What is the default timeout when waiting for a window or element to appear?

The default timeout when waiting for a window or UI element to appear is 10 seconds. If the target element or window is not found within this configurable timeout period, a timeout error is returned.

Can I wait for a window to open instead of a specific UI element?

Yes, you can wait for a window to open by setting the target_type to window. The system supports both element and window target types, returning the found item once it appears or throwing a timeout error.

Why does my desktop automation fail when synchronizing actions with loading dialogs?

Desktop automation fails when actions proceed before loading dialogs disappear or appear. Waiting for UI elements or windows to appear synchronizes application state, ensuring subsequent actions have the correct context and preventing premature execution.

What's the best way to synchronize application state before the next action?

The best way to synchronize application state is to wait for UI elements or windows to appear before proceeding. This guarantees subsequent actions execute only after dialogs open or loading completes, avoiding timing mismatches.