agentleFS
termalinapptermalinapp/termalin-plugin/skills/run-commands/SKILL.md

run-commands

Skill0 starsChanged 35 days agoMITView on GitHub

Run shell commands and edit files on the user's servers through Termalin safely. Use whenever a task needs ssh_exec, ssh_exec_many, job_start, sftp_read or sftp_write — installing packages, editing configs, restarting services, tailing logs, running scripts on one or many servers.

  • Deletes or force-pushes
  • Commits and pushes

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Start with hosts_list to get server ids and the connection policy (full access, allowlist or read-only) and the server note.

    line 10
  2. Distinctive:

    If there are no servers, do not improvise: tell the user to add one at https://termal.in/account (Add → Tunnel gives a one-line Connector …

    line 11

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Termalin runs each command on the user's own server through their Connector, authenticated with a short-lived certificate, and records it in their audit log. Treat every call as something the user will read later.

Before running

  • Start with hosts_list to get server ids and the connection policy (full access, allowlist or read-only) and the server note; follow the note, it is the owner's instruction for this machine.
  • If there are no servers, do not improvise: tell the user to add one at https://termal.in/account (Add → Tunnel gives a one-line Connector install) and stop.
  • Pick the login user: the Connector's default unless the user names another. Commands that need root go through sudo only when the policy and the user allow it.

How to run

  • One server, quick command: ssh_exec. Keep output bounded (tail -n, head, --no-pager, -q), the answer is cut at about 90 seconds of wall time.
  • Longer than a minute (builds, migrations, backups, apt-get upgrade, large rsync): job_start, then job_status with lines to follow it, job_stop only on request. Report the job id so the user can ask about it later.
  • The same command on several servers: ssh_exec_many with the ids, at most 10 per call, and report per server.
  • Files: sftp_read before sftp_write, never overwrite blind. Writing a config: keep a copy first (cp file file.bak-$(date +%F) via ssh_exec), write, then validate (nginx -t, sshd -t, apachectl configtest, postgres --check equivalents, docker compose config) and reload only if the user asked for the reload.

What not to do without an explicit yes

  • Anything destructive or hard to undo: rm -rf, dd, disk formatting, DROP, git push --force, reboot, shutdown, firewall changes that could lock the user out, apt-get remove of a running stack, changing sshd_config or the Connector's own service.
  • Printing secrets into the chat: environment files, private keys, /etc/shadow, password fields in configs, tokens in logs. If a task needs such a value, ask the user to provide it or to set it on the server themselves; never copy it into the conversation.
  • Interactive commands (vim, top without -bn1, less, apt prompts): use non-interactive flags (-y, DEBIAN_FRONTEND=noninteractive, --no-pager).
  • Guessing paths and unit names: look first (ls, systemctl list-units | grep), then act.

After running

Say what ran, where, the exit code and the part of the output that matters. If a command failed, show the error and suggest the next step; do not retry blindly with sudo or --force.

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.