using-software
See and use software as a real user does while checking it: a browser that is already open and signed in, a browser in a universe, agent-browser, computer use, a terminal for a CLI, or a tester for a native or mobile app. Use when choosing how to drive the app and see what a user sees.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- using-software
- description
- See and use software as a real user does while checking it: a browser that is already open and signed in, a browser in a universe, agent-browser, computer use, a terminal for a CLI, or a tester for a native or mobile app. Use when choosing how to drive the app and see what a user sees.
03 SKILL.md 正文
Do what the user would do, through what the user would see. Reading the code or calling the API directly is not using the app; do it only to explain what you saw.
Pick the view
- Web app, and a browser the caller already uses: attach to it rather than starting a new one,
so their sign-in is kept. A Chromium browser started with
--remote-debugging-port=9222is reachable over CDP (http://<host>:9222/json/version); agent-browser attaches with--cdp <url>. A browser extension or bridge the caller named is another way. - Web app, nothing open:
agent-browser, with the using-browser skill; do not install Playwright or another browser. Or a browser in a universe next to the app: a universe can run agent-browser beside the app, as Digital Twin Universe'sweb-testerexample does. - Desktop and native apps: computer use through cua-driver, with the using-computer-use skill.
Use it when nothing else reaches the app, and also when what does reach it would not show what
a user experiences. If it is not enabled, say so instead of guessing. For example:
- An Electron or other desktop app built on web content: a browser against its dev server misses the native window, menus, file dialogs, and tray.
- A UI test hook or API that sets state directly: it passes where a user's clicks would not.
- Canvas, game, or custom-drawn UIs: the DOM or tree says nothing about what is drawn.
- OS-level steps a user goes through: file pickers, permission and sign-in prompts, installers, notifications.
- CLI: run it in a terminal as the user would, with their kind of shell and working directory,
in a universe when it must not touch this machine (
digital-twin-universe exec). - Native or mobile: the platform's tester or simulator (Xcode
simctl, Androidadband an emulator, WinAppDriver), only when installed. A missing one is something that seems off.
Work like a user
- Follow the steps in order and note each one: what you did and what the app showed.
- Wait for what a user waits for: the page settled, the spinner gone, the message shown. Do not sleep blindly; wait on what you can see.
- Sign-in: enter a password or code that was made for this check yourself. A sign-in that belongs to the caller is theirs: use a browser where they are signed in, or open the sign-in page and stop to ask.
- Look past the happy path: slow responses, repeated requests, layout shifts, wording and spacing that differ between pages, and what happens with realistic data or a throttled network.
- Use a page the way a user explores it: scroll below the fold, watch loading and empty states, and submit a form empty or wrong before submitting it right.
- Claim only what you saw happen. When the app does not respond as expected after two tries, or a
page does not load after three, stop and record what you saw. Do not let
curl, the API, or a script stand in for the UI the user uses. - Never turn off certificate checks (
curl -k, ignoring HTTPS errors). A certificate the user's browser would reject is a finding. - Do not change the app to make a step pass. A failure is a finding.
04 同仓库更多 Skills
using-computer-use
Drive any app's real UI on the desktop through the cua-driver CLI: see it in screenshots, read it through its accessibility tree when it has one, click and type. Use for desktop and native apps, and for anything with no better option that is also realistic enough to validate effectively.
using-browser
Drive a web app's real UI in a headless browser through the agent-browser CLI: open pages, read them, click and type, and screenshot them. Use for any software with a web UI.
reaching-software
Reach software where it runs when checking it as a user: a local process, a deployed site, a Digital Twin Universe on this or another machine, or an app that is not running yet. Use when the app, the agent, and the user's view may be on different machines, or a URL does not answer.
gathering-evidence
Decide what evidence to record while checking software, for web, CLI, desktop, and mobile apps, and how to name and store it so a report can point at it. Use before and during any check whose verdicts must stand on what was recorded rather than on what was claimed.
reality-check
Checks that an app works the way a real user would experience it and returns evidence for every finding. Drive it from the command line as `reality-check`, or from Python through `reality_check.lib`. Use whenever a fix or capability needs to be validated: once you have fixed a bug, or built or changed a feature, run a check of what changed before you report the work as done, so the report says what a user can actually do, not only what the code or tests suggest. Also use when asked to check, verify, or make sure an app works, and when the user mentions "reality check" directly.