[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B868XAR1MZ3JQP8SW51YFV":3,"skill-same:01M7B868XAR1MZ3JQP8SW51YFV":107},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":13,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":58,"install":59,"resources":72},"01M7B868XAR1MZ3JQP8SW51YFV","performing-alert-triage-with-elastic-siem",null,"Perform systematic alert triage in Elastic Security SIEM—classifying, prioritizing, and investigating alerts using Kibana, ES|QL queries, and ECS-normalized data—to drive SOC analyst workflows. Use when triaging incoming Elastic Security detections, prioritizing an analyst's alert queue, or investigating alerts during SOC operations.","vikasvardhanv\u002Fjerry_skills","vikasvardhanv","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99010657?v=4","01M7B2B0VN78W7529RQX5BR6DZ","01M7B2B0WDNTXJHRK3QNPNWRP6",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-alert-triage-with-elastic-siem\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-alert-triage-with-elastic-siem\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: performing-alert-triage-with-elastic-siem\ndescription: Perform systematic alert triage in Elastic Security SIEM—classifying,\n  prioritizing, and investigating alerts using Kibana, ES|QL queries, and ECS-normalized\n  data—to drive SOC analyst workflows. Use when triaging incoming Elastic Security\n  detections, prioritizing an analyst's alert queue, or investigating alerts during\n  SOC operations.\ndomain: cybersecurity\nsubdomain: soc-operations\ntags:\n- elastic\n- siem\n- alert-triage\n- soc\n- elastic-security\n- detection\n- esql\n- kibana\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nd3fend_techniques:\n- Token Binding\n- Restore Access\n- Application Protocol Command Analysis\n- Password Authentication\n- Reissue Credential\nnist_csf:\n- DE.CM-01\n- DE.AE-02\n- RS.MA-01\n- DE.AE-06\nmitre_attack:\n- T1078\n- T1685.002\n- T1685.005\n- T1566\n---\n\n# Performing Alert Triage with Elastic SIEM\n\n## Overview\n\nAlert triage in Elastic Security is the systematic process of reviewing, classifying, and prioritizing security alerts to determine which represent genuine threats. Elastic's AI-driven Attack Discovery feature can triage hundreds of alerts down to discrete attack chains, but skilled analyst triage remains essential. A structured triage workflow typically takes 5-10 minutes per alert cluster using Elastic's built-in tools.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing alert triage with elastic siem\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- Elastic Security deployed (version 8.x or later)\n- Elastic Agent or Beats configured for endpoint and network data collection\n- Detection rules enabled and generating alerts\n- Elastic Common Schema (ECS) compliance across data sources\n- Analyst access to Kibana Security app with appropriate privileges\n\n## Alert Triage Workflow\n\n### Step 1: Initial Alert Assessment (2 minutes)\n\nWhen viewing an alert in Elastic Security, review the alert details panel:\n\n```\nAlert Details Panel:\n- Rule Name and Description\n- Severity and Risk Score\n- MITRE ATT&CK Mapping\n- Host and User Context\n- Process Tree (for endpoint alerts)\n- Timeline of related events\n```\n\n#### Key Fields to Examine First\n\n| Field | Purpose | ECS Field |\n|---|---|---|\n| Rule severity | Initial priority assessment | `kibana.alert.severity` |\n| Risk score | Quantified threat level | `kibana.alert.risk_score` |\n| Host name | Affected system | `host.name` |\n| User name | Affected identity | `user.name` |\n| Process name | Executing process | `process.name` |\n| Source IP | Origin of activity | `source.ip` |\n| Destination IP | Target of activity | `destination.ip` |\n| MITRE tactic | Attack stage | `threat.tactic.name` |\n\n### Step 2: Context Gathering (3 minutes)\n\n#### Query Related Events with ES|QL\n\n```esql\nFROM logs-endpoint.events.*\n| WHERE host.name == \"affected-host\" AND @timestamp > NOW() - 1 HOUR\n| STATS count = COUNT(*) BY event.category, event.action\n| SORT count DESC\n```\n\n#### Find All Activity from Suspicious User\n\n```esql\nFROM logs-*\n| WHERE user.name == \"suspicious-user\" AND @timestamp > NOW() - 24 HOURS\n| STATS count = COUNT(*), unique_hosts = COUNT_DISTINCT(host.name) BY event.category\n| SORT count DESC\n```\n\n#### Check for Related Alerts from Same Source\n\n```esql\nFROM .alerts-security.alerts-default\n| WHERE source.ip == \"10.0.0.50\" AND @timestamp > NOW() - 24 HOURS\n| STATS alert_count = COUNT(*) BY kibana.alert.rule.name, kibana.alert.severity\n| SORT alert_count DESC\n```\n\n#### Investigate Lateral Movement from Same IP\n\n```esql\nFROM logs-system.auth-*\n| WHERE source.ip == \"10.0.0.50\" AND event.outcome == \"success\"\n| STATS login_count = COUNT(*), hosts = COUNT_DISTINCT(host.name) BY user.name\n| WHERE hosts > 3\n```\n\n### Step 3: Threat Intelligence Enrichment (2 minutes)\n\nCheck indicators against threat intelligence:\n\n```esql\nFROM logs-ti_*\n| WHERE threat.indicator.ip == \"203.0.113.50\"\n| KEEP threat.indicator.type, threat.indicator.provider, threat.indicator.confidence, threat.feed.name\n```\n\n#### Check File Hash Against Known Threats\n\n```esql\nFROM logs-endpoint.events.file-*\n| WHERE file.hash.sha256 == \"abc123...\"\n| STATS occurrences = COUNT(*) BY host.name, file.path, user.name\n```\n\n### Step 4: Classification Decision (2 minutes)\n\n| Classification | Criteria | Action |\n|---|---|---|\n| True Positive | Confirmed malicious activity | Escalate to incident, begin containment |\n| Benign True Positive | Expected behavior matching rule | Document in alert notes, acknowledge |\n| False Positive | Rule triggered on benign activity | Mark as false positive, create tuning task |\n| Needs Investigation | Insufficient data for determination | Assign for deeper investigation |\n\n### Step 5: Documentation and Escalation (1 minute)\n\nFor each triaged alert, document:\n- Classification decision with rationale\n- Evidence artifacts examined\n- Related alerts or investigations\n- Recommended next steps\n\n## Detection Rules for Triage\n\n### Pre-Built Detection Rules\n\nElastic Security includes 1000+ pre-built detection rules organized by:\n- **MITRE ATT&CK Tactic**: Initial Access, Execution, Persistence, etc.\n- **Platform**: Windows, Linux, macOS, Cloud\n- **Data Source**: Endpoint, Network, Cloud, Identity\n\n### Custom Alert Correlation Rule\n\n```json\n{\n  \"name\": \"Multiple Failed Logins Followed by Success\",\n  \"type\": \"threshold\",\n  \"query\": \"event.category:authentication AND event.outcome:failure\",\n  \"threshold\": {\n    \"field\": [\"source.ip\", \"user.name\"],\n    \"value\": 5,\n    \"cardinality\": [\n      {\n        \"field\": \"user.name\",\n        \"value\": 3\n      }\n    ]\n  },\n  \"severity\": \"high\",\n  \"risk_score\": 73,\n  \"threat\": [\n    {\n      \"framework\": \"MITRE ATT&CK\",\n      \"tactic\": {\n        \"id\": \"TA0006\",\n        \"name\": \"Credential Access\"\n      },\n      \"technique\": [\n        {\n          \"id\": \"T1110\",\n          \"name\": \"Brute Force\"\n        }\n      ]\n    }\n  ]\n}\n```\n\n## AI-Assisted Triage\n\n### Elastic AI Assistant Integration\n\n1. Open alert in Elastic Security\n2. Click AI Assistant panel\n3. Use quick prompts:\n   - \"Summarize this alert\" - Get initial assessment\n   - \"Generate ES|QL query to find related activity\" - Expand investigation\n   - \"What are the recommended response actions?\" - Get playbook guidance\n   - \"Is this likely a false positive?\" - Get AI confidence assessment\n\n### Attack Discovery\n\nElastic's Attack Discovery automatically:\n- Groups related alerts into attack chains\n- Maps alerts to MITRE ATT&CK kill chain stages\n- Filters false positives using ML models\n- Prioritizes based on business impact\n- Provides narrative summary of the attack\n\n## Triage Prioritization Matrix\n\n| Risk Score | Severity | Asset Criticality | Response SLA |\n|---|---|---|---|\n| 90-100 | Critical | High | 15 minutes |\n| 70-89 | High | High | 30 minutes |\n| 70-89 | High | Medium | 1 hour |\n| 50-69 | Medium | Any | 4 hours |\n| 21-49 | Low | Any | 8 hours |\n| 1-20 | Informational | Any | 24 hours |\n\n## Triage Metrics and KPIs\n\n| Metric | Target | Measurement |\n|---|---|---|\n| Mean Time to Triage (MTTT) | \u003C 10 minutes | Time from alert creation to classification |\n| False Positive Rate | \u003C 30% | False positives \u002F total alerts |\n| Escalation Rate | 10-20% | Escalated alerts \u002F total alerts |\n| Alert Coverage | > 80% | Triaged alerts \u002F generated alerts per shift |\n| Reclassification Rate | \u003C 5% | Changed classifications \u002F total classified |\n\n## References\n\n- [Elastic Security - Triage Alerts Documentation](https:\u002F\u002Fwww.elastic.co\u002Fdocs\u002Fsolutions\u002Fsecurity\u002Fai\u002Ftriage-alerts)\n- [SOC Analyst's Guide to Triage with Elastic](https:\u002F\u002Fsystemweakness.com\u002Ffrom-alert-to-action-a-soc-analysts-guide-to-triage-with-elastic-%EF%B8%8F-4e5354ab5da9)\n- [Elastic Blog - AI and 2025 SIEM Landscape](https:\u002F\u002Fwww.elastic.co\u002Fblog\u002Fai-siem-landscape)\n- [Reducing False Positives with Elastic and Tines](https:\u002F\u002Fwww.elastic.co\u002Fblog\u002Ffalse-positives-automated-siem-investigations-elastic-tines)\n","# Performing Alert Triage with Elastic SIEM\n\n## Overview\n\nAlert triage in Elastic Security is the systematic process of reviewing, classifying, and prioritizing security alerts to determine which represent genuine threats. Elastic's AI-driven Attack Discovery feature can triage hundreds of alerts down to discrete attack chains, but skilled analyst triage remains essential. A structured triage workflow typically takes 5-10 minutes per alert cluster using Elastic's built-in tools.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing alert triage with elastic siem\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- Elastic Security deployed (version 8.x or later)\n- Elastic Agent or Beats configured for endpoint and network data collection\n- Detection rules enabled and generating alerts\n- Elastic Common Schema (ECS) compliance across data sources\n- Analyst access to Kibana Security app with appropriate privileges\n\n## Alert Triage Workflow\n\n### Step 1: Initial Alert Assessment (2 minutes)\n\nWhen viewing an alert in Elastic Security, review the alert details panel:\n\n```\nAlert Details Panel:\n- Rule Name and Description\n- Severity and Risk Score\n- MITRE ATT&CK Mapping\n- Host and User Context\n- Process Tree (for endpoint alerts)\n- Timeline of related events\n```\n\n#### Key Fields to Examine First\n\n| Field | Purpose | ECS Field |\n|---|---|---|\n| Rule severity | Initial priority assessment | `kibana.alert.severity` |\n| Risk score | Quantified threat level | `kibana.alert.risk_score` |\n| Host name | Affected system | `host.name` |\n| User name | Affected identity | `user.name` |\n| Process name | Executing process | `process.name` |\n| Source IP | Origin of activity | `source.ip` |\n| Destination IP | Target of activity | `destination.ip` |\n| MITRE tactic | Attack stage | `threat.tactic.name` |\n\n### Step 2: Context Gathering (3 minutes)\n\n#### Query Related Events with ES|QL\n\n```esql\nFROM logs-endpoint.events.*\n| WHERE host.name == \"affected-host\" AND @timestamp > NOW() - 1 HOUR\n| STATS count = COUNT(*) BY event.category, event.action\n| SORT count DESC\n```\n\n#### Find All Activity from Suspicious User\n\n```esql\nFROM logs-*\n| WHERE user.name == \"suspicious-user\" AND @timestamp > NOW() - 24 HOURS\n| STATS count = COUNT(*), unique_hosts = COUNT_DISTINCT(host.name) BY event.category\n| SORT count DESC\n```\n\n#### Check for Related Alerts from Same Source\n\n```esql\nFROM .alerts-security.alerts-default\n| WHERE source.ip == \"10.0.0.50\" AND @timestamp > NOW() - 24 HOURS\n| STATS alert_count = COUNT(*) BY kibana.alert.rule.name, kibana.alert.severity\n| SORT alert_count DESC\n```\n\n#### Investigate Lateral Movement from Same IP\n\n```esql\nFROM logs-system.auth-*\n| WHERE source.ip == \"10.0.0.50\" AND event.outcome == \"success\"\n| STATS login_count = COUNT(*), hosts = COUNT_DISTINCT(host.name) BY user.name\n| WHERE hosts > 3\n```\n\n### Step 3: Threat Intelligence Enrichment (2 minutes)\n\nCheck indicators against threat intelligence:\n\n```esql\nFROM logs-ti_*\n| WHERE threat.indicator.ip == \"203.0.113.50\"\n| KEEP threat.indicator.type, threat.indicator.provider, threat.indicator.confidence, threat.feed.name\n```\n\n#### Check File Hash Against Known Threats\n\n```esql\nFROM logs-endpoint.events.file-*\n| WHERE file.hash.sha256 == \"abc123...\"\n| STATS occurrences = COUNT(*) BY host.name, file.path, user.name\n```\n\n### Step 4: Classification Decision (2 minutes)\n\n| Classification | Criteria | Action |\n|---|---|---|\n| True Positive | Confirmed malicious activity | Escalate to incident, begin containment |\n| Benign True Positive | Expected behavior matching rule | Document in alert notes, acknowledge |\n| False Positive | Rule triggered on benign activity | Mark as false positive, create tuning task |\n| Needs Investigation | Insufficient data for determination | Assign for deeper investigation |\n\n### Step 5: Documentation and Escalation (1 minute)\n\nFor each triaged alert, document:\n- Classification decision with rationale\n- Evidence artifacts examined\n- Related alerts or investigations\n- Recommended next steps\n\n## Detection Rules for Triage\n\n### Pre-Built Detection Rules\n\nElastic Security includes 1000+ pre-built detection rules organized by:\n- **MITRE ATT&CK Tactic**: Initial Access, Execution, Persistence, etc.\n- **Platform**: Windows, Linux, macOS, Cloud\n- **Data Source**: Endpoint, Network, Cloud, Identity\n\n### Custom Alert Correlation Rule\n\n```json\n{\n  \"name\": \"Multiple Failed Logins Followed by Success\",\n  \"type\": \"threshold\",\n  \"query\": \"event.category:authentication AND event.outcome:failure\",\n  \"threshold\": {\n    \"field\": [\"source.ip\", \"user.name\"],\n    \"value\": 5,\n    \"cardinality\": [\n      {\n        \"field\": \"user.name\",\n        \"value\": 3\n      }\n    ]\n  },\n  \"severity\": \"high\",\n  \"risk_score\": 73,\n  \"threat\": [\n    {\n      \"framework\": \"MITRE ATT&CK\",\n      \"tactic\": {\n        \"id\": \"TA0006\",\n        \"name\": \"Credential Access\"\n      },\n      \"technique\": [\n        {\n          \"id\": \"T1110\",\n          \"name\": \"Brute Force\"\n        }\n      ]\n    }\n  ]\n}\n```\n\n## AI-Assisted Triage\n\n### Elastic AI Assistant Integration\n\n1. Open alert in Elastic Security\n2. Click AI Assistant panel\n3. Use quick prompts:\n   - \"Summarize this alert\" - Get initial assessment\n   - \"Generate ES|QL query to find related activity\" - Expand investigation\n   - \"What are the recommended response actions?\" - Get playbook guidance\n   - \"Is this likely a false positive?\" - Get AI confidence assessment\n\n### Attack Discovery\n\nElastic's Attack Discovery automatically:\n- Groups related alerts into attack chains\n- Maps alerts to MITRE ATT&CK kill chain stages\n- Filters false positives using ML models\n- Prioritizes based on business impact\n- Provides narrative summary of the attack\n\n## Triage Prioritization Matrix\n\n| Risk Score | Severity | Asset Criticality | Response SLA |\n|---|---|---|---|\n| 90-100 | Critical | High | 15 minutes |\n| 70-89 | High | High | 30 minutes |\n| 70-89 | High | Medium | 1 hour |\n| 50-69 | Medium | Any | 4 hours |\n| 21-49 | Low | Any | 8 hours |\n| 1-20 | Informational | Any | 24 hours |\n\n## Triage Metrics and KPIs\n\n| Metric | Target | Measurement |\n|---|---|---|\n| Mean Time to Triage (MTTT) | \u003C 10 minutes | Time from alert creation to classification |\n| False Positive Rate | \u003C 30% | False positives \u002F total alerts |\n| Escalation Rate | 10-20% | Escalated alerts \u002F total alerts |\n| Alert Coverage | > 80% | Triaged alerts \u002F generated alerts per shift |\n| Reclassification Rate | \u003C 5% | Changed classifications \u002F total classified |\n\n## References\n\n- [Elastic Security - Triage Alerts Documentation](https:\u002F\u002Fwww.elastic.co\u002Fdocs\u002Fsolutions\u002Fsecurity\u002Fai\u002Ftriage-alerts)\n- [SOC Analyst's Guide to Triage with Elastic](https:\u002F\u002Fsystemweakness.com\u002Ffrom-alert-to-action-a-soc-analysts-guide-to-triage-with-elastic-%EF%B8%8F-4e5354ab5da9)\n- [Elastic Blog - AI and 2025 SIEM Landscape](https:\u002F\u002Fwww.elastic.co\u002Fblog\u002Fai-siem-landscape)\n- [Reducing False Positives with Elastic and Tines](https:\u002F\u002Fwww.elastic.co\u002Fblog\u002Ffalse-positives-automated-siem-investigations-elastic-tines)\n",{"name":5,"tags":24,"author":33,"domain":34,"license":14,"version":35,"nist_csf":36,"subdomain":41,"description":7,"mitre_attack":42,"d3fend_techniques":47},[25,26,27,28,29,30,31,32],"elastic","siem","alert-triage","soc","elastic-security","detection","esql","kibana","mahipal","cybersecurity","1.0",[37,38,39,40],"DE.CM-01","DE.AE-02","RS.MA-01","DE.AE-06","soc-operations",[43,44,45,46],"T1078","T1685.002","T1685.005","T1566",[48,49,50,51,52],"Token Binding","Restore Access","Application Protocol Command Analysis","Password Authentication","Reissue Credential","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-alert-triage-with-elastic-siem","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv","2026-08-25 13:16:33",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add vikasvardhanv\u002Fjerry_skills --skill performing-alert-triage-with-elastic-siem",{"tool":65,"command":66},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill performing-alert-triage-with-elastic-siem",{"tool":68,"command":69},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill performing-alert-triage-with-elastic-siem","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-alert-triage-with-elastic-siem\u002FSKILL.md",true,[73,79,83,89,93,97,103],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"assets\u002Ftemplate.md","ASSET","资产文件",1203,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-alert-triage-with-elastic-siem\u002Fassets\u002Ftemplate.md",{"path":80,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":15},"LICENSE","许可证",11255,{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fapi-reference.md","REFERENCE","参考文档",2847,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-alert-triage-with-elastic-siem\u002Freferences\u002Fapi-reference.md",{"path":90,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fstandards.md",1699,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-alert-triage-with-elastic-siem\u002Freferences\u002Fstandards.md",{"path":94,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fworkflows.md",1618,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-alert-triage-with-elastic-siem\u002Freferences\u002Fworkflows.md",{"path":98,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":101,"sourceHtmlUrl":102},"scripts\u002Fagent.py","SCRIPT","脚本",6797,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-alert-triage-with-elastic-siem\u002Fscripts\u002Fagent.py",{"path":104,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":105,"sourceHtmlUrl":106},"scripts\u002Fprocess.py",11465,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-alert-triage-with-elastic-siem\u002Fscripts\u002Fprocess.py",[108,116,123,130,137,144],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":112,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":19},"01M7BESR1CJ3H5SP9XM8KYJZ9W","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","MIT","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":112,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":19},"01M7BES1YA6R97W7QPMFFM1PED","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":112,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":19},"01M7BERNHYGY035AR00VRT03KE","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":112,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":19},"01M7BERCK1EAKTWW7R436WAR0J","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":112,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":19},"01M7BEQZAZAQRTXFJRY7RHV3TY","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":112,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":19},"01M7BEQKJ45K31QK5VRAQSVJCJ","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]