Wait for UI element or window to appear. When you need to wait for dialog to open, loading to complete, or synchronize with application state before next action. Default timeout is 10 seconds.
| Publisher | openakita |
| Repository | openakita |
| Skill name | desktop-wait |
| Stars | 2K |
| Forks | 284 |
| Bundled files | 1 |
| License | AGPL-3.0 |
| Links |
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Published by openakita on GitHub. Read the source before you install it.
Install the Desktop Wait AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.
TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.
https://github.com/openakita/openakita/tree/main/skills/system/desktop-waitAny agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.
git clone --depth 1 https://github.com/openakita/openakita.git /tmp/openakita
mkdir -p .claude/skills
cp -r /tmp/openakita/skills/system/desktop-wait .claude/skills/desktop-waitEnable Desktop Wait in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.
AI skills are plain Markdown instructions rather than provider-specific code, so Desktop Wait is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.
This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.
等待某个 UI 元素或窗口出现。
| 参数 | 类型 | 必填 | 说明 |
|---|---|---|---|
| target | string | 是 | 元素描述或窗口标题 |
| target_type | string | 否 | 目标类型：element（默认）/ window |
| timeout | integer | 否 | 超时时间（秒），默认 10 |
element: 等待 UI 元素出现window: 等待窗口出现等待保存对话框:
json{"target": "另存为", "target_type": "window"}
等待确定按钮:
json{"target": "确定按钮", "timeout": 5}
desktop-click: 等待后点击desktop-find-element: 查找元素The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.
Wait for UI element or window to appear. When you need to wait for dialog to open, loading to complete, or synchronize with application state before next action. Default timeout is 10 seconds.
Because you install it once and use it with any model. Desktop Wait is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.
Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/openakita/openakita/tree/main/skills/system/desktop-wait. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.
Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.
As many as you like. As long as a model supports skills, you can use Desktop Wait with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.
Yes. It is published on GitHub by openakita under the AGPL-3.0 license. You only pay your own AI provider for the tokens you use.
An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.
A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.
Control Ui E2e
Use when designing, testing, fixing, or extending the OpenClaw Control UI GUI, including UI stress-test galleries with feedback inputs, Vitest + Playwright end-to-end checks, mocked Gateway flows,…
Deslop
Diff-scoped AI-slop cleanup pass: strip comment slop, defensive-check slop, type-laundering, and style drift from the current branch diff before autoreview.
Discord Clawd
Use to talk to the Discord-backed OpenClaw agent/session; not for archive search.
Discord User Post
Post an approved message as the logged-in Discord user through the Discord desktop app. Use for release announcements or other direct user-authored Discord posts; not for OpenClaw channel sends, bots,…
Get notified about new features and future giveaways by subscribing to our newsletter 👇
