[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M734KVT462K3GD5GZXKQ58Y7":3,"skill-same:01M734KVT462K3GD5GZXKQ58Y7":109},{"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":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M734KVT462K3GD5GZXKQ58Y7","implementing-soar-playbook-with-palo-alto-xsoar",null,"Implement automated incident response playbooks in Cortex XSOAR to orchestrate security workflows across SOC tools and reduce manual response time.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-soar-playbook-with-palo-alto-xsoar\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-soar-playbook-with-palo-alto-xsoar\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: implementing-soar-playbook-with-palo-alto-xsoar\ndescription: Implement automated incident response playbooks in Cortex XSOAR to orchestrate\n  security workflows across SOC tools and reduce manual response time.\ndomain: cybersecurity\nsubdomain: soc-operations\ntags:\n- xsoar\n- soar\n- palo-alto\n- playbook\n- automation\n- incident-response\n- orchestration\n- cortex\nmitre_attack:\n- T1078\n- T1685.002\n- T1685.005\n- T1566\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- DE.CM-01\n- DE.AE-02\n- RS.MA-01\n- DE.AE-06\nsource: https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\nsource_commit: 04450304b12645cb2b974ab96d28c0664758a88d\nnote: \"Vendored verbatim from an external Apache-2.0 security-skill library, pinned by commit. Exceeds the internal 300-line skill guideline (agent-code-constraints.md) -- kept as-is because this is vendored reference material (forensics\u002Fthreat-intel procedure), not Yana AI-authored content, and trimming would damage technical accuracy.\"\n---\n\n# Implementing SOAR Playbook with Palo Alto XSOAR\n\n## Overview\n\nCortex XSOAR (formerly Demisto) is Palo Alto Networks' Security Orchestration, Automation, and Response platform. Playbooks are the core automation engine in XSOAR, enabling SOC teams to automate repetitive incident response tasks. XSOAR provides 900+ prebuilt integration packs, 87 common playbooks, and a visual drag-and-drop editor for building custom workflows. Organizations using SOAR automation reduce mean time to respond (MTTR) by 80% on average.\n\n\n## When to Use\n\n- When deploying or configuring implementing soar playbook with palo alto xsoar capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Cortex XSOAR deployed (version 8.x or later, or XSOAR hosted)\n- Administrative access for playbook creation\n- Integration packs installed for relevant security tools\n- Incident types and layouts configured\n- API access to external tools (SIEM, EDR, TI platforms, ticketing)\n\n## Playbook Architecture\n\n### XSOAR Component Hierarchy\n\n```\nIncident Type (e.g., Phishing)\n    |\n    v\nIncident Layout (UI display configuration)\n    |\n    v\nPre-Processing Rules (auto-classification, deduplication)\n    |\n    v\nPlaybook (automation logic)\n    |-- Sub-Playbooks (modular reusable workflows)\n    |-- Tasks (individual automation steps)\n    |-- Conditional Tasks (decision branches)\n    |-- Scripts (custom Python\u002FJavaScript)\n    |-- Integrations (external tool commands)\n    |\n    v\nWar Room (investigation timeline)\n    |\n    v\nClosing Report\n```\n\n### Playbook Task Types\n\n| Task Type | Purpose | Example |\n|---|---|---|\n| Standard | Execute a command | `!ip ip=8.8.8.8` |\n| Conditional | Branch logic | If severity > high, escalate |\n| Manual | Require analyst input | Approve containment action |\n| Section Header | Organize workflow | \"Enrichment Phase\" |\n| Data Collection | Gather external data | Ask user for additional details |\n| Timer | Wait for condition\u002Ftime | Wait 5 minutes then check |\n\n## Building a Phishing Response Playbook\n\n### Step 1: Define Incident Type\n\n```yaml\nincident_type: Phishing\nplaybook: Phishing Investigation - Full\nseverity_mapping:\n  - condition: email contains executable attachment\n    severity: high\n  - condition: email from external domain with link\n    severity: medium\n  - condition: email reported by user\n    severity: low\nlayout: Phishing Layout\nsla: 60 minutes\n```\n\n### Step 2: Playbook YAML Structure\n\n```yaml\nid: phishing-investigation-full\nversion: -1\nname: Phishing Investigation - Full\ndescription: Automated phishing email investigation with enrichment, analysis, and response\nstarttaskid: \"0\"\ntasks:\n  \"0\":\n    id: \"0\"\n    taskid: start\n    type: start\n    nexttasks:\n      '#none#':\n      - \"1\"\n  \"1\":\n    id: \"1\"\n    taskid: extract-indicators\n    type: regular\n    task:\n      name: Extract Indicators from Email\n      script: ParseEmailFiles\n    nexttasks:\n      '#none#':\n      - \"2\"\n      - \"3\"\n      - \"4\"\n  \"2\":\n    id: \"2\"\n    taskid: enrich-urls\n    type: playbook\n    task:\n      name: URL Enrichment\n      playbookName: URL Enrichment - Generic v2\n  \"3\":\n    id: \"3\"\n    taskid: enrich-files\n    type: playbook\n    task:\n      name: File Enrichment\n      playbookName: File Enrichment - Generic v2\n  \"4\":\n    id: \"4\"\n    taskid: enrich-ips\n    type: playbook\n    task:\n      name: IP Enrichment\n      playbookName: IP Enrichment - Generic v2\n  \"5\":\n    id: \"5\"\n    taskid: determine-verdict\n    type: condition\n    task:\n      name: Is Email Malicious?\n    conditions:\n      - label: \"yes\"\n        condition:\n          - - operator: isEqualString\n              left: DBotScore.Score\n              right: \"3\"\n      - label: \"no\"\n    nexttasks:\n      \"yes\":\n      - \"6\"\n      \"no\":\n      - \"9\"\n  \"6\":\n    id: \"6\"\n    taskid: block-sender\n    type: regular\n    task:\n      name: Block Sender Domain\n      script: '|||o365-mail-block-sender'\n    scriptarguments:\n      sender_address: ${incident.emailfrom}\n  \"7\":\n    id: \"7\"\n    taskid: search-mailboxes\n    type: regular\n    task:\n      name: Search and Delete from All Mailboxes\n      script: '|||o365-mail-purge-compliance-search'\n    scriptarguments:\n      query: \"from:${incident.emailfrom} subject:${incident.emailsubject}\"\n  \"8\":\n    id: \"8\"\n    taskid: notify-user\n    type: regular\n    task:\n      name: Notify Reporting User\n      script: '|||send-mail'\n    scriptarguments:\n      to: ${incident.reporter}\n      subject: \"Phishing Report Confirmed - Action Taken\"\n      body: \"The email you reported has been confirmed as malicious and removed.\"\n  \"9\":\n    id: \"9\"\n    taskid: close-incident\n    type: regular\n    task:\n      name: Close Incident\n      script: closeInvestigation\n```\n\n### Step 3: Integration Commands\n\n#### Email Analysis\n```\n!ParseEmailFiles entryid=${File.EntryID}\n!rasterize url=${URL.Data} type=png\n```\n\n#### Threat Intelligence Enrichment\n```\n!url url=${URL.Data}\n!file file=${File.SHA256}\n!ip ip=${IP.Address}\n!domain domain=${Domain.Name}\n```\n\n#### Containment Actions\n```\n!o365-mail-block-sender sender=${incident.emailfrom}\n!o365-mail-purge-compliance-search query=\"from:${incident.emailfrom}\"\n!pan-os-block-ip ip=${IP.Address} log_forwarding=\"default\"\n!cortex-xdr-isolate-endpoint endpoint_id=${Endpoint.ID}\n```\n\n#### Ticketing Integration\n```\n!jira-create-issue summary=\"Phishing Incident - ${incident.id}\" type=\"Incident\" priority=\"High\"\n!servicenow-create-ticket short_description=\"Security Incident\" urgency=\"2\"\n```\n\n## Common SOC Playbook Templates\n\n### 1. Malware Investigation Playbook\n\n```\nTrigger: Malware alert from EDR\nSteps:\n  1. Extract file hash, process details, host info\n  2. Enrich hash via VirusTotal, Hybrid Analysis\n  3. Check if file is on allowlist\n  4. If malicious:\n     a. Isolate endpoint via EDR\n     b. Block hash on all endpoints\n     c. Search for hash across environment\n     d. Create incident ticket\n  5. If clean: Close as false positive\n```\n\n### 2. Account Compromise Playbook\n\n```\nTrigger: Impossible travel or suspicious login alert\nSteps:\n  1. Get user details from Active Directory\n  2. Get login history for past 30 days\n  3. Check for impossible travel (geo-distance vs time)\n  4. Check for known VPN\u002Fproxy IP\n  5. If compromised:\n     a. Disable AD account\n     b. Revoke all OAuth tokens\n     c. Reset MFA\n     d. Notify user's manager\n     e. Search for lateral movement\n  6. If false positive: Document and close\n```\n\n### 3. DDoS Mitigation Playbook\n\n```\nTrigger: Network anomaly alert\nSteps:\n  1. Verify traffic spike from network monitoring\n  2. Identify source IPs and geolocation\n  3. Check if source IPs are known botnets\n  4. Implement rate limiting on WAF\n  5. If sustained attack:\n     a. Enable upstream DDoS protection\n     b. Activate CDN scrubbing\n     c. Notify ISP if needed\n  6. Monitor and document\n```\n\n## Custom XSOAR Scripts\n\n### Python Automation Script Example\n\n```python\n# XSOAR Automation Script: CalculateRiskScore\ndef calculate_risk_score():\n    \"\"\"Calculate composite risk score for an incident.\"\"\"\n    severity = demisto.incident().get('severity', 0)\n    indicator_count = len(demisto.get(demisto.context(), 'DBotScore', []))\n    malicious_count = len([\n        i for i in demisto.get(demisto.context(), 'DBotScore', [])\n        if i.get('Score', 0) == 3\n    ])\n\n    base_score = severity * 20\n    indicator_boost = min(indicator_count * 5, 25)\n    malicious_boost = malicious_count * 15\n\n    risk_score = min(100, base_score + indicator_boost + malicious_boost)\n\n    return_results(CommandResults(\n        outputs_prefix='RiskScore',\n        outputs={'Score': risk_score, 'Level': 'Critical' if risk_score > 80 else 'High' if risk_score > 60 else 'Medium'},\n        readable_output=f'Risk Score: {risk_score}\u002F100'\n    ))\n\ncalculate_risk_score()\n```\n\n## Playbook Performance Metrics\n\n| Metric | Before SOAR | After SOAR | Improvement |\n|---|---|---|---|\n| Phishing MTTR | 45 min | 5 min | 89% reduction |\n| Malware MTTR | 60 min | 8 min | 87% reduction |\n| Account Compromise MTTR | 30 min | 4 min | 87% reduction |\n| Alerts Handled per Shift | 50 | 200+ | 300% increase |\n| False Positive Handling | 10 min | 30 sec | 95% reduction |\n\n## References\n\n- [Cortex XSOAR Playbooks Overview](https:\u002F\u002Fxsoar.pan.dev\u002Fdocs\u002Fplaybooks\u002Fplaybooks-overview)\n- [From Zero to Process to XSOAR Playbook](https:\u002F\u002Flive.paloaltonetworks.com\u002Ft5\u002Fcommunity-blogs\u002Ffrom-zero-to-process-to-xsoar-playbook\u002Fba-p\u002F564568)\n- [XSOAR Common Playbooks Pack](https:\u002F\u002Fwww.paloaltonetworks.com\u002Fblog\u002Fsecurity-operations\u002Fplaybook-of-the-week-xsoar-common-playbook\u002F)\n- [Cortex XSOAR Product Page](https:\u002F\u002Fwww.paloaltonetworks.com\u002Fcortex\u002Fcortex-xsoar)\n","# Implementing SOAR Playbook with Palo Alto XSOAR\n\n## Overview\n\nCortex XSOAR (formerly Demisto) is Palo Alto Networks' Security Orchestration, Automation, and Response platform. Playbooks are the core automation engine in XSOAR, enabling SOC teams to automate repetitive incident response tasks. XSOAR provides 900+ prebuilt integration packs, 87 common playbooks, and a visual drag-and-drop editor for building custom workflows. Organizations using SOAR automation reduce mean time to respond (MTTR) by 80% on average.\n\n\n## When to Use\n\n- When deploying or configuring implementing soar playbook with palo alto xsoar capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Cortex XSOAR deployed (version 8.x or later, or XSOAR hosted)\n- Administrative access for playbook creation\n- Integration packs installed for relevant security tools\n- Incident types and layouts configured\n- API access to external tools (SIEM, EDR, TI platforms, ticketing)\n\n## Playbook Architecture\n\n### XSOAR Component Hierarchy\n\n```\nIncident Type (e.g., Phishing)\n    |\n    v\nIncident Layout (UI display configuration)\n    |\n    v\nPre-Processing Rules (auto-classification, deduplication)\n    |\n    v\nPlaybook (automation logic)\n    |-- Sub-Playbooks (modular reusable workflows)\n    |-- Tasks (individual automation steps)\n    |-- Conditional Tasks (decision branches)\n    |-- Scripts (custom Python\u002FJavaScript)\n    |-- Integrations (external tool commands)\n    |\n    v\nWar Room (investigation timeline)\n    |\n    v\nClosing Report\n```\n\n### Playbook Task Types\n\n| Task Type | Purpose | Example |\n|---|---|---|\n| Standard | Execute a command | `!ip ip=8.8.8.8` |\n| Conditional | Branch logic | If severity > high, escalate |\n| Manual | Require analyst input | Approve containment action |\n| Section Header | Organize workflow | \"Enrichment Phase\" |\n| Data Collection | Gather external data | Ask user for additional details |\n| Timer | Wait for condition\u002Ftime | Wait 5 minutes then check |\n\n## Building a Phishing Response Playbook\n\n### Step 1: Define Incident Type\n\n```yaml\nincident_type: Phishing\nplaybook: Phishing Investigation - Full\nseverity_mapping:\n  - condition: email contains executable attachment\n    severity: high\n  - condition: email from external domain with link\n    severity: medium\n  - condition: email reported by user\n    severity: low\nlayout: Phishing Layout\nsla: 60 minutes\n```\n\n### Step 2: Playbook YAML Structure\n\n```yaml\nid: phishing-investigation-full\nversion: -1\nname: Phishing Investigation - Full\ndescription: Automated phishing email investigation with enrichment, analysis, and response\nstarttaskid: \"0\"\ntasks:\n  \"0\":\n    id: \"0\"\n    taskid: start\n    type: start\n    nexttasks:\n      '#none#':\n      - \"1\"\n  \"1\":\n    id: \"1\"\n    taskid: extract-indicators\n    type: regular\n    task:\n      name: Extract Indicators from Email\n      script: ParseEmailFiles\n    nexttasks:\n      '#none#':\n      - \"2\"\n      - \"3\"\n      - \"4\"\n  \"2\":\n    id: \"2\"\n    taskid: enrich-urls\n    type: playbook\n    task:\n      name: URL Enrichment\n      playbookName: URL Enrichment - Generic v2\n  \"3\":\n    id: \"3\"\n    taskid: enrich-files\n    type: playbook\n    task:\n      name: File Enrichment\n      playbookName: File Enrichment - Generic v2\n  \"4\":\n    id: \"4\"\n    taskid: enrich-ips\n    type: playbook\n    task:\n      name: IP Enrichment\n      playbookName: IP Enrichment - Generic v2\n  \"5\":\n    id: \"5\"\n    taskid: determine-verdict\n    type: condition\n    task:\n      name: Is Email Malicious?\n    conditions:\n      - label: \"yes\"\n        condition:\n          - - operator: isEqualString\n              left: DBotScore.Score\n              right: \"3\"\n      - label: \"no\"\n    nexttasks:\n      \"yes\":\n      - \"6\"\n      \"no\":\n      - \"9\"\n  \"6\":\n    id: \"6\"\n    taskid: block-sender\n    type: regular\n    task:\n      name: Block Sender Domain\n      script: '|||o365-mail-block-sender'\n    scriptarguments:\n      sender_address: ${incident.emailfrom}\n  \"7\":\n    id: \"7\"\n    taskid: search-mailboxes\n    type: regular\n    task:\n      name: Search and Delete from All Mailboxes\n      script: '|||o365-mail-purge-compliance-search'\n    scriptarguments:\n      query: \"from:${incident.emailfrom} subject:${incident.emailsubject}\"\n  \"8\":\n    id: \"8\"\n    taskid: notify-user\n    type: regular\n    task:\n      name: Notify Reporting User\n      script: '|||send-mail'\n    scriptarguments:\n      to: ${incident.reporter}\n      subject: \"Phishing Report Confirmed - Action Taken\"\n      body: \"The email you reported has been confirmed as malicious and removed.\"\n  \"9\":\n    id: \"9\"\n    taskid: close-incident\n    type: regular\n    task:\n      name: Close Incident\n      script: closeInvestigation\n```\n\n### Step 3: Integration Commands\n\n#### Email Analysis\n```\n!ParseEmailFiles entryid=${File.EntryID}\n!rasterize url=${URL.Data} type=png\n```\n\n#### Threat Intelligence Enrichment\n```\n!url url=${URL.Data}\n!file file=${File.SHA256}\n!ip ip=${IP.Address}\n!domain domain=${Domain.Name}\n```\n\n#### Containment Actions\n```\n!o365-mail-block-sender sender=${incident.emailfrom}\n!o365-mail-purge-compliance-search query=\"from:${incident.emailfrom}\"\n!pan-os-block-ip ip=${IP.Address} log_forwarding=\"default\"\n!cortex-xdr-isolate-endpoint endpoint_id=${Endpoint.ID}\n```\n\n#### Ticketing Integration\n```\n!jira-create-issue summary=\"Phishing Incident - ${incident.id}\" type=\"Incident\" priority=\"High\"\n!servicenow-create-ticket short_description=\"Security Incident\" urgency=\"2\"\n```\n\n## Common SOC Playbook Templates\n\n### 1. Malware Investigation Playbook\n\n```\nTrigger: Malware alert from EDR\nSteps:\n  1. Extract file hash, process details, host info\n  2. Enrich hash via VirusTotal, Hybrid Analysis\n  3. Check if file is on allowlist\n  4. If malicious:\n     a. Isolate endpoint via EDR\n     b. Block hash on all endpoints\n     c. Search for hash across environment\n     d. Create incident ticket\n  5. If clean: Close as false positive\n```\n\n### 2. Account Compromise Playbook\n\n```\nTrigger: Impossible travel or suspicious login alert\nSteps:\n  1. Get user details from Active Directory\n  2. Get login history for past 30 days\n  3. Check for impossible travel (geo-distance vs time)\n  4. Check for known VPN\u002Fproxy IP\n  5. If compromised:\n     a. Disable AD account\n     b. Revoke all OAuth tokens\n     c. Reset MFA\n     d. Notify user's manager\n     e. Search for lateral movement\n  6. If false positive: Document and close\n```\n\n### 3. DDoS Mitigation Playbook\n\n```\nTrigger: Network anomaly alert\nSteps:\n  1. Verify traffic spike from network monitoring\n  2. Identify source IPs and geolocation\n  3. Check if source IPs are known botnets\n  4. Implement rate limiting on WAF\n  5. If sustained attack:\n     a. Enable upstream DDoS protection\n     b. Activate CDN scrubbing\n     c. Notify ISP if needed\n  6. Monitor and document\n```\n\n## Custom XSOAR Scripts\n\n### Python Automation Script Example\n\n```python\n# XSOAR Automation Script: CalculateRiskScore\ndef calculate_risk_score():\n    \"\"\"Calculate composite risk score for an incident.\"\"\"\n    severity = demisto.incident().get('severity', 0)\n    indicator_count = len(demisto.get(demisto.context(), 'DBotScore', []))\n    malicious_count = len([\n        i for i in demisto.get(demisto.context(), 'DBotScore', [])\n        if i.get('Score', 0) == 3\n    ])\n\n    base_score = severity * 20\n    indicator_boost = min(indicator_count * 5, 25)\n    malicious_boost = malicious_count * 15\n\n    risk_score = min(100, base_score + indicator_boost + malicious_boost)\n\n    return_results(CommandResults(\n        outputs_prefix='RiskScore',\n        outputs={'Score': risk_score, 'Level': 'Critical' if risk_score > 80 else 'High' if risk_score > 60 else 'Medium'},\n        readable_output=f'Risk Score: {risk_score}\u002F100'\n    ))\n\ncalculate_risk_score()\n```\n\n## Playbook Performance Metrics\n\n| Metric | Before SOAR | After SOAR | Improvement |\n|---|---|---|---|\n| Phishing MTTR | 45 min | 5 min | 89% reduction |\n| Malware MTTR | 60 min | 8 min | 87% reduction |\n| Account Compromise MTTR | 30 min | 4 min | 87% reduction |\n| Alerts Handled per Shift | 50 | 200+ | 300% increase |\n| False Positive Handling | 10 min | 30 sec | 95% reduction |\n\n## References\n\n- [Cortex XSOAR Playbooks Overview](https:\u002F\u002Fxsoar.pan.dev\u002Fdocs\u002Fplaybooks\u002Fplaybooks-overview)\n- [From Zero to Process to XSOAR Playbook](https:\u002F\u002Flive.paloaltonetworks.com\u002Ft5\u002Fcommunity-blogs\u002Ffrom-zero-to-process-to-xsoar-playbook\u002Fba-p\u002F564568)\n- [XSOAR Common Playbooks Pack](https:\u002F\u002Fwww.paloaltonetworks.com\u002Fblog\u002Fsecurity-operations\u002Fplaybook-of-the-week-xsoar-common-playbook\u002F)\n- [Cortex XSOAR Product Page](https:\u002F\u002Fwww.paloaltonetworks.com\u002Fcortex\u002Fcortex-xsoar)\n",{"name":5,"note":25,"tags":26,"author":35,"domain":36,"source":37,"license":15,"version":38,"nist_csf":39,"subdomain":44,"description":7,"mitre_attack":45,"source_commit":50},"Vendored verbatim from an external Apache-2.0 security-skill library, pinned by commit. Exceeds the internal 300-line skill guideline (agent-code-constraints.md) -- kept as-is because this is vendored reference material (forensics\u002Fthreat-intel procedure), not Yana AI-authored content, and trimming would damage technical accuracy.",[27,28,29,30,31,32,33,34],"xsoar","soar","palo-alto","playbook","automation","incident-response","orchestration","cortex","mahipal","cybersecurity","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","1.0",[40,41,42,43],"DE.CM-01","DE.AE-02","RS.MA-01","DE.AE-06","soc-operations",[46,47,48,49],"T1078","T1685.002","T1685.005","T1566","04450304b12645cb2b974ab96d28c0664758a88d","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa",".claude\u002Fskills\u002Fimplementing-soar-playbook-with-palo-alto-xsoar",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill implementing-soar-playbook-with-palo-alto-xsoar",{"tool":67,"command":68},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill implementing-soar-playbook-with-palo-alto-xsoar",{"tool":70,"command":71},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill implementing-soar-playbook-with-palo-alto-xsoar","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-soar-playbook-with-palo-alto-xsoar\u002FSKILL.md",true,[75,81,85,91,95,99,105],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"assets\u002Ftemplate.md","ASSET","资产文件",1408,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-soar-playbook-with-palo-alto-xsoar\u002Fassets\u002Ftemplate.md",{"path":82,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fapi-reference.md","REFERENCE","参考文档",4203,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-soar-playbook-with-palo-alto-xsoar\u002Freferences\u002Fapi-reference.md",{"path":92,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fstandards.md",1761,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-soar-playbook-with-palo-alto-xsoar\u002Freferences\u002Fstandards.md",{"path":96,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fworkflows.md",2043,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-soar-playbook-with-palo-alto-xsoar\u002Freferences\u002Fworkflows.md",{"path":100,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":103,"sourceHtmlUrl":104},"scripts\u002Fagent.py","SCRIPT","脚本",7525,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-soar-playbook-with-palo-alto-xsoar\u002Fscripts\u002Fagent.py",{"path":106,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":107,"sourceHtmlUrl":108},"scripts\u002Fprocess.py",10081,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-soar-playbook-with-palo-alto-xsoar\u002Fscripts\u002Fprocess.py",[110,118,125,133,141,149],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":114,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":20},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":20},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\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},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\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":15,"licenseFileUrl":137,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":20},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":145,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":20},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":150,"name":151,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":20},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]