agentleFS
michaelnealemichaelneale/mesh-llm/.agents/skills/remote-observable-process/SKILL.md

remote-observable-process

Skill3.8k starsChanged 20 days agoApache-2.0View on GitHub

Use this skill when starting, supervising, debugging, holding open, or stopping any remote process over SSH that needs an operator-like interactive environment, a TTY, login-shell startup files, long-running observation, logs, readiness checks, or later inspection.

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill before starting a non-trivial remote process over SSH when the process needs to behave like it was launched by an operator …

    line 10
  2. Very specific:

    If a macOS same-LAN join or split fails, or remote macOS nodes on the same LAN connect only via relay, check the deploy-macos skill's Local …

    line 17
  3. Distinctive:

    If the remote host does not use zsh, adapt the shell while preserving the same properties: allocate a TTY, use a login/interactive shell, …

    line 34
  4. Distinctive:

    Avoid detached first attempts such as:

    line 38
  5. Very specific:

    Keep the SSH session open while sending traffic.

    line 57

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

remote-observable-process

Use this skill before starting a non-trivial remote process over SSH when the process needs to behave like it was launched by an operator in a terminal, be observed after launch, expose readiness, keep running beyond one command, or be stopped cleanly later.

macOS Local Network privacy

If a macOS same-LAN join or split fails, or remote macOS nodes on the same LAN connect only via relay, check the deploy-macos skill's Local Network troubleshooting section before diagnosing iroh (not a routine preflight; SSH/shell launches normally just work). A raw UDP probe, a LAN address in an invite, or relay connectivity is not proof that the deployed process was authorized. Do not collect performance data until both nodes report the intended LAN peer as an iroh direct path.

Rule

For environment-sensitive processes, prefer SSH with a TTY and an interactive login shell:

ssh -tt host '/bin/zsh -ilc '\''COMMAND'\'''

If the remote host does not use zsh, adapt the shell while preserving the same properties: allocate a TTY, use a login/interactive shell, and keep the session foreground for first repro/debug runs.

Avoid detached first attempts such as:

ssh host "nohup COMMAND > /tmp/process.log 2>&1 &"
ssh host "COMMAND > /tmp/process.log 2>&1 &"

Those shapes hide lifecycle and can behave differently from a real remote session.

Stage Runtime Debugging

For network-sensitive server chains, model stage servers, GPU/Metal workloads, or bind/connect debugging, first prove the process in a held foreground TTY:

ssh -tt host '/bin/zsh -ilc '\''COMMAND 2>&1 | tee /tmp/COMMAND.log'\'''

Keep the SSH session open while sending traffic. Use tmux or screen only after validating that they preserve the same listener, downstream connection, and request behavior on that host.

Download now (ZIP)

Trending

Quiet since April.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 4 mentionsApr 2026: 14 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the michaelneale/mesh-llm repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about michaelneale/mesh-llm

The biggest 5 of 18 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 18

Talked about on GitHub, Bluesky and Hacker News (18 times).

On GitHub · 15

10 more on GitHub

On Hacker News · 1

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.