agentleFS
Sign inStart free
bks-labbks-lab/open-bridge/skills/remote/SKILL.md

remote

Skill13 starsChanged 13 days agoMITView on GitHub

Owns `infra/remotes/*.yaml` — fleet ops (inventory, WoL, SSH/RDP, reachability, shutdown/reboot) + service ops (health, logs, restart, deploy). "remote" = physical machine, not git remote. Triggers: "remote", "my PC", "my machines", "fleet", "wake", "WoL", "ssh to", "RDP", machine names (homeserver, workstation, laptop, router).

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the referenced file ONLY when triggered.

    line 11

≈ “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

Remote

Manage remote machines defined in infra/remotes/*.yaml. Read the referenced file ONLY when triggered.

Guard

remotes.enabled must be true in bridge-config.yaml. If not: inform and exit.

Arguments

ArgumentEffectDefault
(none)Dashboard of all remotes—
{hostname}Detail view of one remote—
health {hostname}SSH health check—
logs {hostname} {service}Show recent logs—
restart {hostname} {service}Restart service—
sync {hostname}Sync config files—
wake {hostname}Wake-on-LAN—
connect {hostname}Open SSH / RDP session—
shutdown {hostname}Power off (requires [y])—
reboot {hostname}Restart machine (requires [y])—

Decision Tree

User wants to...
├── Remote overview / dashboard        → Read references/workflow.md (§ Dashboard)
├── Detail view of one machine         → Read references/workflow.md (§ Dashboard, single host)
├── Wake / power on a machine          → Read references/fleet.md (§ Stage 3 WoL)
├── Connect via SSH / RDP              → Read references/fleet.md (§ Stage 4 Connect)
├── Reboot or shutdown                 → Read references/fleet.md (§ Stage 5)
├── Check reachability / online?       → Read references/fleet.md (§ Stage 2)
├── Update inventory after a change    → Read references/fleet.md (§ Stage 6)
├── Health check for a machine         → Read references/workflow.md (§ Health Check)
├── View service logs                  → Read references/workflow.md (§ Logs)
├── Restart a service                  → Read references/workflow.md (§ Restart)
├── Sync config to a remote            → Read references/workflow.md (§ Sync)
├── Deploy services to a remote        → Read references/workflow.md (§ Deploy)
├── Identify "my PC" / intent-only     → Read references/fleet.md (§ Stage 1 + Learned routing)
└── Questions about remotes            → Answer from infra/remotes/_template.yaml + docs/remotes.md

A machine that stays on can carry the capability arm: the always-on machine that runs the watchers and writes the inbox (docs/always-on-machine.md).

Reference map

FileOwns
references/fleet.mdInventory, WoL, connect, shutdown, reachability, "my PC" routing
references/workflow.mdService dashboard, health, logs, restart, sync, deploy

Hard Rules (non-negotiable)

  • Tailscale first, LAN as fallback — LAN fails on VPN or foreign networks
  • No destructive operation (shutdown, reboot, format) without per-action [y]
  • Never store credentials in infra/remotes/*.yaml — KeyVault / 1Password URIs only
  • Honor wake_on_lan.enabled: false — never force wake a machine that opted out
  • Read infra/remotes/{target}.yaml before any operation — no guessing

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