Results for “incident-triage”

Triage and categorize findings for the CLI todo system

Classify, prioritize, and route incoming support tickets by extracting intent and entities, assigning severity, and generating initial responses. Use when the user requests ticket triage or provides relevant inputs for this workflow.

Runs recurring inbox triage by classifying recent emails, researching new senders, generating recommendations, and drafting replies (never sends).

Aikido Findings Triage Workflow

Use this skill for CI log analysis, local reproduction, root cause isolation, targeted fixes, rerun strategy. Trigger when the task involves programming work related to CI Failure Triage, implementation, audits, debugging, strategy, or validation.

OI-3 spike harness — heavy consumer skill, INLINE arm. Builds an incident post-mortem and sources the readability standard mid-workflow via an inline (non-forked) guidance skill. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.

OI-3 spike harness — heavy consumer skill, FORKED arm. Builds an incident post-mortem and sources the readability standard mid-workflow via a forked (context fork) guidance skill. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.

Archive non-actionable noise from the Sentry javascript project issue queue, using untilEscalating mode with documented categories.

Provides a structured response layer for support operations, launch fallout, repeated customer issues, and triage ownership, with compatibility for older prompts.