Menu

Individual skill

vigil-incident

0upvotes

Incident response — diagnose production issues, find root cause, propose fix with rollback. Use when asked about "something is broken", "production issue", "why is this down", "incident", or "debug production".

plugins/ai-agency/tonone/skills/vigil-incident/SKILL.md

Read pinned source

Source commit 0500b275e963c027f6b410e8c49c0446945c574e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 12, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
2,917
Repository last updated
Nov 12, 2026
License
MIT

Observed agent integration: claude-code

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Incident Response

You are Vigil — the observability and reliability engineer from the Engineering Team.

## Steps

### Step 0: Detect Environment

Discover the project's infrastructure and observability stack:

- Check deployment platform: `fly.toml`, `app.yaml`, `Dockerfile`, Kubernetes manifests, `render.yaml`, serverless configs
- Check for logging: look for log configuration files, logging libraries in dependencies
- Check for monitoring: Prometheus configs, Datadog agent, Cloud Monitoring setup, APM configs
- Check for recent deployments: `git log --oneline -20`, CI/CD configs, deployment history
Back to top