agentleFS
Sign inStart free
frontier-ai-nextfrontier-ai-next/mgarlbot/skills/vps_host_ssh/SKILL.md

vps_host_ssh

Skill17 starsChanged 4 months agoMITView on GitHub

Run commands on the VPS host OS via preconfigured SSH from the mgarlbot container

  • Reads credentials
  • Deletes or force-pushes
  • Installs packages

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    When the user asks to install a package on the VPS, run a command on the server, apt on the host, etc.

    line 11
  2. Very specific:

    Use one shell invocation:

    line 15
  3. Very specific:

    After install, verify: ssh -F /data/.ssh/config vps 'command -v NAME || NAME --version'.

    line 29
  4. Very specific:

    Never paste private keys or secret material from ~/.ssh.

    line 38
  5. Very specific:

    Do not suggest destructive host commands (rm -rf /, disk wipe, etc.).

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

VPS host — always via ssh, never “bare” apt inside the bot container

When the user asks to install a package on the VPS, run a command on the server, apt on the host, etc. — do not ask for IP, login, or distro unless they volunteered it. Assume access is already wired.

Fixed wrapper

Use one shell invocation:

ssh -F /data/.ssh/config vps 'REMOTE_COMMAND_HERE'
  • Host alias vps, config /data/.ssh/config, keys and UserKnownHostsFile live on the mounted /data volume (on the host: mgarlbot data dir).

Non-interactive apt on Debian/Ubuntu:

ssh -F /data/.ssh/config vps 'DEBIAN_FRONTEND=noninteractive apt-get update && apt-get install -y PACKAGE_NAME'

After install, verify: ssh -F /data/.ssh/config vps 'command -v NAME || NAME --version'.

Do not confuse with the container

  • apt install without ssh ... vps installs into the container (often fails without root). For the host, always prefix ssh -F /data/.ssh/config vps '...'.
  • docker / docker compose against the host daemon — use the compose/socket setup on that machine, not this SSH wrapper, unless the user asked for OS-level edits on the host.

Rules

  • Never paste private keys or secret material from ~/.ssh.
  • Do not suggest destructive host commands (rm -rf /, disk wipe, etc.).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free