351 skills · sorted by relevance
Use a computer connected to Kortix to read and write files, run shell commands, and operate desktop apps. The skill covers machine selection, access checks, screen inspection, and handling connection or permission errors.
Helps Claude work in desktop apps by viewing screenshots, clicking, typing, and scrolling. It covers access approval, choosing appropriate tools, and handling app restrictions for tasks in Notes, Finder, settings, and other native apps.
Inspect and control the connected local computer through A0 CLI or a Launcher host gateway. The skill guides screenshots, native app input, window targeting, and checking results, with background actions where the connected system supports them.
Read this skill before the first step of any request to do something in an app on the person's own computer (Notes, Finder, System Settings, any desktop app), to look at their screen, or for "computer use". Computer use (desktop control) lets Claude take screenshots of the person's desktop and control it with clicks, typing and scrolling through the Claude desktop app; its tools are named mcp__computer-use__* when the session runs in the desktop app and mcp__remote-devices__computer_* when a cloud session is linked to the person's computer; before computer use is turned on for a conversation there may be no such tools, only an enable__mcp__remote-devices__computer tool, which turns it on. It covers turning it on, picking the right tool, the access flow, and the safety rules for tiered apps, links and financial actions. It is not for websites, which go through Claude in Chrome or the built-in browser and their own skills.
The English summary is being prepared. Showing the original description.
Find available computers and remote environments, then start or continue a task in the requested location. Route work involving files or apps on the user's computer to that computer, and follow progress while preserving the selected environment.
Read this skill before the first step of any request to do something in an app on the person's own computer (Notes, Finder, System Settings, any desktop app), to look at their screen, or for "computer use". Computer use (desktop control) lets Claude take screenshots of the person's desktop and control it with clicks, typing and scrolling through the Claude desktop app; its tools are named mcp__computer-use__* when the session runs in the desktop app and mcp__remote-devices__computer_* when a cloud session is linked to the person's computer; before a conversation is linked there may be no such tools, only an enable__mcp__remote-devices__Claude_Browser tool, which links it. It covers getting linked, picking the right tool, the access flow, and what to do when computer use is off or out of reach. It is not for websites, which go through Claude in Chrome or the built-in browser and their own skills.
The English summary is being prepared. Showing the original description.
Configure Hermes to run AI models through Actual Computer on your own hardware. Set up either the hosted relay or a local connection, select models, verify responses, and troubleshoot request errors or empty output.
Operates native desktop apps through Cherry Studio Computer Use. It reads interface information, types, clicks, and captures windows, using fresh observations to choose actions and verify results within the permissions and capabilities available.
Build AI agents that inspect screenshots, choose actions, and operate a mouse and keyboard. Covers the observation and action loop, desktop control examples, and isolated environments that restrict access to files, credentials, and networks.
Operate desktop applications through DeepChat's built-in Computer Use tools. Inspect windows, click controls, enter text, use menus, and arrange windows, checking the visible result after each action.
MUST USE whenever the user wants to automate a real desktop or sandbox - clicking, typing, scrolling, screenshotting, running an OS shell command, or handing a high-level 'open browser and do X' task to an autonomous computer-use agent. Wraps the trycua/cua Python toolkit via its `cua` CLI - pynput-based, cross-platform (macOS / Linux / Windows). NO custom tools are registered; you call `cua` through pi's built-in bash and read screenshots back through the Read tool. Triggers: cua, computer use, computer-use, GUI automation, screenshot the desktop, click on the screen, type into the active app, scroll the page, control my computer, drive my browser, sandbox, docker sandbox, QEMU sandbox, Lume sandbox, ComputerAgent, cua do, cua sandbox, 컴퓨터 자동화, 스크린샷 찍어, 내 컴퓨터 조작, 브라우저 열어서, 샌드박스, 화면 자동화, 마우스로 클릭, 키보드 타이핑, computer use 위임, 자동으로 클릭, 자율 에이전트로 처리.
The English summary is being prepared. Showing the original description.
Change the wallpaper and the accent color used for the Dock and window titlebars on the user’s dot’s computer. The skill uses a dedicated appearance command’s help instructions to inspect and adjust these settings.
Guide desktop actions on a connected Linux computer using accessibility information that identifies buttons and fields. It covers checking keyboard focus, verifying results with screenshots, and handling limitations in XWayland apps and remote desktop viewers.
Build and run computer-use-demo in Docker, then use Playwright to test its Streamlit interface without opening a visible browser. Save conversation transcripts, API exchanges, and screenshots to inspect behavior after changes.
Build AI agents that interact with computers like humans do - viewing screens, moving cursors, clicking buttons, and typing text. Covers Anthropic's Computer Use, OpenAI's Operator/CUA, and open-source alternatives. Critical focus on sandboxing, security, and handling the unique challenges of vision-based control. Use when "computer use, desktop automation agent, screen control AI, vision-based agent, GUI automation, Claude computer, OpenAI Operator, browser agent, visual agent, RPA with AI, " mentioned.
The English summary is being prepared. Showing the original description.
Control local apps through Computer Use (the @oai/sky runtime) inside the Codex app. Use when the session uses a custom (non-OpenAI) model, for example deepseek-v4-flash or mimo-v2.5, and the user asks to control the computer, operate a desktop app's UI, use Safari or Chrome through computer use, click or type in an app, or take a screenshot of an app. Prefer purpose-built connectors, APIs, or CLIs when they exist.
The English summary is being prepared. Showing the original description.
Create disposable Linux or macOS computers for running code, testing apps, operating desktop interfaces, and browsing websites. Use isolated environments locally or in the Cua cloud, then delete them when the work is complete.
Guide remote Windows app control using UI Automation, which identifies controls by names and roles. Covers text entry, buttons, window management, screenshot checks, and handling desktop session problems when the connected backend supports these features.
Control native macOS apps through named buttons, fields, and menus using accessibility data, which describes interface elements. The skill also guides window actions and checking fresh screenshots to confirm what actually changed.
Guide a first computer-use agent run from environment checks to a browser-only task and a viewer of the run history. Explain each stage so users can understand the output and review screenshots afterward.
Prepare a local LangBot environment for development and browser testing. The skill covers service startup, shared connection settings, browser access, proxy troubleshooting, and reusable login profiles, with guidance for Linux and WSL environments.
This skill should be used when the user asks to "build a computer-use agent", "automate a GUI with an AI agent", "when to use computer use vs an API", "make browser automation reliable", or "design screenshot-driven agent actions".
The English summary is being prepared. Showing the original description.
Build AI agents that interact with computers like humans do - viewing screens, moving cursors, clicking buttons, and typing text. Covers Anthropic's Computer Use, OpenAI's Operator/CUA, and open-source alternatives. Critical focus on sandboxing, security, and handling the unique challenges of vision-based control. Use when: computer use, desktop automation agent, screen control AI, vision-based agent, GUI automation.
The English summary is being prepared. Showing the original description.
Build AI agents that interact with computers like humans do - viewing screens, moving cursors, clicking buttons, and typing text. Covers Anthropic's Computer Use, OpenAI's Operator/CUA, and open-source alternatives. Critical focus on sandboxing, security, and handling the unique challenges of vision-based control. Use when: computer use, desktop automation agent, screen control AI, vision-based agent, GUI automation.
The English summary is being prepared. Showing the original description.