[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E6Q8PTMT7XSCJCMD4XPRW5":3,"skill-same:01M7E6Q8PTMT7XSCJCMD4XPRW5":100},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M7E6Q8PTMT7XSCJCMD4XPRW5","triaging-security-incident-with-ir-playbook",null,"Classifies and prioritizes security incidents using structured IR playbooks and SIEM\u002Fcase-management queries (Splunk, TheHive) to determine severity, assign response teams, and initiate the appropriate response procedures. Use when a new SOC alert needs triage, multiple concurrent incidents require prioritization, or automated triage rules need validation or tuning.","sanjeevafk\u002Fagent-skills","sanjeevafk","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F230678117?v=4","01M7C540EFY46ETG1NNWKS5X3Q","Sanjeev","01M7C540F366J5C1D587BMKH9Q",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Ftriaging-security-incident-with-ir-playbook\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Ftriaging-security-incident-with-ir-playbook\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: triaging-security-incident-with-ir-playbook\ndescription: Classifies and prioritizes security incidents using structured IR\n  playbooks and SIEM\u002Fcase-management queries (Splunk, TheHive) to determine severity,\n  assign response teams, and initiate the appropriate response procedures. Use when\n  a new SOC alert needs triage, multiple concurrent incidents require prioritization,\n  or automated triage rules need validation or tuning.\ndomain: cybersecurity\nsubdomain: incident-response\ntags:\n- incident-response\n- triage\n- playbook\n- severity-classification\n- soc\nmitre_attack:\n- T1486\n- T1490\n- T1070\n- T1078\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- RS.MA-01\n- RS.MA-02\n- RS.AN-03\n- RC.RP-01\n---\n\n# Triaging Security Incidents with IR Playbooks\n\n## When to Use\n- New security alert received from SIEM, EDR, or other detection sources\n- SOC analyst needs to determine if an alert is a true positive requiring response\n- Incident needs severity classification and team assignment\n- Multiple concurrent incidents require prioritization\n- Automated triage rules need validation or tuning\n\n## Prerequisites\n- SIEM platform with alert correlation (Splunk, Elastic, QRadar, Sentinel)\n- Incident response playbook library (by incident type)\n- Severity classification matrix approved by CISO\n- On-call rotation and escalation procedures\n- Ticketing system for incident tracking (ServiceNow, Jira, TheHive)\n- Threat intelligence feeds for IOC enrichment\n\n## Workflow\n\n### Step 1: Receive and Acknowledge Alert\n```bash\n# Query Splunk for new critical\u002Fhigh severity alerts\nindex=notable status=new severity IN (\"critical\",\"high\")\n| table _time, rule_name, src, dest, severity, description\n| sort -_time\n\n# Query TheHive for new cases\ncurl -s -H \"Authorization: Bearer $THEHIVE_API_KEY\" \\\n  \"https:\u002F\u002Fthehive.local\u002Fapi\u002Fv1\u002Fquery?name=list-alerts\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"query\":[{\"_name\":\"listAlert\"},{\"_name\":\"filter\",\"_field\":\"status\",\"_value\":\"New\"}]}'\n\n# Acknowledge alert in SIEM to prevent duplicate triage\ncurl -X POST \"https:\u002F\u002Fsplunk.local:8089\u002Fservices\u002Fnotable_update\" \\\n  -H \"Authorization: Bearer $SPLUNK_TOKEN\" \\\n  -d \"ruleUIDs=$RULE_UID&status=1&comment=Triage+initiated+by+analyst\"\n```\n\n### Step 2: Enrich Alert Data\n```bash\n# Enrich source IP with VirusTotal\ncurl -s \"https:\u002F\u002Fwww.virustotal.com\u002Fapi\u002Fv3\u002Fip_addresses\u002F$SRC_IP\" \\\n  -H \"x-apikey: $VT_API_KEY\" | jq '.data.attributes.last_analysis_stats'\n\n# Check IP reputation with AbuseIPDB\ncurl -s \"https:\u002F\u002Fapi.abuseipdb.com\u002Fapi\u002Fv2\u002Fcheck?ipAddress=$SRC_IP&maxAgeInDays=90\" \\\n  -H \"Key: $ABUSEIPDB_KEY\" -H \"Accept: application\u002Fjson\" | jq '.data'\n\n# Enrich file hash with threat intelligence\ncurl -s \"https:\u002F\u002Fwww.virustotal.com\u002Fapi\u002Fv3\u002Ffiles\u002F$FILE_HASH\" \\\n  -H \"x-apikey: $VT_API_KEY\" | jq '.data.attributes.last_analysis_stats'\n\n# Query internal asset database for affected systems\ncurl -s \"https:\u002F\u002Fcmdb.local\u002Fapi\u002Fassets?ip=$DEST_IP\" \\\n  -H \"Authorization: Bearer $CMDB_TOKEN\" | jq '.asset_criticality, .owner, .environment'\n```\n\n### Step 3: Classify Incident Type\n```bash\n# Map alert to incident category using playbook lookup\n# Categories: Malware, Phishing, Unauthorized Access, Data Exfiltration,\n# DoS\u002FDDoS, Insider Threat, Ransomware, Account Compromise, Web Attack\n\n# Check if alert matches known playbook trigger conditions\ngrep -i \"$ALERT_SIGNATURE\" \u002Fopt\u002Fir\u002Fplaybooks\u002Ftrigger_conditions.yaml\n\n# Determine incident type from MITRE ATT&CK technique\ncurl -s \"https:\u002F\u002Fattack.mitre.org\u002Fapi\u002Ftechniques\u002F$TECHNIQUE_ID\" | jq '.name, .tactic'\n```\n\n### Step 4: Assign Severity Level\n```bash\n# Severity matrix factors:\n# 1. Asset criticality (Critical\u002FHigh\u002FMedium\u002FLow)\n# 2. Data sensitivity (PII\u002FPHI\u002FPCI\u002FConfidential\u002FPublic)\n# 3. Number of affected systems\n# 4. Active vs historical threat\n# 5. Confirmed vs suspected compromise\n\n# Automated severity calculation\npython3 -c \"\nseverity_score = 0\n# Asset criticality: Critical=4, High=3, Medium=2, Low=1\nseverity_score += 4  # Critical server\n# Data sensitivity: PII\u002FPHI=4, PCI=3, Confidential=2, Public=1\nseverity_score += 3  # PCI data\n# Scope: Enterprise=4, Department=3, Single system=2, Single user=1\nseverity_score += 2  # Single system\n# Threat status: Active=4, Recent=3, Historical=2, Potential=1\nseverity_score += 4  # Active threat\n\nif severity_score >= 12: print('CRITICAL - P1')\nelif severity_score >= 9: print('HIGH - P2')\nelif severity_score >= 6: print('MEDIUM - P3')\nelse: print('LOW - P4')\nprint(f'Score: {severity_score}\u002F16')\n\"\n```\n\n### Step 5: Select and Initiate Playbook\n```bash\n# Load appropriate playbook based on incident type\ncat \u002Fopt\u002Fir\u002Fplaybooks\u002Fransomware_playbook.yaml\ncat \u002Fopt\u002Fir\u002Fplaybooks\u002Fphishing_playbook.yaml\ncat \u002Fopt\u002Fir\u002Fplaybooks\u002Funauthorized_access_playbook.yaml\n\n# Create incident ticket in TheHive\ncurl -X POST \"https:\u002F\u002Fthehive.local\u002Fapi\u002Fv1\u002Fcase\" \\\n  -H \"Authorization: Bearer $THEHIVE_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"title\": \"IR-2024-XXX: [Incident Type] - [Brief Description]\",\n    \"description\": \"Triage summary and initial findings\",\n    \"severity\": 3,\n    \"tlp\": 2,\n    \"pap\": 2,\n    \"tags\": [\"ransomware\", \"triage-complete\"],\n    \"customFields\": {\n      \"playbook\": {\"string\": \"ransomware_v2\"},\n      \"affected_systems\": {\"integer\": 5}\n    }\n  }'\n```\n\n### Step 6: Assign Response Team\n```bash\n# Check on-call schedule\ncurl -s \"https:\u002F\u002Fpagerduty.com\u002Fapi\u002Fv2\u002Foncalls?schedule_ids[]=$SCHEDULE_ID\" \\\n  -H \"Authorization: Token token=$PD_TOKEN\" | jq '.oncalls[].user.summary'\n\n# Page incident responders based on severity\n# P1\u002FCritical: Page IR lead + senior analysts + CISO\n# P2\u002FHigh: Page IR lead + available analysts\n# P3\u002FMedium: Assign to next available analyst\n# P4\u002FLow: Queue for business hours processing\n\ncurl -X POST \"https:\u002F\u002Fevents.pagerduty.com\u002Fv2\u002Fenqueue\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"routing_key\": \"'$PD_ROUTING_KEY'\",\n    \"event_action\": \"trigger\",\n    \"payload\": {\n      \"summary\": \"P1 Security Incident: Ransomware detected on PROD-DB-01\",\n      \"severity\": \"critical\",\n      \"source\": \"SIEM-Splunk\",\n      \"custom_details\": {\"incident_id\": \"IR-2024-042\", \"playbook\": \"ransomware_v2\"}\n    }\n  }'\n```\n\n### Step 7: Document Triage Decision and Hand Off\n```bash\n# Update incident ticket with triage summary\ncurl -X PATCH \"https:\u002F\u002Fthehive.local\u002Fapi\u002Fv1\u002Fcase\u002F$CASE_ID\" \\\n  -H \"Authorization: Bearer $THEHIVE_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"status\": \"InProgress\",\n    \"customFields\": {\n      \"triage_analyst\": {\"string\": \"analyst_name\"},\n      \"triage_time\": {\"date\": '$(date +%s000)'},\n      \"severity_justification\": {\"string\": \"Critical asset + active threat + PCI data\"}\n    }\n  }'\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| True Positive | Alert correctly identifying a real security incident |\n| False Positive | Alert incorrectly flagging benign activity as malicious |\n| Severity Classification | Ranking incident priority based on impact and urgency |\n| Playbook Selection | Choosing the appropriate response procedure based on incident type |\n| IOC Enrichment | Adding context to indicators from threat intelligence sources |\n| Escalation Threshold | Criteria triggering escalation to higher severity or management |\n| Triage SLA | Time target for initial assessment (typically 15-30 min for critical) |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| Splunk\u002FElastic\u002FQRadar | SIEM alert correlation and querying |\n| TheHive\u002FSIRP | Incident case management and playbook tracking |\n| VirusTotal\u002FAbuseIPDB | IOC reputation and enrichment |\n| PagerDuty\u002FOpsGenie | On-call management and alerting |\n| MITRE ATT&CK | Technique classification and mapping |\n| Cortex XSOAR | SOAR platform for automated triage workflows |\n\n## Common Scenarios\n\n1. **Brute Force Alert**: Multiple failed logins from single IP. Enrich IP reputation, check geo-location, verify if account was compromised, assign P3 if unsuccessful.\n2. **Malware Detection on Endpoint**: AV\u002FEDR quarantined malware. Verify quarantine success, check for lateral movement, assign P2 if persistence detected.\n3. **Suspicious Outbound Traffic**: Large data transfer to unknown external IP. Check if known cloud service, verify data classification, assign P1 if exfiltration confirmed.\n4. **Phishing Email Reported**: User reports suspicious email. Extract IOCs, check if others received it, assign P2 if credentials were entered.\n5. **Privilege Escalation**: User gained admin rights unexpectedly. Verify if authorized change, check for exploitation, assign P1 if unauthorized.\n\n## Output Format\n- Triage decision document with severity justification\n- Incident ticket with assigned playbook and team\n- IOC enrichment summary attached to case\n- Escalation notification to appropriate stakeholders\n- Initial timeline of events from alert data\n","# Triaging Security Incidents with IR Playbooks\n\n## When to Use\n- New security alert received from SIEM, EDR, or other detection sources\n- SOC analyst needs to determine if an alert is a true positive requiring response\n- Incident needs severity classification and team assignment\n- Multiple concurrent incidents require prioritization\n- Automated triage rules need validation or tuning\n\n## Prerequisites\n- SIEM platform with alert correlation (Splunk, Elastic, QRadar, Sentinel)\n- Incident response playbook library (by incident type)\n- Severity classification matrix approved by CISO\n- On-call rotation and escalation procedures\n- Ticketing system for incident tracking (ServiceNow, Jira, TheHive)\n- Threat intelligence feeds for IOC enrichment\n\n## Workflow\n\n### Step 1: Receive and Acknowledge Alert\n```bash\n# Query Splunk for new critical\u002Fhigh severity alerts\nindex=notable status=new severity IN (\"critical\",\"high\")\n| table _time, rule_name, src, dest, severity, description\n| sort -_time\n\n# Query TheHive for new cases\ncurl -s -H \"Authorization: Bearer $THEHIVE_API_KEY\" \\\n  \"https:\u002F\u002Fthehive.local\u002Fapi\u002Fv1\u002Fquery?name=list-alerts\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"query\":[{\"_name\":\"listAlert\"},{\"_name\":\"filter\",\"_field\":\"status\",\"_value\":\"New\"}]}'\n\n# Acknowledge alert in SIEM to prevent duplicate triage\ncurl -X POST \"https:\u002F\u002Fsplunk.local:8089\u002Fservices\u002Fnotable_update\" \\\n  -H \"Authorization: Bearer $SPLUNK_TOKEN\" \\\n  -d \"ruleUIDs=$RULE_UID&status=1&comment=Triage+initiated+by+analyst\"\n```\n\n### Step 2: Enrich Alert Data\n```bash\n# Enrich source IP with VirusTotal\ncurl -s \"https:\u002F\u002Fwww.virustotal.com\u002Fapi\u002Fv3\u002Fip_addresses\u002F$SRC_IP\" \\\n  -H \"x-apikey: $VT_API_KEY\" | jq '.data.attributes.last_analysis_stats'\n\n# Check IP reputation with AbuseIPDB\ncurl -s \"https:\u002F\u002Fapi.abuseipdb.com\u002Fapi\u002Fv2\u002Fcheck?ipAddress=$SRC_IP&maxAgeInDays=90\" \\\n  -H \"Key: $ABUSEIPDB_KEY\" -H \"Accept: application\u002Fjson\" | jq '.data'\n\n# Enrich file hash with threat intelligence\ncurl -s \"https:\u002F\u002Fwww.virustotal.com\u002Fapi\u002Fv3\u002Ffiles\u002F$FILE_HASH\" \\\n  -H \"x-apikey: $VT_API_KEY\" | jq '.data.attributes.last_analysis_stats'\n\n# Query internal asset database for affected systems\ncurl -s \"https:\u002F\u002Fcmdb.local\u002Fapi\u002Fassets?ip=$DEST_IP\" \\\n  -H \"Authorization: Bearer $CMDB_TOKEN\" | jq '.asset_criticality, .owner, .environment'\n```\n\n### Step 3: Classify Incident Type\n```bash\n# Map alert to incident category using playbook lookup\n# Categories: Malware, Phishing, Unauthorized Access, Data Exfiltration,\n# DoS\u002FDDoS, Insider Threat, Ransomware, Account Compromise, Web Attack\n\n# Check if alert matches known playbook trigger conditions\ngrep -i \"$ALERT_SIGNATURE\" \u002Fopt\u002Fir\u002Fplaybooks\u002Ftrigger_conditions.yaml\n\n# Determine incident type from MITRE ATT&CK technique\ncurl -s \"https:\u002F\u002Fattack.mitre.org\u002Fapi\u002Ftechniques\u002F$TECHNIQUE_ID\" | jq '.name, .tactic'\n```\n\n### Step 4: Assign Severity Level\n```bash\n# Severity matrix factors:\n# 1. Asset criticality (Critical\u002FHigh\u002FMedium\u002FLow)\n# 2. Data sensitivity (PII\u002FPHI\u002FPCI\u002FConfidential\u002FPublic)\n# 3. Number of affected systems\n# 4. Active vs historical threat\n# 5. Confirmed vs suspected compromise\n\n# Automated severity calculation\npython3 -c \"\nseverity_score = 0\n# Asset criticality: Critical=4, High=3, Medium=2, Low=1\nseverity_score += 4  # Critical server\n# Data sensitivity: PII\u002FPHI=4, PCI=3, Confidential=2, Public=1\nseverity_score += 3  # PCI data\n# Scope: Enterprise=4, Department=3, Single system=2, Single user=1\nseverity_score += 2  # Single system\n# Threat status: Active=4, Recent=3, Historical=2, Potential=1\nseverity_score += 4  # Active threat\n\nif severity_score >= 12: print('CRITICAL - P1')\nelif severity_score >= 9: print('HIGH - P2')\nelif severity_score >= 6: print('MEDIUM - P3')\nelse: print('LOW - P4')\nprint(f'Score: {severity_score}\u002F16')\n\"\n```\n\n### Step 5: Select and Initiate Playbook\n```bash\n# Load appropriate playbook based on incident type\ncat \u002Fopt\u002Fir\u002Fplaybooks\u002Fransomware_playbook.yaml\ncat \u002Fopt\u002Fir\u002Fplaybooks\u002Fphishing_playbook.yaml\ncat \u002Fopt\u002Fir\u002Fplaybooks\u002Funauthorized_access_playbook.yaml\n\n# Create incident ticket in TheHive\ncurl -X POST \"https:\u002F\u002Fthehive.local\u002Fapi\u002Fv1\u002Fcase\" \\\n  -H \"Authorization: Bearer $THEHIVE_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"title\": \"IR-2024-XXX: [Incident Type] - [Brief Description]\",\n    \"description\": \"Triage summary and initial findings\",\n    \"severity\": 3,\n    \"tlp\": 2,\n    \"pap\": 2,\n    \"tags\": [\"ransomware\", \"triage-complete\"],\n    \"customFields\": {\n      \"playbook\": {\"string\": \"ransomware_v2\"},\n      \"affected_systems\": {\"integer\": 5}\n    }\n  }'\n```\n\n### Step 6: Assign Response Team\n```bash\n# Check on-call schedule\ncurl -s \"https:\u002F\u002Fpagerduty.com\u002Fapi\u002Fv2\u002Foncalls?schedule_ids[]=$SCHEDULE_ID\" \\\n  -H \"Authorization: Token token=$PD_TOKEN\" | jq '.oncalls[].user.summary'\n\n# Page incident responders based on severity\n# P1\u002FCritical: Page IR lead + senior analysts + CISO\n# P2\u002FHigh: Page IR lead + available analysts\n# P3\u002FMedium: Assign to next available analyst\n# P4\u002FLow: Queue for business hours processing\n\ncurl -X POST \"https:\u002F\u002Fevents.pagerduty.com\u002Fv2\u002Fenqueue\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"routing_key\": \"'$PD_ROUTING_KEY'\",\n    \"event_action\": \"trigger\",\n    \"payload\": {\n      \"summary\": \"P1 Security Incident: Ransomware detected on PROD-DB-01\",\n      \"severity\": \"critical\",\n      \"source\": \"SIEM-Splunk\",\n      \"custom_details\": {\"incident_id\": \"IR-2024-042\", \"playbook\": \"ransomware_v2\"}\n    }\n  }'\n```\n\n### Step 7: Document Triage Decision and Hand Off\n```bash\n# Update incident ticket with triage summary\ncurl -X PATCH \"https:\u002F\u002Fthehive.local\u002Fapi\u002Fv1\u002Fcase\u002F$CASE_ID\" \\\n  -H \"Authorization: Bearer $THEHIVE_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"status\": \"InProgress\",\n    \"customFields\": {\n      \"triage_analyst\": {\"string\": \"analyst_name\"},\n      \"triage_time\": {\"date\": '$(date +%s000)'},\n      \"severity_justification\": {\"string\": \"Critical asset + active threat + PCI data\"}\n    }\n  }'\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| True Positive | Alert correctly identifying a real security incident |\n| False Positive | Alert incorrectly flagging benign activity as malicious |\n| Severity Classification | Ranking incident priority based on impact and urgency |\n| Playbook Selection | Choosing the appropriate response procedure based on incident type |\n| IOC Enrichment | Adding context to indicators from threat intelligence sources |\n| Escalation Threshold | Criteria triggering escalation to higher severity or management |\n| Triage SLA | Time target for initial assessment (typically 15-30 min for critical) |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| Splunk\u002FElastic\u002FQRadar | SIEM alert correlation and querying |\n| TheHive\u002FSIRP | Incident case management and playbook tracking |\n| VirusTotal\u002FAbuseIPDB | IOC reputation and enrichment |\n| PagerDuty\u002FOpsGenie | On-call management and alerting |\n| MITRE ATT&CK | Technique classification and mapping |\n| Cortex XSOAR | SOAR platform for automated triage workflows |\n\n## Common Scenarios\n\n1. **Brute Force Alert**: Multiple failed logins from single IP. Enrich IP reputation, check geo-location, verify if account was compromised, assign P3 if unsuccessful.\n2. **Malware Detection on Endpoint**: AV\u002FEDR quarantined malware. Verify quarantine success, check for lateral movement, assign P2 if persistence detected.\n3. **Suspicious Outbound Traffic**: Large data transfer to unknown external IP. Check if known cloud service, verify data classification, assign P1 if exfiltration confirmed.\n4. **Phishing Email Reported**: User reports suspicious email. Extract IOCs, check if others received it, assign P2 if credentials were entered.\n5. **Privilege Escalation**: User gained admin rights unexpectedly. Verify if authorized change, check for exploitation, assign P1 if unauthorized.\n\n## Output Format\n- Triage decision document with severity justification\n- Incident ticket with assigned playbook and team\n- IOC enrichment summary attached to case\n- Escalation notification to appropriate stakeholders\n- Initial timeline of events from alert data\n",{"name":5,"tags":25,"author":31,"domain":32,"license":15,"version":33,"nist_csf":34,"subdomain":26,"description":7,"mitre_attack":39},[26,27,28,29,30],"incident-response","triage","playbook","severity-classification","soc","mahipal","cybersecurity","1.0",[35,36,37,38],"RS.MA-01","RS.MA-02","RS.AN-03","RC.RP-01",[40,41,42,43],"T1486","T1490","T1070","T1078","main","4e084e84eb42fc53e144c89c0f7f48b39c8a4b0f","collections\u002Fcybersecurity-skills\u002Fskills\u002Ftriaging-security-incident-with-ir-playbook",1,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills","https:\u002F\u002Fgithub.com\u002Fsanjeevafk","First make it work. Then make it right. Then make it fast.","2026-11-14 13:36:16",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add sanjeevafk\u002Fagent-skills --skill triaging-security-incident-with-ir-playbook",{"tool":58,"command":59},"bunx","bunx skills add sanjeevafk\u002Fagent-skills --skill triaging-security-incident-with-ir-playbook",{"tool":61,"command":62},"pnpm","pnpm dlx skills add sanjeevafk\u002Fagent-skills --skill triaging-security-incident-with-ir-playbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Ftriaging-security-incident-with-ir-playbook\u002FSKILL.md",true,[66,72,76,82,86,90,96],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"assets\u002Ftemplate.md","ASSET","资产文件",2921,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Ftriaging-security-incident-with-ir-playbook\u002Fassets\u002Ftemplate.md",{"path":73,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fapi-reference.md","REFERENCE","参考文档",1963,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Ftriaging-security-incident-with-ir-playbook\u002Freferences\u002Fapi-reference.md",{"path":83,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fstandards.md",2361,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Ftriaging-security-incident-with-ir-playbook\u002Freferences\u002Fstandards.md",{"path":87,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fworkflows.md",4705,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Ftriaging-security-incident-with-ir-playbook\u002Freferences\u002Fworkflows.md",{"path":91,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"scripts\u002Fagent.py","SCRIPT","脚本",8659,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Ftriaging-security-incident-with-ir-playbook\u002Fscripts\u002Fagent.py",{"path":97,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":98,"sourceHtmlUrl":99},"scripts\u002Fprocess.py",15558,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Ftriaging-security-incident-with-ir-playbook\u002Fscripts\u002Fprocess.py",[101,109,117,125,133,140],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":105,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":20},"01M7EFHX67M3KKXT1BXVPA5ADT","zarr-python","Chunked N-D arrays for cloud storage (Zarr-Python 3). Compressed arrays, parallel I\u002FO, S3\u002FGCS via fsspec, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","MIT","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":105,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":20},"01M7EFFQGM51TZBGRENXY50ZYM","whiteboard-diagrams","Create accurate, simple, hand-drawn whiteboard diagrams from a user's process, system, architecture, learning workflow, comparison, or causal explanation. Use when the user asks for a scribbly whiteboard visual, educational workflow graphic, hand-drawn explainer, or diagram like the bundled reference; ask one focused clarification question when the subject or relationships are missing, then generate and visually verify the final image.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwhiteboard-diagrams\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwhiteboard-diagrams\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":20},"01M7EFF1CSQNTDMHFK4ZGY6NYK","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":129,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":20},"01M7EFE8106X6C28FT8PA74427","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":105,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":20},"01M7EFCSNZM9G7ZHS6F127Q71X","verification-loop","A comprehensive verification system for Claude Code sessions.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":105,"licenseFileUrl":144,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":20},"01M7EFCE7EZMKPRYDDNKBQ9EEH","vercel-deploy","Deploy applications and websites to Vercel. Use when the user requests deployment actions like \"deploy my app\", \"deploy and give me the link\", \"push this live\", or \"create a preview deployment\".","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-deploy\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-deploy\u002FSKILL.md",[],[]]