Inspect window UI element tree structure for debugging and understanding interface layout. When you need to debug UI automation issues, understand application structure, or find correct element identifiers.
| Publisher | openakita |
| Repository | openakita |
| Skill name | desktop-inspect |
| 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 Inspect 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-inspectAny 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-inspect .claude/skills/desktop-inspectEnable Desktop Inspect 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 Inspect 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 元素树结构（用于调试和了解界面结构）。
| 参数 | 类型 | 必填 | 说明 |
|---|---|---|---|
| window_title | string | 否 | 窗口标题，不填则检查当前活动窗口 |
| depth | integer | 否 | 元素树遍历深度，默认 2 |
检查当前窗口:
json{}
检查记事本，深度 3:
json{"window_title": "记事本", "depth": 3}
desktop-find-element: 查找特定元素desktop-window: 窗口管理The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.
Inspect window UI element tree structure for debugging and understanding interface layout. When you need to debug UI automation issues, understand application structure, or find correct element identifiers.
Because you install it once and use it with any model. Desktop Inspect 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-inspect. 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 Inspect 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.
Openclaw Repair Sweep
Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.
Openclaw Test Performance
Benchmark, diagnose, and optimize OpenClaw test and plugin-suite runtime, import hotspots, CPU/RSS, heap growth, and slow coverage paths.
Openclaw Testing
Choose proportional OpenClaw tests and checks, diagnose failures, and route environment-sensitive or release proof to its owner.
Release Openclaw Ci
Run, watch, debug, and summarize OpenClaw full release CI, release checks, live provider gates, install/update proofs, and release-secret preflights.
Get notified about new features and future giveaways by subscribing to our newsletter 👇
