macmini-offload

Offloads CPU- and memory-intensive tasks to a remote Mac mini over SSH.

366|90|Updated Aug 22, 2026
One-click install
npx skills add https://github.com/bam-bam-2/solo-skills --skill macmini-offload-bam-bam-2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: macmini-offload
Source: https://github.com/bam-bam-2/solo-skills/tree/main/skills/remote-offload
Command: npx skills add https://github.com/bam-bam-2/solo-skills --skill macmini-offload-bam-bam-2

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Running heavy workloads like headless scraping, media encoding, builds, and bulk API collection on an 8GB MacBook Air causes memory pressure and kills the user's browser tabs. This Skill routes those jobs to a more capable remote Mac mini over SSH so the local machine stays responsive. ## Core Features & Use Cases - Remote execution via SSH: Sends scripts to the remote host with scp and runs them with a login shell so Homebrew PATH resolves correctly. - Background job runner: Uses a run.sh runner with start/status/tail/log/list commands so long jobs survive SSH disconnects and can be polled later. - Fail-safe behavior: Checks remote availability first and aborts instead of falling back to local execution, protecting the low-memory laptop. - Use Case: You need to scrape hundreds of pages with Playwright or encode a video with ffmpeg. Write the script locally, scp it to the Mac mini's offload workspace, run it in the background, and retrieve the output files with scp when done. ## Quick Start Offload this ffmpeg video encoding job to the Mac mini and fetch the output file when it finishes.

Frequently Asked Questions about macmini-offload

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run heavy scripts on a remote Mac over SSH?

Write the script to a local file, copy it to the remote host with scp, then execute it with ssh using a login shell (bash -lc) so Homebrew PATH resolves. For long jobs, launch through a runner script with nohup so the process survives SSH disconnects.

How to run background jobs over SSH that survive disconnects?

Wrap the command with nohup and redirect output to a log file on the remote host, then poll its status later. The offload.sh script supports a --bg flag that starts the job detached and prints the remote PID and log path.

What tasks should be offloaded to a remote machine?

Offload headless browser scraping, ffmpeg encoding, npm installs and builds, bulk API pagination, and large file parsing. Keep tasks needing local login sessions, interactive UI, or sub-second lookups on the local machine since SSH round-trips cost more than they save.

What happens if the remote host is unreachable?

The script checks connectivity with a BatchMode SSH probe and a 10-second timeout. If the remote host does not respond, it aborts with an error instead of falling back to local execution, since running heavy jobs locally risks memory exhaustion.

Why do SSH commands fail to find brew-installed tools?

Non-interactive SSH sessions do not load the login shell profile, so Homebrew paths are missing. Prefix the command with bash -lc to start a login shell, which sources the profile and exposes tools like ffmpeg and node.