Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

jarvis-gui-control

Estrelas0

Forks0

Atualizado2 de julho de 2026 às 15:14

Use when asked to test or operate macOS apps through Jarvis GUI Control, OpenComputerUse, or the OpenClaw gui-control/gui-benchmark CLI. Proactively use for natural-language GUI tasks and GUI proof requests.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

artemgetmann

artemgetmann/openclaw

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	jarvis-gui-control
description	Use when asked to test or operate macOS apps through Jarvis GUI Control, OpenComputerUse, or the OpenClaw gui-control/gui-benchmark CLI. Proactively use for natural-language GUI tasks and GUI proof requests.

Jarvis GUI Control

Canonical instructions live in the product-bundled skill when this skill is loaded from the repository:

../../../skills/jarvis-gui-control/SKILL.md

Read that file and follow it when the path exists. This repo-local skill exists so dev agents and Codex select the same Jarvis GUI-control runbook that ships to Jarvis users.

If this skill has been copied into an isolated worker workspace and the canonical file is not reachable, use this portable fallback:

Prefer openclaw gui-control --runtime open-computer-use for GUI operation and GUI proof.
Use the screen-record skill and openclaw screen record for target-aware video proof. Do not use Peekaboo as the default GUI-operation proof path. Peekaboo is only for still screenshots, UI maps, diagnostics, explicit Peekaboo requests, or fallback after GUI Control or screen recording is unavailable.
Do not use benchmark scripts as product behavior. They are proof tools, not live assistant workflows.
Do not use raw coordinates, AppleScript/JXA, browser plugins, or clipboard fallback as proof of Jarvis GUI-control capability.
Hard-stop unless the user explicitly approves the exact step: auth/login, payment/card/checkout/final purchase/final booking/final order, destructive delete/remove/erase, account/privacy/security/profile settings, and software install/update/relaunch-to-update/package-manager mutation.
If cgWindowNotFound appears across ordinary apps, first suspect a locked or sleeping Mac session and ask for unlock/recovery approval before debugging app adapters or permissions.

Minimal TextEdit proof shape:

openclaw gui-control observe --runtime open-computer-use --app TextEdit --json
openclaw gui-control set-value \
  --runtime open-computer-use \
  --app TextEdit \
  --intent text-input \
  --value "$TOKEN" \
  --approve-policy-risk \
  --json
openclaw gui-control observe --runtime open-computer-use --app TextEdit --json

Mais deste repositório

mesmo repositório

consumer-setup

artemgetmann/openclaw

Use when the user asks to use a consumer integration that is not set up yet: WhatsApp as Me, Email, Google Workspace, Apple Notes, Apple Reminders, Telegram as Me, Google Maps Search, or creative audio. Route here only when the right integration exists but is blocked by missing login, OAuth, QR pairing, permissions, local dependency setup, configuration, or API credentials, and the response should guide setup in product language instead of dumping CLI commands.

2026-07-110

gog

artemgetmann/openclaw

Use for Google Workspace requests tied to Gmail, Google Calendar, Drive, Docs, Sheets, or Contacts, especially when the user explicitly mentions Google or needs cross-surface Google account access. Prefer this over generic email skills when the task is clearly in the Google ecosystem.

2026-07-110

cross-channel-triage

artemgetmann/openclaw

Use when the user asks to triage messages, emails, chats, inboxes, unread messages, recent messages, open replies, who they owe replies to, outreach, or reply drafting across one or more channels such as WhatsApp, Telegram, Gmail/email, Slack, Signal, iMessage, browser portals, or files. For broad sweeps, first produce a scoped prioritized triage list; for one known target, use single-thread draft mode. Always require user approval before any external reply/send.

2026-07-100

himalaya

artemgetmann/openclaw

Use for generic email tasks on connected mail accounts: search, read, summarize, draft, reply, forward, send, and organize email over IMAP/SMTP. This is the better match for normal mailbox work that is not specifically a Gmail or Google Workspace request.

2026-07-100

telegram-user

artemgetmann/openclaw

Use for Telegram-as-me requests on this Mac: reading, sending, replying, or waiting as the user's real Telegram account. Do not use it for the normal Telegram bot channel, BotFather setup, or generic bot onboarding.

2026-07-100

wacli

artemgetmann/openclaw

Send WhatsApp messages to other people or search/sync WhatsApp history via the wacli CLI (not for normal user chats).

2026-07-100

name	jarvis-gui-control
description	Use when asked to test or operate macOS apps through Jarvis GUI Control, OpenComputerUse, or the OpenClaw gui-control/gui-benchmark CLI. Proactively use for natural-language GUI tasks and GUI proof requests.

Jarvis GUI Control

Canonical instructions live in the product-bundled skill when this skill is loaded from the repository:

../../../skills/jarvis-gui-control/SKILL.md

Read that file and follow it when the path exists. This repo-local skill exists so dev agents and Codex select the same Jarvis GUI-control runbook that ships to Jarvis users.

If this skill has been copied into an isolated worker workspace and the canonical file is not reachable, use this portable fallback:

Prefer openclaw gui-control --runtime open-computer-use for GUI operation and GUI proof.
Use the screen-record skill and openclaw screen record for target-aware video proof. Do not use Peekaboo as the default GUI-operation proof path. Peekaboo is only for still screenshots, UI maps, diagnostics, explicit Peekaboo requests, or fallback after GUI Control or screen recording is unavailable.
Do not use benchmark scripts as product behavior. They are proof tools, not live assistant workflows.
Do not use raw coordinates, AppleScript/JXA, browser plugins, or clipboard fallback as proof of Jarvis GUI-control capability.
Hard-stop unless the user explicitly approves the exact step: auth/login, payment/card/checkout/final purchase/final booking/final order, destructive delete/remove/erase, account/privacy/security/profile settings, and software install/update/relaunch-to-update/package-manager mutation.
If cgWindowNotFound appears across ordinary apps, first suspect a locked or sleeping Mac session and ask for unlock/recovery approval before debugging app adapters or permissions.

Minimal TextEdit proof shape:

openclaw gui-control observe --runtime open-computer-use --app TextEdit --json
openclaw gui-control set-value \
  --runtime open-computer-use \
  --app TextEdit \
  --intent text-input \
  --value "$TOKEN" \
  --approve-policy-risk \
  --json
openclaw gui-control observe --runtime open-computer-use --app TextEdit --json