Agent skill

Desktop App Testing

by Porabuild in Porabuild/Poracode

Walk a native Windows, macOS, or Linux app through a flow with Poracode's desktop control and verify each step from the window itself.

Apache-2.0Auto-check passedProductivity & Automation

Install Desktop App Testing

skills CLI
$ npx skills add Porabuild/Poracode --skill desktop-app-testing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Porabuild/Poracode desktop-app-testing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Porabuild/Poracode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/resources/plugins/computer-use/skills/desktop-app-testing .claude/skills/desktop-app-testing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
desktop-app-testing
GitHub stars
114
Token cost
~557 tokens
SKILL.md length
318 words
Files
1
Skills in repo
21
Repo updated
First seen
Licence
Apache-2.0

At a glance

Walk a native Windows, macOS, or Linux app through a flow with Poracode's desktop control and verify each step from the window itself.

  • Tasks that involve Desktop control
  • SKILL.md covers Plan the run, Run the flow, Judge the result and Report
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Desktop App Testing is an agent skill from Porabuild/Poracode. Walk a native Windows, macOS, or Linux app through a flow with Poracode's desktop control and verify each step from the window itself.

Its SKILL.md is about 560 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Productivity & Automation, covering Desktop control. It works with Linux and macOS. The repository describes itself as: One window for all your AI coding agents. Run Claude, Codex, OpenCode, Gemini, Antigravity, Cursor, and Copilot side-by-side. Terminal and chat, any layout. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Desktop control

Example prompts

  • “/desktop-app-testing”

What it can do on your machine

Read from SKILL.md and the folder at commit bffd89d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Desktop App Testing loads about 557 tokens when it runs. Until then it costs about 39 tokens; SKILL.md has 318 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~39
When it runs · the whole SKILL.md, loaded when a task matches
~557

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Porabuild/Poracode at commit bffd89d, republished under its Apache-2.0 licence (© Porabuild). 318 words, ~557 tokens.

