[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B5F454FFZ2SFMDYPYX4RTQ":3,"skill-same:01M7B5F454FFZ2SFMDYPYX4RTQ":87},{"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":51,"commitSha":52,"skillDirectory":53,"forksCount":13,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M7B5F454FFZ2SFMDYPYX4RTQ","conducting-malware-incident-response",null,"Respond to malware infections across enterprise endpoints by identifying the malware family, determining infection vectors, assessing spread, and executing containment, analysis, eradication, and recovery procedures aligned to MITRE ATT&CK. Use when responding to a confirmed or suspected malware infection, including trojan\u002Fworm\u002Fransomware outbreaks, malware triage, or infected endpoint remediation.","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\u002Fconducting-malware-incident-response\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fconducting-malware-incident-response\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: conducting-malware-incident-response\ndescription: Respond to malware infections across enterprise endpoints by identifying the malware family, determining infection vectors, assessing spread, and executing containment, analysis, eradication, and recovery procedures aligned to MITRE ATT&CK. Use when responding to a confirmed or suspected malware infection, including trojan\u002Fworm\u002Fransomware outbreaks, malware triage, or infected endpoint remediation.\ndomain: cybersecurity\nsubdomain: incident-response\ntags:\n- malware-response\n- malware-analysis\n- eradication\n- endpoint-remediation\n- MITRE-ATT&CK\nmitre_attack:\n- T1204\n- T1027\n- T1055\n- T1059\n- T1486\nversion: 1.0.0\nauthor: mahipal\nlicense: Apache-2.0\nd3fend_techniques:\n- File Metadata Consistency Validation\n- Application Protocol Command Analysis\n- Identifier Analysis\n- Content Format Conversion\n- Message Analysis\nnist_csf:\n- RS.MA-01\n- RS.MA-02\n- RS.AN-03\n- RC.RP-01\n---\n\n# Conducting Malware Incident Response\n\n## When to Use\n\n- EDR or antivirus detects malware execution on one or more endpoints\n- A user reports suspicious system behavior indicative of malware infection\n- Threat intelligence indicates a malware campaign targeting the organization's industry\n- Network monitoring detects beaconing traffic consistent with known malware C2 patterns\n- A file detonation in a sandbox returns a malicious verdict\n\n**Do not use** for analyzing malware samples in a research context; use dedicated malware analysis procedures for reverse engineering.\n\n## Prerequisites\n\n- EDR platform with process tree visibility and host isolation capability\n- Malware sandbox environment (Cuckoo, ANY.RUN, Joe Sandbox, Hybrid Analysis)\n- Access to threat intelligence platforms for malware family identification (VirusTotal, MalwareBazaar)\n- Forensic imaging tools for evidence preservation (FTK Imager, KAPE)\n- Clean system images or gold images for endpoint rebuild\n- MITRE ATT&CK framework reference for technique mapping\n\n## Workflow\n\n### Step 1: Detect and Confirm Malware Presence\n\nValidate the malware alert and gather initial indicators:\n\n- Review EDR alert details: detection name, file path, hash (SHA-256), process tree\n- Check if the detection is a known malware family or generic heuristic detection\n- Query the file hash against VirusTotal, MalwareBazaar, and internal threat intelligence\n- Examine the process execution chain to determine how the malware was delivered\n\n```\nDetection Summary:\nFile:        C:\\Users\\jsmith\\AppData\\Local\\Temp\\update.exe\nSHA-256:     a1b2c3d4e5f6...\nDetection:   CrowdStrike: Malware\u002FQakbot | VirusTotal: 58\u002F72 engines\nParent:      WINWORD.EXE → cmd.exe → powershell.exe → update.exe\nDelivery:    Email attachment (Invoice-Nov2025.docm)\nNetwork:     HTTPS POST to 185.220.101[.]42:443 every 60s\nPersistence: Scheduled Task \"WindowsUpdate\" → update.exe\n```\n\n### Step 2: Scope the Infection\n\nDetermine how many systems are affected and the malware's propagation method:\n\n- Use EDR to search for the malware hash, filename, and behavioral indicators across all endpoints\n- Check for network-based spreading (SMB, WMI, PsExec, exploitation)\n- Query email gateway logs for all recipients of the delivery email\n- Search for C2 communications to the identified infrastructure from other internal hosts\n- Check for persistence mechanisms on all identified infected hosts\n\n### Step 3: Contain Infected Systems\n\nExecute containment per the active breach containment procedures:\n\n- Network-isolate infected endpoints via EDR containment\n- Block malware C2 infrastructure at firewall and DNS\n- Block the malware hash in EDR prevention policy organization-wide\n- Quarantine the delivery email from all mailboxes (if email-delivered)\n- Disable compromised user accounts if credential theft is suspected\n\n### Step 4: Analyze the Malware\n\nPerform sufficient analysis to support complete eradication:\n\n- Submit the sample to a sandbox for dynamic analysis (behavioral report, dropped files, network IOCs)\n- Identify all persistence mechanisms: registry keys, scheduled tasks, services, WMI subscriptions, startup folders\n- Document all file system artifacts: dropped files, modified files, created directories\n- Extract network IOCs: C2 domains, IPs, URLs, user agents, JA3\u002FJA3S hashes\n- Map observed behaviors to MITRE ATT&CK techniques\n\n```\nMalware Analysis Summary - Qakbot Variant\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nInitial Access:   T1566.001 - Spearphishing Attachment (.docm)\nExecution:        T1059.001 - PowerShell (encoded downloader)\nPersistence:      T1053.005 - Scheduled Task\nDefense Evasion:  T1055.012 - Process Hollowing (explorer.exe)\nC2:               T1071.001 - HTTPS with custom headers\nCollection:       T1005 - Data from Local System (browser credentials)\nExfiltration:     T1041 - Exfiltration Over C2 Channel\n\nArtifacts:\n- C:\\Users\\*\\AppData\\Local\\Temp\\update.exe (dropper)\n- C:\\ProgramData\\Microsoft\\{GUID}\\config.dll (payload)\n- HKCU\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\{random} (backup persistence)\n- Scheduled Task: \"WindowsUpdate\" (primary persistence)\n```\n\n### Step 5: Eradicate the Malware\n\nRemove all malware artifacts from every infected system:\n\n- Terminate malicious processes and injected threads\n- Delete malware files from all identified paths\n- Remove persistence mechanisms (scheduled tasks, registry keys, services, WMI subscriptions)\n- Clear browser credential stores if credential harvesting was confirmed\n- Run a full EDR scan to verify no artifacts remain\n- If eradication confidence is low, reimage the system from a known-clean gold image\n\n### Step 6: Recover and Validate\n\nRestore systems to production and verify clean status:\n\n- Reconnect contained systems to the network in stages\n- Monitor for 72 hours for any recurrence of malware indicators\n- Force password resets for all users on infected endpoints\n- Verify that C2 traffic has completely ceased across the environment\n- Update detection rules based on newly discovered IOCs from the investigation\n- Distribute IOCs to threat intelligence sharing partners (ISAC, MISP)\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| **Malware Family** | Classification of malware variants sharing code, infrastructure, or behavior patterns (e.g., Qakbot, Emotet, Cobalt Strike) |\n| **Process Hollowing** | Technique where malware creates a legitimate process in a suspended state, replaces its memory with malicious code, then resumes execution |\n| **Beacon** | Periodic network communication from malware to its C2 server, typically with a set interval and jitter for detection evasion |\n| **Dropper** | Initial malware component that downloads or unpacks the primary payload; often delivered via phishing |\n| **Persistence Mechanism** | Method used by malware to survive system reboots (registry run keys, scheduled tasks, services, WMI event subscriptions) |\n| **IOC (Indicator of Compromise)** | Observable artifact such as file hash, IP address, domain, or registry key that indicates malware presence |\n\n## Tools & Systems\n\n- **CrowdStrike Falcon \u002F Microsoft Defender for Endpoint**: EDR platforms for detection, containment, and threat hunting\n- **ANY.RUN \u002F Joe Sandbox**: Interactive malware sandboxes for dynamic behavioral analysis\n- **VirusTotal \u002F MalwareBazaar**: Malware intelligence platforms for sample identification and IOC enrichment\n- **KAPE (Kroll Artifact Parser and Extractor)**: Forensic triage tool for rapid artifact collection from infected endpoints\n- **YARA**: Pattern-matching engine for creating custom malware detection rules based on observed indicators\n\n## Common Scenarios\n\n### Scenario: Emotet Loader Leading to Cobalt Strike Deployment\n\n**Context**: EDR detects a macro-enabled document that spawns PowerShell, downloads an Emotet DLL, which subsequently loads a Cobalt Strike beacon. Three hosts are infected within 45 minutes.\n\n**Approach**:\n1. Immediately isolate all three hosts and block C2 IPs at the perimeter\n2. Search email gateway for all recipients of the original phishing email and quarantine it\n3. Sweep all endpoints for the Emotet DLL hash and Cobalt Strike beacon indicators\n4. Analyze the Cobalt Strike beacon configuration to extract watermark, C2 profile, and staging URLs\n5. Check for credential harvesting (Mimikatz\u002FLSASS dump) and lateral movement artifacts\n6. Eradicate all malware artifacts and reset credentials for affected users\n\n**Pitfalls**:\n- Focusing only on Emotet and missing the Cobalt Strike second-stage payload\n- Failing to extract and block the Cobalt Strike Malleable C2 profile indicators\n- Not checking for additional persistence beyond the initial detection (Emotet often installs multiple backup persistence mechanisms)\n\n## Output Format\n\n```\nMALWARE INCIDENT RESPONSE REPORT\n=================================\nIncident:         INC-2025-1547\nMalware Family:   Qakbot (variant: Obama265)\nDelivery Vector:  Spearphishing attachment (Invoice-Nov2025.docm)\nFirst Detection:  2025-11-15T14:23:17Z\nScope:            4 endpoints confirmed infected\n\nINFECTION TIMELINE\n14:18 UTC - Phishing email received by jsmith@corp.example.com\n14:19 UTC - Macro executed in WINWORD.EXE\n14:20 UTC - PowerShell downloads update.exe from staging server\n14:21 UTC - update.exe establishes persistence (Scheduled Task)\n14:23 UTC - C2 beacon initiated to 185.220.101[.]42\n14:35 UTC - Lateral spread to WKSTN-087 via stolen credentials\n14:42 UTC - EDR detection fires, SOC alerted\n\nIOCs EXTRACTED\nFile Hashes:  [SHA-256 list]\nC2 Domains:   [domain list]\nC2 IPs:       [IP list]\nFile Paths:   [artifact paths]\n\nERADICATION STATUS\n[x] All malware artifacts removed from 4 hosts\n[x] Persistence mechanisms deleted\n[x] C2 infrastructure blocked\n[x] Compromised credentials reset\n[x] Email quarantined from all mailboxes\n\nRECOMMENDATIONS\n1. Deploy YARA rule for Qakbot variant detection\n2. Block macro execution in documents from external senders\n3. Implement application whitelisting on finance workstations\n```\n","# Conducting Malware Incident Response\n\n## When to Use\n\n- EDR or antivirus detects malware execution on one or more endpoints\n- A user reports suspicious system behavior indicative of malware infection\n- Threat intelligence indicates a malware campaign targeting the organization's industry\n- Network monitoring detects beaconing traffic consistent with known malware C2 patterns\n- A file detonation in a sandbox returns a malicious verdict\n\n**Do not use** for analyzing malware samples in a research context; use dedicated malware analysis procedures for reverse engineering.\n\n## Prerequisites\n\n- EDR platform with process tree visibility and host isolation capability\n- Malware sandbox environment (Cuckoo, ANY.RUN, Joe Sandbox, Hybrid Analysis)\n- Access to threat intelligence platforms for malware family identification (VirusTotal, MalwareBazaar)\n- Forensic imaging tools for evidence preservation (FTK Imager, KAPE)\n- Clean system images or gold images for endpoint rebuild\n- MITRE ATT&CK framework reference for technique mapping\n\n## Workflow\n\n### Step 1: Detect and Confirm Malware Presence\n\nValidate the malware alert and gather initial indicators:\n\n- Review EDR alert details: detection name, file path, hash (SHA-256), process tree\n- Check if the detection is a known malware family or generic heuristic detection\n- Query the file hash against VirusTotal, MalwareBazaar, and internal threat intelligence\n- Examine the process execution chain to determine how the malware was delivered\n\n```\nDetection Summary:\nFile:        C:\\Users\\jsmith\\AppData\\Local\\Temp\\update.exe\nSHA-256:     a1b2c3d4e5f6...\nDetection:   CrowdStrike: Malware\u002FQakbot | VirusTotal: 58\u002F72 engines\nParent:      WINWORD.EXE → cmd.exe → powershell.exe → update.exe\nDelivery:    Email attachment (Invoice-Nov2025.docm)\nNetwork:     HTTPS POST to 185.220.101[.]42:443 every 60s\nPersistence: Scheduled Task \"WindowsUpdate\" → update.exe\n```\n\n### Step 2: Scope the Infection\n\nDetermine how many systems are affected and the malware's propagation method:\n\n- Use EDR to search for the malware hash, filename, and behavioral indicators across all endpoints\n- Check for network-based spreading (SMB, WMI, PsExec, exploitation)\n- Query email gateway logs for all recipients of the delivery email\n- Search for C2 communications to the identified infrastructure from other internal hosts\n- Check for persistence mechanisms on all identified infected hosts\n\n### Step 3: Contain Infected Systems\n\nExecute containment per the active breach containment procedures:\n\n- Network-isolate infected endpoints via EDR containment\n- Block malware C2 infrastructure at firewall and DNS\n- Block the malware hash in EDR prevention policy organization-wide\n- Quarantine the delivery email from all mailboxes (if email-delivered)\n- Disable compromised user accounts if credential theft is suspected\n\n### Step 4: Analyze the Malware\n\nPerform sufficient analysis to support complete eradication:\n\n- Submit the sample to a sandbox for dynamic analysis (behavioral report, dropped files, network IOCs)\n- Identify all persistence mechanisms: registry keys, scheduled tasks, services, WMI subscriptions, startup folders\n- Document all file system artifacts: dropped files, modified files, created directories\n- Extract network IOCs: C2 domains, IPs, URLs, user agents, JA3\u002FJA3S hashes\n- Map observed behaviors to MITRE ATT&CK techniques\n\n```\nMalware Analysis Summary - Qakbot Variant\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nInitial Access:   T1566.001 - Spearphishing Attachment (.docm)\nExecution:        T1059.001 - PowerShell (encoded downloader)\nPersistence:      T1053.005 - Scheduled Task\nDefense Evasion:  T1055.012 - Process Hollowing (explorer.exe)\nC2:               T1071.001 - HTTPS with custom headers\nCollection:       T1005 - Data from Local System (browser credentials)\nExfiltration:     T1041 - Exfiltration Over C2 Channel\n\nArtifacts:\n- C:\\Users\\*\\AppData\\Local\\Temp\\update.exe (dropper)\n- C:\\ProgramData\\Microsoft\\{GUID}\\config.dll (payload)\n- HKCU\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\\{random} (backup persistence)\n- Scheduled Task: \"WindowsUpdate\" (primary persistence)\n```\n\n### Step 5: Eradicate the Malware\n\nRemove all malware artifacts from every infected system:\n\n- Terminate malicious processes and injected threads\n- Delete malware files from all identified paths\n- Remove persistence mechanisms (scheduled tasks, registry keys, services, WMI subscriptions)\n- Clear browser credential stores if credential harvesting was confirmed\n- Run a full EDR scan to verify no artifacts remain\n- If eradication confidence is low, reimage the system from a known-clean gold image\n\n### Step 6: Recover and Validate\n\nRestore systems to production and verify clean status:\n\n- Reconnect contained systems to the network in stages\n- Monitor for 72 hours for any recurrence of malware indicators\n- Force password resets for all users on infected endpoints\n- Verify that C2 traffic has completely ceased across the environment\n- Update detection rules based on newly discovered IOCs from the investigation\n- Distribute IOCs to threat intelligence sharing partners (ISAC, MISP)\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| **Malware Family** | Classification of malware variants sharing code, infrastructure, or behavior patterns (e.g., Qakbot, Emotet, Cobalt Strike) |\n| **Process Hollowing** | Technique where malware creates a legitimate process in a suspended state, replaces its memory with malicious code, then resumes execution |\n| **Beacon** | Periodic network communication from malware to its C2 server, typically with a set interval and jitter for detection evasion |\n| **Dropper** | Initial malware component that downloads or unpacks the primary payload; often delivered via phishing |\n| **Persistence Mechanism** | Method used by malware to survive system reboots (registry run keys, scheduled tasks, services, WMI event subscriptions) |\n| **IOC (Indicator of Compromise)** | Observable artifact such as file hash, IP address, domain, or registry key that indicates malware presence |\n\n## Tools & Systems\n\n- **CrowdStrike Falcon \u002F Microsoft Defender for Endpoint**: EDR platforms for detection, containment, and threat hunting\n- **ANY.RUN \u002F Joe Sandbox**: Interactive malware sandboxes for dynamic behavioral analysis\n- **VirusTotal \u002F MalwareBazaar**: Malware intelligence platforms for sample identification and IOC enrichment\n- **KAPE (Kroll Artifact Parser and Extractor)**: Forensic triage tool for rapid artifact collection from infected endpoints\n- **YARA**: Pattern-matching engine for creating custom malware detection rules based on observed indicators\n\n## Common Scenarios\n\n### Scenario: Emotet Loader Leading to Cobalt Strike Deployment\n\n**Context**: EDR detects a macro-enabled document that spawns PowerShell, downloads an Emotet DLL, which subsequently loads a Cobalt Strike beacon. Three hosts are infected within 45 minutes.\n\n**Approach**:\n1. Immediately isolate all three hosts and block C2 IPs at the perimeter\n2. Search email gateway for all recipients of the original phishing email and quarantine it\n3. Sweep all endpoints for the Emotet DLL hash and Cobalt Strike beacon indicators\n4. Analyze the Cobalt Strike beacon configuration to extract watermark, C2 profile, and staging URLs\n5. Check for credential harvesting (Mimikatz\u002FLSASS dump) and lateral movement artifacts\n6. Eradicate all malware artifacts and reset credentials for affected users\n\n**Pitfalls**:\n- Focusing only on Emotet and missing the Cobalt Strike second-stage payload\n- Failing to extract and block the Cobalt Strike Malleable C2 profile indicators\n- Not checking for additional persistence beyond the initial detection (Emotet often installs multiple backup persistence mechanisms)\n\n## Output Format\n\n```\nMALWARE INCIDENT RESPONSE REPORT\n=================================\nIncident:         INC-2025-1547\nMalware Family:   Qakbot (variant: Obama265)\nDelivery Vector:  Spearphishing attachment (Invoice-Nov2025.docm)\nFirst Detection:  2025-11-15T14:23:17Z\nScope:            4 endpoints confirmed infected\n\nINFECTION TIMELINE\n14:18 UTC - Phishing email received by jsmith@corp.example.com\n14:19 UTC - Macro executed in WINWORD.EXE\n14:20 UTC - PowerShell downloads update.exe from staging server\n14:21 UTC - update.exe establishes persistence (Scheduled Task)\n14:23 UTC - C2 beacon initiated to 185.220.101[.]42\n14:35 UTC - Lateral spread to WKSTN-087 via stolen credentials\n14:42 UTC - EDR detection fires, SOC alerted\n\nIOCs EXTRACTED\nFile Hashes:  [SHA-256 list]\nC2 Domains:   [domain list]\nC2 IPs:       [IP list]\nFile Paths:   [artifact paths]\n\nERADICATION STATUS\n[x] All malware artifacts removed from 4 hosts\n[x] Persistence mechanisms deleted\n[x] C2 infrastructure blocked\n[x] Compromised credentials reset\n[x] Email quarantined from all mailboxes\n\nRECOMMENDATIONS\n1. Deploy YARA rule for Qakbot variant detection\n2. Block macro execution in documents from external senders\n3. Implement application whitelisting on finance workstations\n```\n",{"name":5,"tags":24,"author":30,"domain":31,"license":14,"version":32,"nist_csf":33,"subdomain":38,"description":7,"mitre_attack":39,"d3fend_techniques":45},[25,26,27,28,29],"malware-response","malware-analysis","eradication","endpoint-remediation","MITRE-ATT&CK","mahipal","cybersecurity","1.0.0",[34,35,36,37],"RS.MA-01","RS.MA-02","RS.AN-03","RC.RP-01","incident-response",[40,41,42,43,44],"T1204","T1027","T1055","T1059","T1486",[46,47,48,49,50],"File Metadata Consistency Validation","Application Protocol Command Analysis","Identifier Analysis","Content Format Conversion","Message Analysis","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fconducting-malware-incident-response","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv","2026-08-25 13:16:33",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add vikasvardhanv\u002Fjerry_skills --skill conducting-malware-incident-response",{"tool":63,"command":64},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill conducting-malware-incident-response",{"tool":66,"command":67},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill conducting-malware-incident-response","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fconducting-malware-incident-response\u002FSKILL.md",true,[71,75,81],{"path":72,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":15},"LICENSE","许可证",11255,{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fapi-reference.md","REFERENCE","参考文档",1763,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fconducting-malware-incident-response\u002Freferences\u002Fapi-reference.md",{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"scripts\u002Fagent.py","SCRIPT","脚本",7313,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fconducting-malware-incident-response\u002Fscripts\u002Fagent.py",[88,96,103,110,117,124],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":92,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":92,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"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":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":92,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"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":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":92,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"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":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":92,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"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":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":92,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"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",[],[]]