Complete Tier 1 triage workflow. Orchestrates the full alert triage process: check-duplicates, triage-alert, enrich-ioc for each entity, and either close (FP/BTP) or escalate (TP/Suspicious). Use for end-to-end alert processing.
Install with Tessl CLI
npx tessl i github:dandye/ai-runbooks --skill full-triage-alert83
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
A composite skill that orchestrates the complete Tier 1 alert triage process from initial receipt to disposition (close or escalate).
CASE_ID or ALERT_ID - The alert/case to triage (required)┌─────────────────────────────────────────────────────────────────┐
│ FULL ALERT TRIAGE │
├─────────────────────────────────────────────────────────────────┤
│ │
│ START │
│ │ │
│ ▼ │
│ ┌─────────────────────┐ │
│ │ /check-duplicates │ │
│ └──────────┬──────────┘ │
│ │ │
│ ┌───────┴───────┐ │
│ ▼ ▼ │
│ DUPLICATE NOT DUPLICATE │
│ │ │ │
│ ▼ ▼ │
│ Close & ┌─────────────────────┐ │
│ Document │ /triage-alert │ │
│ │ └───────────┬─────────┘ │
│ │ │ │
│ │ ┌───────────┴─────────┐ │
│ │ │ For each entity: │ │
│ │ │ /enrich-ioc │ │
│ │ └───────────┬─────────┘ │
│ │ │ │
│ │ ┌───────────┴─────────┐ │
│ │ │ DECISION │ │
│ │ └───────────┬─────────┘ │
│ │ │ │
│ │ ┌───────────────┼────────────────┐ │
│ │ ▼ ▼ ▼ │
│ │ FP/BTP TP/Suspicious Inconclusive │
│ │ │ │ │ │
│ │ ▼ ▼ ▼ │
│ │ /document-in-case /document-in-case /document-in-case │
│ │ /close-case-artifact ESCALATE Request more info │
│ │ │ │ │ │
│ └─────┴──────────────────┴──────────────────┘ │
│ │ │
│ ▼ │
│ /generate-report │
│ │ │
│ ▼ │
│ END │
│ │
└─────────────────────────────────────────────────────────────────┘Step 1.1: Check for Duplicates
Invoke: /check-duplicates CASE_ID=$CASE_ID
/document-in-case with "Closing as duplicate of [Similar Case ID]"/close-case-artifact with reason NOT_MALICIOUSStep 2.1: Perform Alert Triage
Invoke: /triage-alert CASE_ID=$CASE_ID
Extract from results:
CLASSIFICATION - FP, BTP, TP, or SuspiciousKEY_ENTITIES - List of IOCs (IPs, domains, hashes, URLs)ALERT_TYPE - Type of alert (malware, authentication, network, etc.)PRIORITY - Suggested priority levelStep 3.1: Enrich Each Entity
For each entity in KEY_ENTITIES:
Invoke: /enrich-ioc IOC_VALUE=$entity
Collect:
GTI_FINDINGS - Threat intelligence resultsSIEM_CONTEXT - SIEM entity summaryIOC_MATCH_STATUS - Whether IOC appears in threat feedsUpdate CLASSIFICATION if enrichment reveals new information.
Step 4.1: Make Final Classification
Based on triage and enrichment, confirm classification:
| Classification | Criteria | Action |
|---|---|---|
| False Positive (FP) | No malicious indicators, known benign | Close |
| Benign True Positive (BTP) | Real but authorized/expected | Close |
| True Positive (TP) | Confirmed malicious | Escalate |
| Suspicious | Inconclusive, warrants investigation | Escalate |
Step 4.2: Execute Disposition
If FP or BTP:
/document-in-case with:
/close-case-artifact with:
If TP or Suspicious:
/document-in-case with:
/triage-malware/triage-suspicious-login/deep-dive-iocStep 5.1: Generate Triage Report
Invoke: /generate-report REPORT_TYPE=triage
Include:
| Output | Description |
|---|---|
FINAL_CLASSIFICATION | FP, BTP, TP, or Suspicious |
DISPOSITION | Closed or Escalated |
EVIDENCE_SUMMARY | Key findings from triage and enrichment |
REPORT_PATH | Path to generated triage report |
ESCALATION_TARGET | If escalated, recommended next skill/tier |
/check-duplicates fails → Log warning, continue with triage/enrich-ioc fails for an entity → Log warning, continue with other entities/close-case-artifact fails → Log error, manual closure required67a00be
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.