ai-triage

Analyzes incident logs to detect recurring failures and queue remediation tasks.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/Vimurai/ai-os --skill ai-triage-vimurai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ai-triage
Source: https://github.com/Vimurai/ai-os/tree/main/.claude/skills/ai-triage
Command: npx skills add https://github.com/Vimurai/ai-os --skill ai-triage-vimurai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Recurring failures buried in growing incident logs go unnoticed until they cause repeated outages. This Skill automates the analysis of the incidents.ndjson log, groups failures by stack signature, drafts post-mortems, and queues remediation tasks so patterns are addressed before they escalate. ## Core Features & Use Cases - Automated Incident Analysis: Invokes the sre_responder agent to parse incidents.ndjson, group entries by stack_signature, and count duplicate failures. - Post-Mortem Drafting: Generates POSTMORTEM.md entries for any failure signature occurring three or more times. - Task Queueing: Creates E-## remediation tasks in TASKS.md via the task-synchronizer MCP and stamps results with [SRE_PASS] or [SRE_FAIL]. - Use Case: Your incidents.ndjson file has grown past 10 KB after a week of errors. Run this Skill to identify that a null-pointer signature appeared 12 times, get a post-mortem drafted, and have a remediation task queued for the Engineer automatically. ## Quick Start Run the ai-triage skill to analyze the current incidents log and queue remediation tasks for any recurring failure patterns.

Frequently Asked Questions about ai-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate incident log analysis for recurring failures?▼

Run the ai-triage skill, which invokes the sre_responder agent to parse incidents.ndjson, group entries by stack_signature, and count duplicates. Signatures with three or more occurrences get post-mortem drafts and queued remediation tasks automatically.

When should incident triage run on an NDJSON log file?▼

Triage should run once daily during off-peak hours as part of a scheduled job, or immediately when incidents.ndjson exceeds 10 KB (roughly 200 lines). Files with two or fewer lines are skipped since no pattern exists yet.

What happens if the sre_responder agent is not found?▼

The skill logs a warning to stderr and exits without attempting to inline the agent logic. You should verify that src/claude/agents/sre_responder.md exists before rerunning the triage.

Can the skill repair a corrupted incidents.ndjson file?▼

No. If the first NDJSON line fails to parse with jq, the skill reports the file as malformed and stops. Manual recovery or deletion is required; the file is treated as read-only and never modified automatically.

How are false-positive remediation tasks handled?▼

When a task is disputed as a false positive, the skill uses handoff_control to escalate to the Architect for policy review rather than Engineer remediation, including the task ID, reason, and post-mortem reference.