agentleFS
termalinapptermalinapp/termalin-plugin/skills/incident-triage/SKILL.md

incident-triage

Skill0 starsChanged 34 days agoMITView on GitHub

Work through a server alert or outage step by step — disk full, high load, service down, OOM, certificate expiring, server offline. Use when the user pastes an alert, says something is down or slow, or asks why a server misbehaves.

23 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use write-runbook, threat-hunting and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MaheshAwasareSkill

    write-runbook

    Generate an operational runbook for a service from its code, config, and dependencies — what to do when it breaks, where to look, how to roll back, who to escalate to. Use proactively before a service goes to production, after a major incident, or when handing off operational ownership.

    Also in 3 projects that use this

  • allanninalSkill

    threat-hunting

    Hunt threats using Sigma detection rules and security analysis techniques. Use when investigating security incidents, creating detection rules, or analyzing suspicious activity.

    Also in 3 projects that use this

  • srclightSkill

    explore-codebase

    This skill should be used when the user asks to "explore this codebase", "understand this project", "give me an overview", "how does this work", "onboard me", "walk me through the architecture", "map the codebase", or any request to understand a codebase's structure, architecture, or design.

    Also in 3 projects that use this

  • thlaureSkill

    review-change

    Use this skill when the user asks for a code review, a correctness pass, a check before PR, or asks whether a Signalist change follows project conventions.

    Also in 4 projects that use this

  • SentrySkill

    write-tests

    Write tests following project conventions. Use when adding new tests or modifying existing ones.

    Also in 3 projects that use this

  • MicrosoftSkill

    api-design

    Guide for designing and documenting RESTful APIs. Use when asked to design an API, create endpoints, or document an API.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 0

    Distinctive

    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. Very specific:

    Run these with ssh_exec as needed.

    line 15
  2. Very specific:

    Keep output short: use tail, head, -n.

    line 25

“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “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

Triage in a fixed order, read-only first, and stop to ask before any change.

1. Frame it

  • Which server? Resolve the name with hosts_list. If the alert came from Termalin, alerts_list has the current state and when it started.
  • Pull server_metrics for that host with hours: 24 to see the trend: a disk that fills steadily and a disk that jumped are different problems.

2. Look, with read-only commands

Run these with ssh_exec as needed; they change nothing:

  • Disk: df -h, then du -xsh /var/log /var/lib/docker /home /tmp 2>/dev/null | sort -h, journalctl --disk-usage, docker system df if Docker is there.
  • Memory / OOM: free -m, ps aux --sort=-%mem | head -15, dmesg -T | grep -i -E 'oom|killed process' | tail -20.
  • Load / CPU: uptime, top -bn1 | head -25, ps aux --sort=-%cpu | head -15, iostat -x 1 3 or vmstat 1 5 when I/O is suspected.
  • Service down: systemctl status <unit> --no-pager -l, journalctl -u <unit> -n 100 --no-pager, ss -tlnp to see what is actually listening.
  • Server offline per Termalin but the user says it is up: the Connector itself may be down; check systemctl status termalin-agent from another path or ask the user to look at the machine.
  • Certificate: openssl x509 -in <path> -noout -enddate, and whether a renewal timer exists: systemctl list-timers | grep -i -E 'certbot|acme'.
  • Website slow: curl -s -o /dev/null -w '%{http_code} %{time_total}s' https://<domain>/, then the web server and app logs.

Keep output short: use tail, head, -n. Anything that could run longer than a minute goes through job_start and job_status, not ssh_exec.

3. Explain

Give one paragraph: what is wrong, the evidence (numbers, log lines), the likely cause. Then a numbered plan, with the first step being the least destructive thing that stops the bleeding (rotate logs, clear a cache, restart one service) and the real fix after it.

4. Fix only with consent

Do not restart services, delete files, kill processes or change configs until the user says yes to the specific step. For deletion prefer the reversible form: journalctl --vacuum-size=500M, apt-get clean, docker image prune -f (not -a unless agreed). After each change, re-check the metric that triggered the alert and say whether it recovered.

Respect the connection's policy and the server note Termalin shows in the tool output; a read-only connection cannot perform fixes, say so instead of trying.

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.