DevOps (devops)¶
The devops skill specializes the agent for infrastructure access: SSH, host connectivity, remote administration, and server troubleshooting.
| Skill name | devops |
| Library path | /AI/Skills/devops/SKILL.md |
What it is for¶
- Reach remote hosts from the sandbox over SSH / SCP
- Diagnose network and service problems (
dig,curl, remotesystemctl, …) - Apply configuration changes on servers when the operator asks for them
- Use sandbox scripting (jq/yq, Python, shell) as part of an infra workflow
It is not required for ordinary local work that only needs files under /workspace.
Activate it when the task leaves the sandbox and talks to real infrastructure.
How the agent works with this skill¶
- Analyse — local-only vs remote; hostname/IP; user; credentials beyond the default key; desired outcome
- Gather —
web_fetchfor public docs or templates when useful - Execute —
shell_exec,read_file,write_file(scripts in/workspace, then simple remote invocations) - Verify — check exit codes, re-query state, report success or failure with evidence
Sandbox and SSH¶
The sandbox image includes an OpenSSH client. A key may be provisioned for automation-friendly SSH (see harness / sandbox configuration).
Recommended pattern (avoids nested quoting bugs):
write_filea script or payload under/workspaceshell_execa simple command such asscp/sshthat uses that file- Confirm remote state with a follow-up command
Example shape:
scp /workspace/script.sh user@host:/tmp/
ssh user@host "bash /tmp/script.sh"
Safety and control¶
Remote admin is high impact.
Combine this skill with harness vetting so destructive or broad shell_exec patterns pause for operator approval.
Prefer read-only diagnostics before writes; say clearly what will change on the remote host.
Site-specific references¶
Deployments can add infrastructure notes under the skill’s references/ (host lists, networks, jump hosts) in the Library or on a share.
Keep customer-specific inventories out of the default prompt; load them when the skill needs them.
Related¶
- Harness sandbox — where SSH actually runs
lmio-rest-api— prefer API access for LogMan.io product operations when an API exists