agentleFS
KogaCyberKogaCyber/jarvis-skills/skills/server-check/SKILL.md

server-check

Skill0 starsChanged 3 months agoMITView on GitHub

Health check a remote server — uptime, disk, memory, Docker containers, service logs. Use when the user says "check the server", "server status", "is prod alive", or "show me the logs".

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Run over SSH, all in one connection:

    line 16
  2. Distinctive:

    If the user named a project, also tail its logs:

    line 27
  3. Distinctive:

    Don't dump raw command output at the user unless they ask — summarize, flag anomalies, suggest the fix.

    line 41
  4. Distinctive:

    If something is red: propose the fix (restart container, clear disk, check logs deeper) and ask "fix it?" — don't auto-restart production …

    line 45

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

Server Health Check

One command from the user → full picture of the server.

Config

Servers are listed in ~/.jarvis/servers.md (see the deploy skill). Never hardcode hosts or passwords in this file.

Checks

Run over SSH, all in one connection:

ssh $USER@$HOST '
  echo "=== uptime ===";  uptime
  echo "=== disk ===";    df -h / | tail -1
  echo "=== memory ===";  free -h | grep Mem
  echo "=== docker ===";  docker ps --format "table {{.Names}}\t{{.Status}}\t{{.Ports}}"
'

If the user named a project, also tail its logs:

ssh $USER@$HOST "docker logs --tail 30 $PROJECT 2>&1"

Report Format

Short summary, problems first:

  • 🔴 anything down, restarting, or erroring in logs
  • 🟡 disk > 80%, memory > 90%, container restarted recently
  • 🟢 one line: "all N containers up, disk X%, mem Y%"

Don't dump raw command output at the user unless they ask — summarize, flag anomalies, suggest the fix.

Escalation

If something is red: propose the fix (restart container, clear disk, check logs deeper) and ask "fix it?" — don't auto-restart production services without a go-ahead.

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.