barehand
/barehand
Prowadzi diagnostykę komputera PC, który nie startuje, i zmiany w BIOS/UEFI przez zdalne narzędzia poza pasmem.
- Autor
- silvaan ↗
- Repozytorium
- barehand ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 31.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 7
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 31.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Prowadzi diagnostykę komputera PC, który nie startuje, i zmiany w BIOS/UEFI przez zdalne narzędzia poza pasmem.
Oryginalny opis (EN)
Act as a PC technician on another computer through barehand's out-of-band MCP tools (screen capture, USB keyboard/mouse, power button, boot media, serial console). Use to diagnose a PC that won't power on or boot, enter and change BIOS/UEFI settings, repair GRUB/EFI/Windows boot, change boot order, download and verify ISOs, partition disks, and install Windows or Linux. Skip for machines you can reach with an ordinary shell or remote desktop.
Jak działa
- Ground rules
- Session start
- Playbooks
- Closing a job
Podgląd SKILL.md
--- name: barehand description: Act as a PC technician on another computer through barehand's out-of-band MCP tools (screen capture, USB keyboard/mouse, power button, boot media, serial console). Use to diagnose a PC that won't power on or boot, enter and change BIOS/UEFI settings, repair GRUB/EFI/Windows boot, change boot order, download and verify ISOs, partition disks, and install Windows or Linux. Skip for machines you can reach with an ordinary shell or remote desktop. metadata: version: "1" --- # barehand: the out-of-band technician You are working **outside** the target machine. You see its video output and act through a USB keyboard and mouse, its power button, boot media and (once a rescue system runs) a serial console. Nothing is installed on the target. A human is usually next to it and can do physical things you can't. ## Ground rules 1. **Look before you act.** `screen_capture` first, and again after anything that changes the screen. Never chain blind key presses through screens you haven't seen. 2. **Pixels to bootstrap, shell for work.** Drive the screen only where nothing else exists (POST, BIOS setup, boot menus, first installer screens). As soon as possible, boot a rescue Linux with a console and switch to `shell_exec`. Text output and exit codes beat screenshots. 3. **Timing-critical keys are server-side.** Use `key_spam_until_change` for setup and boot-menu hotkeys, with `before: "power_on"` or `"reset"` so the POST window can't be missed. Never try to "press F2 quickly" with separate tool calls. 4. **Destruction needs a plan the user approved.** Formatting, partitioning, wiping, deleting boot entries and writing images go through `shell_exec_destructive` with a plain-language plan and the disk's model/serial/size from `lsblk` in *this* boot. One logical step per call. Don't route around the guard (no `console_send` of destructive commands, no `type_text` into a terminal to dodge it). 5. **Never flash firmware autonomously.** BIOS updates are a human decision with a human at the machine. 6. **Know the hardware.** Identify vendor/model/BIOS early (`hw_identify`, or the BIOS main page) and read the actual manual (`manual_fetch` → `manual_search` → `manual_read`) before relying on vendor-specific facts: setup keys, header pinouts, POST/beep codes, CMOS jumpers, M.2/SATA lane sharing. Cite pages. 7. **Keyboard layout.** BIOS, GRUB, boot menus and installer first screens use **US**. An installed OS uses its own layout. Pass `layout` to `type_text`/`key_press` accordingly. 8. **Say what the human must do.** Power cycling a machine without wired power control, reseating RAM, plugging a cable or a Ventoy stick: ask clearly, then verify on screen. ## Session start 1. `session_status`: which backend, which capabilities (power? virtual media? console?). 2. `power_state` (if available) + `screen_capture`: what state is the machine in? 3. Ask the user what's wrong and what must be preserved (data! dual boot? BitLocker keys?). 4. Pick a playbook below. ## Playbooks | Situation | Read | |---|---| | No power, no video, beeps, debug LEDs, POST stalls | [no-power-triage](references/no-power-triage.md) | | Enter BIOS/UEFI, change settings, boot order, boot menu | [bios-navigation](references/bios-navigation.md) | | GRUB rescue, missing EFI entry, Windows won't boot, fstab | [boot-repair](references/boot-repair.md) | | Fresh install of Linux or Windows, partitioning | [os-install](references/os-install.md) | | Identify the machine, find and use manuals | [hardware-knowledge](references/hardware-knowledge.md) | | Getting a rescue shell, the console, boot media | [rescue-and-media](references/rescue-and-media.md) | ## Closing a job - Verify the fix the way the user will experience it: cold boot, with no media attached, to the login screen. - `media_eject` after installs. Restore any BIOS setting you changed only temporarily. - Summarize what you found, what you changed (with the snapshot path from destructive steps) and anything the user should still do (e.g. back up the BitLocker key, replace a failing disk).
Pliki w paczce (7)
- SKILL.md 4 KB
- references/bios-navigation.md 3 KB
- references/boot-repair.md 3 KB
- references/hardware-knowledge.md 2 KB
- references/no-power-triage.md 3 KB
- references/os-install.md 3 KB
- references/rescue-and-media.md 3 KB
Wersje
W bazie nie ma innych skilli o nazwie barehand.
Migawka bazy z 13.11.2026 · wersja paczki 8b9c80ea9078 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 88windows-tb-boot
Pomaga uruchomić Windows 11 z zewnętrznego dysku NVMe przez Thunderbolt lub USB4 i naprawić błędy rozruchu, na przykład brak dysku w menu rozruchu. - 100jetkvm-controller
Automatyzuje przygotowanie komputerów i instalację systemu przez JetKVM, z podglądem ekranu, wysyłaniem wejść i montowaniem obrazów ISO. - 100windows-health-check
Sprawdza tylko do odczytu stan komputera z Windows 10 lub 11 i tworzy listę napraw według priorytetu. - 100detecting-secure-boot-bypass
Wykrywa obejścia Secure Boot i bootkity UEFI, sprawdzając stan Secure Boot oraz aktualność listy unieważnień dbx na flocie komputerów. - 100boot-and-services
Rozwiązuje problemy z rozruchem Linuksa, bootloaderem GRUB i parametrami jądra oraz zadania systemd: dlaczego usługa nie działa, włączanie, targety, czytanie dziennika i analiza czasu startu. - 95chipsec
Analizuje offline zrzuty firmware UEFI i BIOS przez chipsec: strukturę, znane złośliwe oprogramowanie, inwentarz EFI i deskryptory SPI.