argus-gui-automation
Automates mouse, keyboard, and screen interactions on macOS and Windows.
Install
mkdir -p .claude/skills/argus-gui-automation && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11485" && unzip -o skill.zip -d .claude/skills/argus-gui-automation && rm skill.zipInstalls to .claude/skills/argus-gui-automation
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Desktop GUI automation via the Argus MCP server. Use when the user asks to control their computer, interact with desktop applications, take screenshots, click UI elements, type text, scroll, manage windows, or automate any GUI task. Triggers: "screenshot", "click on", "open app", "type into", "scroll", "computer use", "GUI automation", "desktop control", "操作电脑", "截屏", "点击", "打开应用", "输入文字".Key capabilities
- →Take screenshots of the user's screen.
- →Simulate mouse clicks (left, double, triple, right, middle).
- →Type text into applications.
- →Scroll within applications.
- →Open and manage desktop applications.
How it works
This skill provides access to desktop GUI automation tools via the `argus` MCP server. It allows taking screenshots, analyzing the screen, and then performing actions like clicking, typing, and scrolling. Actions can be batched for efficiency.
Inputs & outputs
When to use argus-gui-automation
- →Automating UI testing
- →Remote GUI navigation
- →Bulk typing or clicking tasks
- →Capturing screen state
About this skill
Argus GUI Automation
You have access to desktop GUI automation tools via the argus MCP server. These tools let you see and control the user's screen — take screenshots, click, type, scroll, and manage applications.
Setup
The argus MCP server must be configured in .mcp.json:
{
"mcpServers": {
"argus": {
"command": "node",
"args": ["<path-to>/argus-automation/dist/index.js"]
}
}
}
macOS Prerequisites
- Grant Accessibility permission to your terminal app (System Settings → Privacy & Security → Accessibility)
- Grant Screen Recording permission to your terminal app (System Settings → Privacy & Security → Screen Recording)
- If permissions are missing,
request_accesswill show the TCC state and guide the user
Windows Prerequisites
- No special permissions needed
- Windows 10/11 supported
Workflow
1. Request Access First
Before interacting with any application, you MUST call request_access with the app names:
request_access({ application_names: ["Safari", "Finder"], reason: "Navigate to a website" })
2. Screenshot → Analyze → Act
Always take a screenshot before acting. Never click blindly.
screenshot() → analyze the image → left_click({ coordinate: [x, y] })
3. Use Batch for Efficiency
Combine multiple actions into one call to reduce latency:
computer_batch({ actions: [
{ action: "left_click", coordinate: [100, 200] },
{ action: "type", text: "hello" },
{ action: "key", text: "Return" },
{ action: "screenshot" }
]})
Key Rules
- Always screenshot first — never guess coordinates. The screen may have changed.
- Request access before interaction — tools will error if the frontmost app isn't in your allowlist.
- Use batch for multi-step actions — reduces round-trips by 60%+.
- CJK text: use clipboard — for non-ASCII text, use
typewithvia_clipboard: true, or manuallywrite_clipboard+key("cmd+v")(macOS) /key("ctrl+v")(Windows). - Coordinate system — coordinates are in logical pixels matching the screenshot dimensions. (0,0) is top-left.
- Permission tiers — browsers are "read" (visible only), terminals are "click" (no typing), other apps are "full".
- One session at a time — if another Claude session is using the computer, you'll get a lock error. Wait or ask the user to stop the other session.
Tool Quick Reference
| Tool | Purpose |
|---|---|
request_access | Grant permission to interact with apps |
screenshot | Capture the current screen |
zoom | High-res capture of a screen region |
left_click | Click at coordinates |
double_click | Double-click |
type | Type text (use via_clipboard for CJK) |
key | Press key combo ("cmd+c", "Return", etc.) |
scroll | Scroll at position |
computer_batch | Run multiple actions in one call |
open_application | Launch an app |
read_clipboard / write_clipboard | Clipboard access |
Platform Differences
| Feature | macOS | Windows |
|---|---|---|
| Paste shortcut | Cmd+V | Ctrl+V |
| App identifier | Bundle ID (com.apple.Safari) | EXE name (CHROME.EXE) |
| Window hiding | Compositor-level (safe) | Minimize (disabled by default) |
| Permissions | TCC (Accessibility + Screen Recording) | None needed |
| File manager | Finder (always allowed) | Explorer (add to allowlist) |
When not to use it
- →When interacting with an application without first requesting access.
- →When clicking blindly without taking a screenshot first.
- →When another Claude session is already using the computer (will result in a lock error).
Limitations
- →Always screenshot first , never guess coordinates.
- →Request access before interaction , tools will error if the frontmost app isn't in your allowlist.
- →Use batch for multi-step actions , reduces round-trips by 60%+.
How it compares
This skill enables programmatic control and interaction with a user's desktop GUI, automating tasks that would otherwise require manual input, and providing a structured workflow for analysis and action.
Compared to similar skills
argus-gui-automation side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| argus-gui-automation (this skill) | 0 | 4mo | No flags | Intermediate |
| opencode-cli | 14 | 7mo | Review | Advanced |
| claude-automation-recommender | 47 | 2mo | Review | Beginner |
| mcp-integration | 21 | 9mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
opencode-cli
SpillwaveSolutions
This skill should be used when configuring or using the OpenCode CLI for headless LLM automation. Use when the user asks to "configure opencode", "use opencode cli", "set up opencode", "opencode run command", "opencode model selection", "opencode providers", "opencode vertex ai", "opencode mcp servers", "opencode ollama", "opencode local models", "opencode deepseek", "opencode kimi", "opencode mistral", "fallback cli tool", or "headless llm cli". Covers command syntax, provider configuration, Vertex AI setup, MCP servers, local models, cloud providers, and subprocess integration patterns.
claude-automation-recommender
anthropics
Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what Claude Code features they should use.
mcp-integration
anthropics
This skill should be used when the user asks to "add MCP server", "integrate MCP", "configure MCP in plugin", "use .mcp.json", "set up Model Context Protocol", "connect external service", mentions "${CLAUDE_PLUGIN_ROOT} with MCP", or discusses MCP server types (SSE, stdio, HTTP, WebSocket). Provides comprehensive guidance for integrating Model Context Protocol servers into Claude Code plugins for external tool and service integration.
hook-development
anthropics
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.
agent-factory
alirezarezvani
Claude Code agent generation system that creates custom agents and sub-agents with enhanced YAML frontmatter, tool access patterns, and MCP integration support following proven production patterns
swarm-advanced
ruvnet
Advanced swarm orchestration patterns for research, development, testing, and complex distributed workflows