agentleFS
ThakurvaibhavThakurvaibhav/platform-agent-harness/skills/investigate-alert/SKILL.md

investigate-alert

Skill2 starsChanged 9 days agoApache-2.0View on GitHub

Investigate a firing alert from a Slack link/message or alert title to determine cause, scope, and impact. Read-only SRE triage. Use when the user asks to investigate, triage, or look into an alert, points at an alert in Slack, gives an alert name, or asks why an alert is firing.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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:

    Read-only SRE triage using the alert-investigator agent and agent-knowledge/references/playbook-alert-investigation.md.

    line 12
  2. Distinctive:

    If neither was supplied, ask for one.

    line 19
  3. Distinctive:

    If delegation is unavailable or forbidden, follow the same agent and playbook directly.

    line 25
  4. Very specific:

    Never mutate resources, acknowledge/resolve/silence alerts, or implement remediation.

    line 31
  5. Distinctive:

    Use available Grafana, Prometheus, Loki, Sift, gcx, kubectl, gcloud, and aws read-only capabilities.

    line 33

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

Investigate Alert

Read-only SRE triage using the alert-investigator agent and agent-knowledge/references/playbook-alert-investigation.md.

What to do

  1. Capture a Slack link/message or alert title/name, plus the user's context. If neither was supplied, ask for one. If Slack access is unavailable, use pasted text or the title and report missing thread context.
  2. Dispatch alert-investigator through the runtime's supported delegation mechanism. Pass the alert input, constraints, and instruction: "Follow agent-knowledge/references/playbook-alert-investigation.md. Stay read-only. Return the triage card, separating evidence from assumptions." If delegation is unavailable or forbidden, follow the same agent and playbook directly.
  3. Relay the triage card. Surface proposed learnings for approval. Show any Slack reply as a draft; never send it.

Notes

  • Never mutate resources, acknowledge/resolve/silence alerts, or implement remediation. Recommendations belong in NEXT STEP for a human.
  • Use available Grafana, Prometheus, Loki, Sift, gcx, kubectl, gcloud, and aws read-only capabilities. Your incident-management tool, if you have one, is optional.
  • For gcx query examples, consult references/alert-investigation-patterns.md.

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.