What problem does it solve? Running persistent services on an Android phone via Termux is tricky: SSH sessions have a broken PATH, Android aggressively kills orphaned background processes, and nohup/setsid do not survive session disconnects. This Skill provides the correct patterns for SSH access, persistent daemons, and boot autostart on Termux. ## Core Features & Use Cases - Persistent services with termux-services (runit): Create, enable, start, and stop runit services under $PREFIX/var/service/sv/ so daemons survive SSH disconnects. - Termux:Boot autostart: Write boot scripts in ~/.termux/boot/ that source the profile, acquire a wake lock, and delay network services until WiFi is up. - SSH access and file transfer: Connect through cloudflared proxy commands, use full binary paths in SSH sessions, and transfer files with scp. - Use Case: Deploy a long-running Python bot on an Android phone by creating a runit service from the Termux app, enabling it with sv-enable, and verifying it survives reboots via a Termux:Boot script. ## Quick Start Set up a persistent Python service on my Termux device using termux-services so it keeps running after my SSH session closes.