incident

Create factual incident records with timestamps and error messages as Markdown files.

3|2|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/fluxforgeai/ARTEMIS --skill incident-fluxforgeai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident
Source: https://github.com/fluxforgeai/ARTEMIS/tree/main/.claude/skills/incident
Command: npx skills add https://github.com/fluxforgeai/ARTEMIS --skill incident-fluxforgeai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture an authoritative, timestamped, and factual record of operational incidents without performing investigation or root-cause analysis, ensuring teams have a neutral source of truth for subsequent workflows.

Core Features & Use Cases

  • Enforces factual, non-speculative language and a chronological timeline for incidents.
  • Writes a structured Markdown report to docs/incidents/{YYYY-MM-DD_HHMM}_{name}.md using a consistent template including Timeline, Impact, and Current Status.
  • Use cases: on-call engineers logging production outages, QA recording reproducible test failures, or monitoring systems summarizing observed errors and raw evidence for handoff to investigators.

Quick Start

Invoke /incident with a concise factual description like "backend returned 429 at 14:02:15 UTC, observed increased error rate and retries" to create the incident report file.

Frequently Asked Questions about incident

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

FAQPage Schema
How do I create a factual incident report without including speculative root cause analysis?

To create a factual incident report, you log raw evidence, timestamps, and error messages using neutral language. This approach captures exactly what happened during an operational incident without performing speculative root cause analysis, providing a reliable source of truth for later review.

What is the best way to log a chronological timeline for production outages on call?

Logging a chronological timeline for production outages requires capturing timestamped events and raw evidence as they occur. This records the exact sequence of operational failures and error messages in a structured format for handoff to investigators.

Can I use this to document reproducible test failures and observed errors for QA handoff?

Yes, you can document reproducible test failures and observed errors for QA handoff. The tool records factual operational incidents by capturing timestamps and error messages, creating a neutral record suitable for engineering and operations workflows.

Does this incident logging tool write structured Markdown files for operations workflows?

Yes, this incident logging tool writes structured Markdown files for operations workflows. It outputs reports to a designated docs directory, enforcing a consistent template that includes required sections for Timeline, Impact, and Current Status.

When should I not use an incident report template for operational incident logging?

You should not use this incident report template for operational incident logging when you need to perform root-cause analysis or investigations. It is designed exclusively to capture factual, chronological evidence and raw error messages using non-speculative language.