Index of every page on this site: llms.txt
All skills
matisolina avatar

/computer-troubleshooting

@3dd91e1
by Mati Solinamatisolina/busy98 stars
14
Run it yourself

Load when your own computer misbehaves, i.e. bash commands fail or hang, the desktop command or browser tools return errors, Chrome won't open or keeps restarting, refs stop working, or the live screen is blank, before you give up or tell the user it's broken.

  • 1 file
  • 4.1 KB
  • Updated 2 weeks ago
  • GitHub
Use this Skill: https://skilld.dev/gh/matisolina/busy/computer-troubleshooting

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈72 tokens for metadata: the name and description. ≈975 when used: this file.

Description uses 3.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈287 characters, or 3.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

When your computer misbehaves

Your computer is a Linux machine with a desktop (display :99), Chrome, persistent /data and temporary /workspace. Diagnose calmly, keep the user posted only at real milestones, and never claim a task finished when the computer blocked it.

1. Is it up?

  • Run a trivial bash command (echo ok; df -h /data /workspace). If it answers, the computer is running. Check free disk while you're there.
  • A first start, or a start after the computer stopped while idle, can take a while. If a tool says the computer is starting or times out once, wait a few seconds and retry once or twice before concluding anything.
  • The computer may stop between idle messages. /data stays; a later turn may resume the same screen or start a fresh one.

2. After any restart, refs are stale

If the screen, the desktop session or Chrome restarted (or the user took control), every old accessibility ref is invalid. Take a fresh browser__snapshot (or a fresh desktop snapshot) before any click or fill. Never replay an old ref or a failed click blindly.

3. What the common errors mean

  • USER_CONTROL_ACTIVE, CONTROL_BUSY, BROWSERERROR_USERCONTROL: the user (or another task) is controlling the screen. Pause, tell the user, wait until control returns, then take a fresh snapshot.
  • CONTROL_LOST: control changed hands during your action. Take a fresh snapshot and check what actually happened before continuing.
  • BROWSER_OBSERVATION_REQUIRED: you must take a fresh snapshot before acting on refs.
  • BROWSER_GENERATION_CHANGED: Chrome restarted mid-batch; nothing more was sent. Snapshot again and redo only the steps that didn't happen.
  • BROWSER_ENDPOINT_UNAVAILABLE, BROWSER_UNMANAGED, an unavailable CDP endpoint: the managed Chrome isn't reachable, or a Chrome was started outside the managed launcher. Don't launch google-chrome yourself; reopen the page with browser__open, which starts the managed Chrome.
  • BROWSER_DESKTOP_UNREADY: the desktop session isn't ready yet. Wait a few seconds and retry.
  • BROWSER_LAUNCH_FAILED: Chrome couldn't start. Retry once; if it fails again, check the logs below.
  • BATCH_* errors: the browser__batch input was invalid or hit a step or time limit. Read the step statuses and the final snapshot, fix the batch, and don't repeat steps that already succeeded.
  • desktop command errors: run desktop <command> --help for the right flags, and re-read desktop skills get desktop if you haven't this conversation.

4. Read-only diagnostics

Use bash only to look, not to repair:

  • Desktop logs: ls /tmp/desktop-*.log and tail -n 50 the relevant one (Xvfb, openbox, accessibility, panel, file manager).
  • Processes: pgrep -a chrome, pgrep -a Xvfb.
  • The computer image version: cat /etc/busy-image-version.
  • Disk: df -h. If /workspace is full, delete your own temporary files there; never delete the user's files in /data.

Don't kill processes, delete lock files, reinstall packages, edit system configuration, or drive the screen with xdotool to force things. Don't use curl or scripts to replace the visible browser.

5. When it needs a reset

You can't reset your own computer. If the desktop, browser or live screen keep failing after a fresh snapshot and a couple of retries, or a notice says your computer comes from an older image, tell the user plainly:

"My computer needs a reset. Files in /data are kept, but browser logins may be lost."

There is no reset button in the Busy app, so don't invent one; the reset is done by whoever runs this Busy installation. Meanwhile, offer what you can still do without the screen (connected apps, files, bash).

6. Software you installed

Packages and tools you installed outside /data may be gone after a reset or a fresh computer. Reinstall what you need. Keep anything that must last (scripts, outputs, notes) in /data.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 3dd91e1. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 2 weeks ago

README badge

README badge for matisolina/busy/computer-troubleshooting