Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Get Started Free →

CI Incident Response · camunda | DecimalAI

devopsby camunda

CI Incident Response

camunda/ci-incident

Source camunda/camunda ↗License Not recorded

Drive CI incident response in camunda/camunda.

SkillScore29Maintained

Automatic

DevOps & SRE pack

Last verified 9/1/2026

What it changes

Passed 3 of 11 test cases with the skill, and 2 of 11 without it.

Without skill21%

With skill29%

Checks it passed that the model alone missed

Ask the responder for the specific incident ID before proceeding.
Refrain from fetching incident state or Slack logs using the alert ID.
Instruct the user to configure the incident.io MCP server and halt execution.

and 4 more in the full report

5 fixed2 passed either way14 still failing3 broke

Pass-rate lift: +8 pp
Tokens: +66%
Agent turns: 0%
Response time: -24%

Model gemini-3.6-flashMeasured 9/1/2026v37 of 24 cases passed with skill · 11 comparable

Tokens, turns and time describe resource use, not a dollar price.

Use this skill

Save it into your project's skills folder. Claude Code picks it up in its next session.

curl -fsSL --create-dirs -o .claude/skills/camunda-ci-incident/SKILL.md https://app.decimal.ai/s/camunda-ci-incident/SKILL.md

Want it pinned and updatable? pip install "decimalai>=0.15", then decimalai skills add camunda-ci-incident, and start Claude Code with claude --plugin-dir "$(git rev-parse --show-toplevel)/.agents"

1 · One-time — install the CLI (docs ↗)

pip install "decimalai>=0.15"

2 · Get the skill — writes .agents/skills/camunda-ci-incident/ and pins it in .decimal/skills.lock

decimalai skills add camunda-ci-incident

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/camunda-ci-incident/SKILL.md https://app.decimal.ai/s/camunda-ci-incident/SKILL.md

Raw file: /s/camunda-ci-incident/SKILL.md ↗ · machine-readable summary at /s/camunda-ci-incident.json ↗

Safety checks: 3 of 3 passed

Code scan CleanIntent PassedContent Clean

See it in action

One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.

1 of 4

Prompt

Please start handling CI incident INC-101. Note that the incident.io MCP server is not currently connected in this environment.

What was checked, without and with the skill
Checked	Without skill	With skill
Instruct the user to configure the incident.io MCP server and halt execution.	Missed	Passed
Refrain from attempting to proceed with incident state extraction when the required tool is missing.	Missed	Passed

case-19 · gemini-3.6-flash · 9/1/2026 · answers are capped and redacted

What's inside

The instructions your model reads when the skill loads.

SKILL.md138 linessingle file

CI Incident Response

Guides a responder through a CI incident in camunda/camunda. Pulls live state from incident.io, context from the incident's Slack channel, the matching runbook from docs/monorepo-docs/ci-runbooks.md, and the process from docs/monorepo-docs/processes.md.

Prerequisites

incident.io MCP — required. Verify the mcp__incident-io__incident_show tool is available. If not, tell the user to configure the incident.io MCP server and stop.
Slack MCP — preferred but optional. If mcp__*__slack_read_channel is not available, warn the user that Slack context will be skipped and continue.

Throughout this skill, MCP tools are referenced by their short verb (incident_show, slack_read_channel); the actual identifier depends on which MCP server is configured.

Scope

Full incidents only. If the user passes an alert ID (or anything that isn't an incident), stop and ask for the incident ID.

Procedure

Step 1 — Parse the incident ID

Read the incident ID from the user's request. If it is missing, ask the user for it before proceeding. Do not guess from recent context.

Step 2 — Pull incident state

Call incident_show with the ID and include: ["investigation", "postmortem", "roles", "custom_fields"].

Extract and remember:

Title, severity, status, opened-at
Role assignments (lead, comms, etc.)
Active alert name(s)
Incident's Slack channel reference (channel ID or name)
Any existing investigation / postmortem content

Track record

Benchmark

3 / 11

test cases passed, vs 2 / 11 without

Adoption

Users: 0
Times used: 0

Safety and source details

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v5 — 9/1/2026

View 15 scanner checks

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

camunda / camunda

.claude/skills/ci-incident/SKILL.md

View on GitHub ↗

Imported 9/1/2026Version v3

More skills from the same source and nearby in the registry, with their headline benchmark lift.

Ready to supercharge your AI agents?

See it in action

What's inside

CI Incident Response

Prerequisites

Scope

Procedure

Step 1 — Parse the incident ID

Step 2 — Pull incident state

Track record

Benchmark

Adoption

SkillSafety

Source

Related skills