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.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- reaching-software
- description
- 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.
03 SKILL.md 正文
A check has three places, and each can be on a different machine: where you run, where the software runs, and where the user's view is (a browser, a screen, a terminal, a device). Find out which is which before you open anything.
Find where it runs
- A URL in the request: open it from where the user's view will be, not only from here.
- A port on this machine:
ss -ltnp(Linux),lsof -iTCP -sTCP:LISTEN(macOS), ornetstat -ano(Windows) shows what listens and on which address. - A universe:
digital-twin-universe listandstatus --id <id>give its state and the URLs the host can open. - A repository and no running app: launch it in a new universe from a profile
(
digital-twin-universe create-profile, orlaunchwith an existing one), as if deployed. Use the project's own profile when it has one; otherwise base a new one on how the project's docs, scripts, or compose files start it. Destroy it after the check unless asked to keep it.
localhost is relative
localhost means the machine or container the request runs in.
- From inside a container or universe, the host's
localhostis not reachable. Use the host's LAN address or name, orhost.docker.internalwhere Docker provides it. - From a browser on another machine, use the serving machine's LAN IP, hostname, or Tailscale
name, such as
http://home-server-2:3000. A server bound to127.0.0.1answers only locally; say so in the report rather than changing how it is started without being asked. - Check reachability first with
curl -sS -o /dev/null -w '%{http_code} %{time_total}\n' <url>from the place the user's view is. That shows the URL answers, not that the UI works.
Other machines
- SSH: run commands there with
ssh <host> '<command>', and forward a port withssh -N -L 3000:localhost:3000 <host>sohttp://localhost:3000here reaches the app there. Use only keys and hosts already configured; never create or change them. - Tailscale:
tailscale statuslists the machines on the tailnet and their names; a tailnet name works like a LAN name. - A universe on another machine: run
digital-twin-universethere over SSH. Its URLs arelocalhoston that machine, so reach them through a port forward or that machine's name.
When it cannot be reached
Name what you tried, from where, and what answered: the URL, the command, and its output. A check that could not reach the software reports each item as not checked, never as a pass.
04 同仓库更多 Skills
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.
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.
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.