Best use case
gui-observe is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Observe current screen state before any GUI action.
Teams using gui-observe should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/gui-observe/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How gui-observe Compares
| Feature / Agent | gui-observe | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Observe current screen state before any GUI action.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
AI Agents for Startups
Explore AI agent skills for startup validation, product research, growth experiments, documentation, and fast execution with small teams.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
SKILL.md Source
# Observe — Know Before You Act ## Three Visual Methods (see main SKILL.md for full details) | Method | Returns | Coordinates? | |--------|---------|-------------| | **OCR** (`detect_text`) | Text + bounding box | ✅ YES | | **GPA-GUI-Detector** (`detect_icons`) | UI components + bounding box | ✅ YES (no labels) | | **image tool** | Semantic understanding | ⛔ NEVER | ## Phase 1: First encounter / unfamiliar page (DEFAULT) 1. Take screenshot 2. Run OCR (`detect_text`) → read all text + get coordinates 3. Send screenshot to image tool → understand layout and semantics (⛔ no coordinates from this) 4. Run GPA-GUI-Detector (`detect_icons`) → detect all UI components + coordinates 5. Combine all three to understand current state ## Phase 2: Familiar page (OPTIMIZATION) 1. Take screenshot (but don't send to image tool) 2. Run OCR + GPA-GUI-Detector → get text + coordinates as structured text 3. LLM reads text output directly → decide without visual analysis 4. If uncertain → fall back to Phase 1 ## For known apps with saved memory Use template matching instead of full detection: 1. `_detect_visible_components()` → which saved components are on screen 2. `identify_state_by_components()` → which known state matches 3. If state is known → proceed with `click_component` (no GPA-GUI-Detector needed) 4. If state is unknown → Phase 1 (full observation) ## Coordinate System — ImageContext `detect_all()` returns **image pixel coordinates** (raw detection output). Callers create an `ImageContext` to convert to screen click coordinates. Cropping uses image pixel coords directly — **no conversion needed**. ### ImageContext (in `ui_detector.py`) ```python from scripts.ui_detector import ImageContext ctx = ImageContext.mac_fullscreen() # Mac screencapture fullscreen ctx = ImageContext.mac_window(wx, wy) # Mac window screenshot (win pos in click-space) ctx = ImageContext.remote() # VM / remote / downloaded image (1:1) # Image pixels → screen click coords click_x, click_y = ctx.image_to_click(el["cx"], el["cy"]) # Screen click coords → image pixels (for cropping) px_x, px_y = ctx.click_to_image(click_x, click_y) ``` ### How it works `ImageContext` knows two things: 1. **pixel_scale** — image pixels per click-space unit (from `backingScaleFactor`: Retina=2.0, else 1.0) 2. **origin** — image top-left in screen click-space (fullscreen=(0,0), window=(win_x, win_y)) | Source | Coordinates | |--------|------------| | detect_all output | **image pixels** | | detect_icons / detect_text | image pixels | | cv2 image crop | image pixels | | gui_action.py click | click-space (use `ctx.image_to_click()`) | | template_match raw | image pixels | - **Mac Retina**: pixel_scale=2.0 (e.g., 3024×1964 image, 1512×982 click-space) - **Mac non-Retina**: pixel_scale=1.0 - **Remote VMs**: pixel_scale=1.0, origin=(0,0) - **Templates**: saved in image pixel coordinates ## State Detection States are identified by which components are visible (F1 score matching): ```python from app_memory import identify_state_by_components, _detect_visible_components visible = _detect_visible_components(app_name) state, f1 = identify_state_by_components(app_name, visible) ```
Related Skills
observer-effect-probe
Helps detect skills that behave differently when they sense they are being monitored — catching the class of evasion where conditional activation logic specifically targets attestation and sandbox environments.
---
name: article-factory-wechat
humanizer
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
tavily-search
Use Tavily API for real-time web search and content extraction. Use when: user needs real-time web search results, research, or current information from the web. Requires Tavily API key.
baidu-search
Search the web using Baidu AI Search Engine (BDSE). Use for live information, documentation, or research topics.
agent-autonomy-kit
Stop waiting for prompts. Keep working.
Meeting Prep
Never walk into a meeting unprepared again. Your agent researches all attendees before calendar events—pulling LinkedIn profiles, recent company news, mutual connections, and conversation starters. Generates a briefing doc with talking points, icebreakers, and context so you show up informed and confident. Triggered automatically before meetings or on-demand. Configure research depth, advance timing, and output format. Walking into meetings blind is amateur hour—missed connections, generic small talk, zero leverage. Use when setting up meeting intelligence, researching specific attendees, generating pre-meeting briefs, or automating your prep workflow.
self-improvement
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Claude ('No, that's wrong...', 'Actually...'), (3) User requests a capability that doesn't exist, (4) An external API or tool fails, (5) Claude realizes its knowledge is outdated or incorrect, (6) A better approach is discovered for a recurring task. Also review learnings before major tasks.
botlearn-healthcheck
botlearn-healthcheck — BotLearn autonomous health inspector for OpenClaw instances across 5 domains (hardware, config, security, skills, autonomy); triggers on system check, health report, diagnostics, or scheduled heartbeat inspection.
linkedin-cli
A bird-like LinkedIn CLI for searching profiles, checking messages, and summarizing your feed using session cookies.
notebooklm
Google NotebookLM 非官方 Python API 的 OpenClaw Skill。支持内容生成(播客、视频、幻灯片、测验、思维导图等)、文档管理和研究自动化。当用户需要使用 NotebookLM 生成音频概述、视频、学习材料或管理知识库时触发。