Agent-skills sysadmin-toolbox
Tool discovery and shell one-liner reference for sysadmin, DevOps, and security tasks. AUTO-CONSULT this skill when the user is: troubleshooting network issues, debugging processes, analyzing logs, working with SSL/TLS, managing DNS, testing HTTP endpoints, auditing security, working with containers, writing shell scripts, or asks 'what tool should I use for X'. Source: github.com/trimstray/the-book-of-secret-knowledge
git clone https://github.com/jdrhyne/agent-skills
T=$(mktemp -d) && git clone --depth=1 https://github.com/jdrhyne/agent-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/sysadmin-toolbox" ~/.claude/skills/jdrhyne-agent-skills-sysadmin-toolbox && rm -rf "$T"
skills/sysadmin-toolbox/SKILL.mdSysadmin Toolbox
Curated tool recommendations and practical shell one-liners for operational work.
When to Auto-Consult
Load relevant references when user is:
- Debugging network connectivity, ports, traffic
- Troubleshooting DNS or SSL/TLS
- Analyzing processes, memory, disk usage
- Working with logs or system diagnostics
- Writing shell scripts or one-liners
- Asking "what's a good tool for..."
- Doing security audits or pentesting
- Working with containers/Docker/K8s
Bundled Guides
| File | Use When |
|---|---|
in this skill's folder | Need practical commands for: terminal, networking, SSL, curl, ssh, tcpdump, git, awk, sed, grep, find |
in this skill's folder | Recommending CLI tools: shells, file managers, network utils, databases, security tools |
in this skill's folder | Web-based tools: SSL checkers, DNS lookup, performance testing, OSINT, scanners |
in this skill's folder | Pentesting, vulnerability scanning, exploit databases, CTF resources |
in this skill's folder | Shell scripting patterns and tricks |
Safety Boundaries
- Do not run destructive system commands, privilege-escalation steps, or offensive tooling unless the user explicitly asked for that scope.
- Do not scan hosts, domains, or networks the user does not control or have permission to assess.
- Do not assume a command is safe to paste into production without explaining what it does.
- Do not persist logs, captures, or credentials outside the user's requested troubleshooting workflow.
Quick Tool Index
Network Debugging
- traceroute + ping combinedmtr
/tcpdump
- packet capturetshark
/netstat
- connection monitoringss
- port scanningnmap
/curl
- HTTP testinghttpie
DNS
/dig
- DNS querieshost
- DNS diagnosticsdnsdiag
/subfinder
- subdomain enumerationamass
SSL/TLS
- certificate inspectionopenssl
- TLS testingtestssl.sh
- SSL scanningsslyze
- Let's Encryptcertbot
Process/System
/htop
- process monitoringbtop
/strace
- syscall/library tracingltrace
- open files/connectionslsof
- disk usagencdu
Log Analysis
- log navigatorlnav
- web log analyzerGoAccess
- log slicingangle-grinder
Containers
- Docker image analysisdive
- container topctop
- Docker TUIlazydocker
Keeping Current
References auto-refresh weekly (Sundays 5am ET) from the upstream repo:
~/clawd-duke-leto/skills/sysadmin-toolbox/scripts/refresh.sh
Manual refresh anytime:
./scripts/refresh.sh [skill-dir]
Example Queries → Actions
"Why is this port not responding?" → Load shell-oneliners.md, search for netstat/ss/lsof commands
"What's a good tool for testing SSL?" → Load cli-tools.md SSL section, recommend testssl.sh or sslyze
"Show me how to find large files" → Load shell-oneliners.md, search for find/ncdu/du commands
"I need to debug DNS resolution" → Load shell-oneliners.md dig section + recommend dnsdiag from cli-tools.md