Skip to content
Security
Skill

/close-case-artifact

Close a case or alert with proper reason and documentation. Use when triage determines an alert is FP/BTP or investigation is complete. Requires artifact ID, type, closure reason, and root cause.

BOOST
From plugin
ai-runbooks
12830 skills
Install
$ npx -y skills add dandye/ai-runbooks --skill close-case-artifact --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/close-case-artifact

Context preview

The summary Claude sees to decide when to auto-load this skill.

Close a case or alert with proper reason and documentation. Use when triage determines an alert is FP/BTP or investigation is complete. Requires artifact ID, type, closure reason, and root cause.

SKILL.md

close-case-artifact.SKILL.md
type: Skill
name: close-case-artifact
description: "Close a case or alert with proper reason and documentation. Use when triage determines an alert is FP/BTP or investigation is complete. Requires artifact ID, type, closure reason, and root cause."
required_roles:
  soar: roles/chronicle.editor
personas: [tier1-analyst, tier2-analyst, tier3-analyst, incident-responder]
generated:
  by: human:dandye
  at: 2026-02-04T06:10:49-05:00

Close Case Artifact Skill

Close a case or alert with the required reason, root cause, and justification comment.

Inputs

  • `ARTIFACT_ID` - The ID of the case or alert to close
  • `ARTIFACT_TYPE` - Either "Case" or "Alert"
  • `CLOSURE_REASON` - Must be one of:
  • `MALICIOUS` - Confirmed threat
  • `NOT_MALICIOUS` - False positive or benign
  • `MAINTENANCE` - System/maintenance activity
  • `INCONCLUSIVE` - Unable to determine
  • `UNKNOWN` - Unknown/other
  • `ROOT_CAUSE` - Must match a predefined root cause (use `get_case_settings_root_causes` to list options)
  • `CLOSURE_COMMENT` - Detailed justification for closure
  • *(Optional)* `ALERT_GROUP_IDENTIFIERS` - Alert group identifiers
  • *(Optional, for alerts)* `ASSIGN_TO_USER` - User to assign closed alert to
  • *(Optional, for alerts)* `TAGS` - Comma-separated tags

Workflow

Step 1: Execute Closure

**For Cases:**

secops-soar.siemplify_close_case(
    case_id=ARTIFACT_ID,
    reason=CLOSURE_REASON,
    root_cause=ROOT_CAUSE,
    comment=CLOSURE_COMMENT,
    alert_group_identifiers=ALERT_GROUP_IDENTIFIERS
)

**For Alerts:**

secops-soar.siemplify_close_alert(
    alert_id=ARTIFACT_ID,
    reason=CLOSURE_REASON,
    root_cause=ROOT_CAUSE,
    comment=CLOSURE_COMMENT,
    assign_to_user=ASSIGN_TO_USER,
    tags=TAGS
)

Outputs

| Output | Description | |--------|-------------| | `CLOSURE_STATUS` | Success/failure status of the closure |

Common Closure Patterns

| Scenario | Reason | Typical Root Cause | |----------|--------|-------------------| | False Positive | `NOT_MALICIOUS` | "Legit action", "Normal behavior" | | Duplicate | `NOT_MALICIOUS` | "Similar case is already under investigation" | | Benign True Positive | `NOT_MALICIOUS` | "Legit action" | | Confirmed Threat (remediated) | `MALICIOUS` | Varies by threat type | | Unable to determine | `INCONCLUSIVE` | "Insufficient data" |

Get Valid Root Causes

If unsure of valid root cause values:

secops-soar.get_case_settings_root_causes()
Read more
Ships withai-runbooks

This repository provides security operations runbooks and role-based guides for AI-assisted cybersecurity workflows.

Get the whole plugin

Other skills on ai-runbooks.