Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →camunda/ci-flood-triage
Triages a flood of CI incidents in camunda/camunda.
Passed 5 of 14 test cases with the skill, and 3 of 14 without it.
and 5 more in the full report
6 fixed3 passed either way12 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
Incident INC-4091 just fired for a single flaky integration test failure in the workflow run. Can you perform a deep-dive investigation on INC-4091, analyze its logs, and update its incident status directly?
| Checked | Without skill | With skill |
|---|---|---|
| Redirects the user to /ci-incident for single incident investigation. | Missed | Passed |
| Refuses to perform a multi-incident triage snapshot for a single incident. | Missed | Passed |
The instructions your model reads when the skill loads.
Gives the medic a fast orientation snapshot when a flood of CI incidents opens at once. Finds the shared pattern, flags outliers, and drafts a broadcast message. Read-only by default — generating the snapshot never writes to incident.io. If the medic explicitly asks to merge incidents afterward, this skill can do that too, always with a confirmation step first (see Step 6).
mcp__incident-io__incident_show tool is available.
If not, tell the user to configure the incident.io MCP server
and stop.Throughout this skill, MCP tools are referenced by their short verb (incident_list,
incident_show, incident_update); the actual tool name is namespaced by whichever MCP server
is configured (e.g. mcp__incident-io__incident_list).
Multiple incidents only. If the user passes a single incident ID, redirect them to /ci-incident
for deep-dive investigation of that one incident.
This skill owns the multi-incident merge action when the medic asks for it — it already has the
correlation context (which incidents share a cause) needed to do that safely. /ci-incident is
scoped to driving a single incident's investigation and status updates once assigned; it does not
handle cross-incident merging.
Read the time window from the user's request. Supported forms:
| Argument | Meaning |
|---|---|
| (empty) | last 30 minutes |
60 | last N minutes |
--since 2026-07-06T15:00Z | from that UTC timestamp to now |
--since 2026-07-06T15:00Z --until 2026-07-06T17:30Z | specific historical range |
test cases passed, vs 3 / 14 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.