Download SKILL.mdSave it as .claude/skills/desktop-app-testing/SKILL.md (or your agent's skills folder).
name
desktop-app-testing
description
Walk a native Windows, macOS, or Linux app through a flow with Poracode's desktop control and verify each step from the window itself.

Desktop App Testing

Follow the computer-use skill for enable/disable, background-only, and how to read a result. This skill is the test plan: predict, drive, prove.

Plan the run

List apps and windows and pick the exact target. If the app is not running, search installed apps with list_apps query and pass the returned id to launch_app. Write down the steps you intend to perform and what each one should produce on screen; do not improvise against whatever window happens to be in front.

Call get_window_state on the selected window with include_text:true before the first step. Some apps recreate windows during navigation, so refresh a stale window instead of reusing its old id.

Run the flow

Call computer_use.enable immediately before the first control step and keep it enabled for the uninterrupted run.

For each step: inspect, act, inspect again, and compare. Prefer observe:"text"; reuse observation.state for the second look. Do not batch coordinates or steps whose target depends on an intermediate result.

Use mode:"foreground" and activate_window only when the user asked for a takeover, and warn the user immediately beforehand — a refusal is not that permission. A background_unavailable refusal means follow the hint to invoke_element or set_element_value, and if none fits, say so rather than taking over the desktop.

Judge the result

A step passed when the window shows what you predicted — the dialog closed, the row appeared, the field holds the value. Input dispatched with no visible change is a failure, not a pass, and so is a screenshot you did not actually look at.

Stop at anything the user owns: locked desktops, OS permission prompts, password fields, payment or account confirmations. Ask instead of typing through them.

Report

Name the app and window, list the steps with their verified outcome, and show the screenshot for anything visual. Call out the steps you could not complete and why, then computer_use.disable so the machine goes back to the user.

© Porabuild, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in resources/plugins/computer-use/skills/desktop-app-testing of Porabuild/Poracode.

Open the folder on GitHubat commit bffd89d

Compare with similar skills

Desktop App Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Desktop App Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Desktop App Testing this skillPorabuild/Poracode114—~557Automated safety check: PassApache-2.0
Open Computer UseiFurySt/open-codex-computer-use2.3k—~1.5kAutomated safety check: PassMIT
Waku Computer Useegoist/waku1.6k—~3.6kAutomated safety check: PassGPL-3.0
Browser MCP Agentantibrow/anti-detect-browser-skills9141 repos~4.2kAutomated safety check: WarnMIT
Drive Screencoleam00/skills670—~5.4kAutomated safety check: PassMIT
Gooeypi Computer Useam-will/gooey-pi940—~370Automated safety check: PassMIT

Similar skills

  • Open Computer Use

    iFurySt/open-codex-computer-use

    Platform-neutral guidance for using Open Computer Use, the open-source Computer Use MCP server and CLI for macOS, Linux, and Windows.

    2.3k GitHub stars~1.5k tokensUpdated yesterday
    Productivity & AutomationAuto-check passed
  • Control local macOS, Windows, and Linux apps through Waku Computer Use.

    1.6k GitHub stars~3.6k tokensUpdated 5 days ago
    Productivity & AutomationAuto-check passed
  • Browser MCP Agent

    antibrow/anti-detect-browser-skills

    Give an AI agent its own real browser over MCP tool calls - launch, navigate, click, fill, screenshot, extract text, run JS - with a kernel-level real-device fingerprint and a persistent profile, so…

    914 GitHub starsUsed in 1 repo~4.2k tokens
    Productivity & AutomationAuto-check: warnings
  • Drive Screen

    coleam00/skills

    Take real control of the desktop - list and focus windows, type, paste, click, scroll, and screenshot - on Windows, macOS or Linux, and drive other coding-agent sessions running in terminals.

    670 GitHub stars~5.4k tokensUpdated 20 days ago
    Productivity & AutomationAuto-check passed
  • Gooeypi Computer Use

    am-will/gooey-pi

    Drive native applications on macOS, Windows, or Linux through the separately installed TryCUA driver CLI.

    940 GitHub stars~370 tokensUpdated 28 days ago
    Productivity & AutomationAuto-check passed
  • Computer Use

    johnson7788/MultiUserClaw

    Drive the user's desktop in the background — clicking, typing, scrolling, dragging — without stealing the cursor, keyboard focus, or switching virtual desktops / Spaces.

    327 GitHub starsUsed in 1 repo~2.8k tokens
    Productivity & AutomationAuto-check: warnings

More from Porabuild/Poracode

All 21 skills in this repo
  • Interactive Testing

    Porabuild/Poracode

    Run repeatable integration and smoke testing against the real Poracode Electron app through Chrome DevTools Protocol.

    114 GitHub stars~4.5k tokensUpdated today
    Auto-check: notes
  • Release Notes

    Porabuild/Poracode

    Write consistent, hand-written-looking changelog entries for a Poracode release.

    114 GitHub stars~4.2k tokensUpdated today
    Auto-check passed
  • Skill Creator Poracode

    Porabuild/Poracode

    Create a new reusable agent skill managed by Poracode. An agent skill from Porabuild/Poracode.

    114 GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • App Controls

    Porabuild/Poracode

    Inspect and drive Poracode itself — the Terminal panel, other threads, projects, workspaces, git, pull requests, and schedules — through the poracode MCP.

    114 GitHub stars~745 tokensUpdated today
    Auto-check passed
  • Chrome Control

    Porabuild/Poracode

    Use the user's real Chrome tabs and signed-in sessions for visible browser workflows.

    114 GitHub stars~691 tokensUpdated today
    Auto-check passed
  • Computer Use

    Porabuild/Poracode

    Inspect and operate native Windows, macOS, or Linux applications through Poracode's desktop-control tools.

    114 GitHub stars~718 tokensUpdated today
    Auto-check passed

Works with

Questions about Desktop App Testing

What does Desktop App Testing do?

Walk a native Windows, macOS, or Linux app through a flow with Poracode's desktop control and verify each step from the window itself. Desktop App Testing is an agent skill from Porabuild/Poracode. Walk a native Windows, macOS, or Linux app through a flow with Poracode's desktop control and verify each step from the window itself.

When should I use Desktop App Testing?

Desktop App Testing fits situations like: tasks that involve Desktop control.

How do I install Desktop App Testing in Claude Code?

Run `npx skills add Porabuild/Poracode --skill desktop-app-testing -a claude-code`. Or copy the skill folder (resources/plugins/computer-use/skills/desktop-app-testing in Porabuild/Poracode) into .claude/skills/desktop-app-testing in your project. Claude Code loads it when a task matches its description.

How do I install Desktop App Testing in Codex?

Run `npx skills add Porabuild/Poracode --skill desktop-app-testing -a codex`. Or copy the skill folder (resources/plugins/computer-use/skills/desktop-app-testing in Porabuild/Poracode) into .agents/skills/desktop-app-testing in your project. Codex loads it when a task matches its description.

Can I use Desktop App Testing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Porabuild/Poracode --skill desktop-app-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/desktop-app-testing, .gemini/skills/desktop-app-testing, .github/skills/desktop-app-testing and .opencode/skills/desktop-app-testing in your project.

What does Desktop App Testing need to run?

SKILL.md names no scripts, command-line tools or credentials: Desktop App Testing is instructions for the agent only.

Does Desktop App Testing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Desktop App Testing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Desktop App Testing use?

Desktop App Testing is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Desktop App Testing use?

About 557 tokens (SKILL.md is roughly 2.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Desktop App Testing?

Skills that share tags, products or a category with Desktop App Testing: Open Computer Use (iFurySt/open-codex-computer-use, 2.3k stars), Waku Computer Use (egoist/waku, 1.6k stars), Browser MCP Agent (antibrow/anti-detect-browser-skills, 914 stars) and Drive Screen (coleam00/skills, 670 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Desktop App Testing?

Porabuild (a GitHub organization) maintains it in Porabuild/Poracode, which has 114 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 7, 2026.

Source: Porabuild/Poracode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.