[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A7DTZ6NDF3C3CFGH4XK3VE":3,"skill-same:01M7A7DTZ6NDF3C3CFGH4XK3VE":82},{"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":41,"commitSha":42,"skillDirectory":43,"forksCount":14,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M7A7DTZ6NDF3C3CFGH4XK3VE","hunting-evtx-with-chainsaw",null,"Run Chainsaw against collected Windows EVTX files to hunt with the SigmaHQ rule corpus, built-in detection rules, and high-speed keyword\u002Fregex search, plus analyze shimcache, SRUM, and event-log gaps, outputting colorized tables, CSV, or JSON. Use during first-response triage for offline, SIEM-free detection over Windows event logs, or to quickly confirm a hunt hypothesis and produce reporting output.","NeelakshSaxena\u002FVayu","NeelakshSaxena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87892838?v=4","01M7A3B9YFS6F6N9DD1787DT86","Neelaksh Saxena","01M7A3B9ZKBT09MNMPX2XN69BY",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fhunting-evtx-with-chainsaw\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fhunting-evtx-with-chainsaw\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: hunting-evtx-with-chainsaw\ndescription: Run Chainsaw against collected Windows EVTX files to hunt with the SigmaHQ rule corpus, built-in detection rules, and high-speed keyword\u002Fregex search, plus analyze shimcache, SRUM, and event-log gaps, outputting colorized tables, CSV, or JSON. Use during first-response triage for offline, SIEM-free detection over Windows event logs, or to quickly confirm a hunt hypothesis and produce reporting output.\ndomain: cybersecurity\nsubdomain: threat-hunting\ntags:\n- chainsaw\n- threat-hunting\n- evtx\n- sigma\n- windows-event-logs\n- dfir\n- detection\n- shimcache\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- DE.AE-02\nmitre_attack:\n- T1059.001\n---\n# Hunting EVTX with Chainsaw\n\n## Overview\n\nChainsaw is a fast, Rust-based forensic artifact search and hunting tool from WithSecure Labs. It provides first-response capability to rapidly identify threats within Windows Event Logs (`.evtx`) and other artifacts. Chainsaw can hunt with the full SigmaHQ rule corpus (translating Sigma to its internal Tau engine), run its own built-in detection rules, perform high-speed keyword\u002Fregex search across logs, and analyse specialized artifacts such as the AppCompatCache (shimcache), SRUM database, and event-log gaps. Output can be a colorized table, CSV, or JSON for downstream tooling.\n\nChainsaw's strength is speed and flexibility during initial triage: an analyst can drop a folder of collected EVTX onto the tool and get back a prioritized set of detections in seconds, then pivot with targeted `search` queries to confirm a hypothesis. Unlike a SIEM, it needs no ingestion pipeline, runs as a single binary, and works fully offline against acquired evidence — ideal for the field or an air-gapped analysis VM. The `--mapping` file tells Chainsaw how Sigma fields translate to Windows event fields, which is what enables broad Sigma coverage over EVTX.\n\nA common hunt outcome is detecting suspicious PowerShell — MITRE ATT&CK **T1059.001 (Command and Scripting Interpreter: PowerShell)** — by running Sigma rules against PowerShell operational logs (Event ID 4104 script-block logging) or searching for encoded-command patterns. This skill maps to NIST CSF **DE.AE-02** (potentially adverse events are analyzed to better understand associated activities).\n\n## When to Use\n\n- During first-response triage to rapidly hunt threats across collected Windows event logs.\n- When you need offline Sigma-based detection over `.evtx` without standing up a SIEM.\n- To run fast keyword\u002Fregex searches confirming or refuting a hunt hypothesis.\n- To analyse shimcache, SRUM, or event-log time gaps for execution evidence and tampering.\n- To produce CSV\u002FJSON detection output for reporting or pipeline ingestion.\n\n## Prerequisites\n\n- Chainsaw binary. Download a release from GitHub or build from source:\n  ```bash\n  # Build from source (Rust toolchain required)\n  git clone https:\u002F\u002Fgithub.com\u002FWithSecureLabs\u002Fchainsaw.git\n  cd chainsaw && cargo build --release\n  .\u002Ftarget\u002Frelease\u002Fchainsaw --version\n  # or: nix profile install github:WithSecureLabs\u002Fchainsaw\n  ```\n- The Chainsaw repo ships `mappings\u002F` (Sigma field mappings) and `rules\u002F` (Chainsaw rules).\n- A copy of the SigmaHQ rules for full Sigma coverage:\n  ```bash\n  git clone https:\u002F\u002Fgithub.com\u002FSigmaHQ\u002Fsigma.git\n  ```\n- Collected Windows `.evtx` files (and registry hives like `SYSTEM`\u002F`Amcache.hve` for shimcache analysis).\n\n## Objectives\n\n- Hunt collected EVTX with Sigma rules using the correct mapping file.\n- Filter detections by rule level, status, and kind to reduce noise.\n- Search logs by keyword, regex, and Tau expression for targeted confirmation.\n- Output detections as table, CSV, and JSON.\n- Analyse shimcache (with Amcache timestamp pairing), SRUM, and event-log gaps.\n\n## MITRE ATT&CK Mapping\n\n| Technique ID | Official Name | Why Chainsaw Detects It |\n|--------------|---------------|-------------------------|\n| T1059.001 | Command and Scripting Interpreter: PowerShell | Sigma rules over EID 4104\u002F4103 and search flag malicious PowerShell |\n| T1059.003 | Command and Scripting Interpreter: Windows Command Shell | Process-creation Sigma rules surface suspicious cmd usage |\n| T1547.001 | Boot or Logon Autostart Execution: Registry Run Keys \u002F Startup Folder | Sigma rules over registry events flag persistence |\n| T1053.005 | Scheduled Task\u002FJob: Scheduled Task | Rules over EID 4698\u002F106 detect task creation |\n| T1070.006 | Indicator Removal: Timestomp | `analyse gaps` and shimcache analysis reveal tampering\u002Ftime gaps |\n| T1204.002 | User Execution: Malicious File | Shimcache analysis shows executed binaries |\n\n## Workflow\n\n### 1. Hunt EVTX with Sigma rules\nRun the SigmaHQ corpus against collected logs using the bundled mapping file. The mapping translates Sigma fields to EVTX fields.\n```bash\nchainsaw hunt .\u002Fcollected_evtx \\\n  -s .\u002Fsigma\u002Frules \\\n  --mapping .\u002Fmappings\u002Fsigma-event-logs-all.yml\n```\n\n### 2. Hunt with Chainsaw built-in rules plus Sigma\nCombine Chainsaw's own rules (`-r`) with Sigma (`-s`) for broader coverage.\n```bash\nchainsaw hunt .\u002Fcollected_evtx \\\n  -r .\u002Frules \\\n  -s .\u002Fsigma\u002Frules \\\n  --mapping .\u002Fmappings\u002Fsigma-event-logs-all.yml\n```\n\n### 3. Filter to reduce noise\nLimit results by Sigma rule level, status, and detection kind.\n```bash\nchainsaw hunt .\u002Fcollected_evtx -s .\u002Fsigma\u002Frules \\\n  --mapping .\u002Fmappings\u002Fsigma-event-logs-all.yml \\\n  --level high --status stable --kind evtx\n```\n\n### 4. Output to CSV and JSON\nWrite structured output for reporting and pipelines.\n```bash\n# JSON to stdout\u002Ffile\nchainsaw hunt .\u002Fcollected_evtx -s .\u002Fsigma\u002Frules \\\n  --mapping .\u002Fmappings\u002Fsigma-event-logs-all.yml --json > detections.json\n\n# CSV into a directory (one file per detection group)\nchainsaw hunt .\u002Fcollected_evtx -s .\u002Fsigma\u002Frules \\\n  --mapping .\u002Fmappings\u002Fsigma-event-logs-all.yml --csv --output .\u002Fcsv_out\n```\n\n### 5. Targeted keyword and regex search\nConfirm a hypothesis by searching raw events independent of rules.\n```bash\n# Case-insensitive keyword search\nchainsaw search \"mimikatz\" -i .\u002Fcollected_evtx\n\n# Regex for base64-encoded PowerShell commands, as JSON\nchainsaw search -e \"-[Ee]nc(odedCommand)?\\s+[A-Za-z0-9+\u002F=]{20,}\" .\u002Fcollected_evtx --json\n\n# Time-bounded search using a Tau expression\nchainsaw search .\u002Fcollected_evtx -t 'Event.System.EventID: =4624' \\\n  --from \"2026-06-01T00:00:00\" --to \"2026-06-20T00:00:00\"\n```\n\n### 6. Analyse shimcache for execution evidence\nParse the AppCompatCache from the SYSTEM hive, pair it with Amcache timestamps, and pattern-match suspicious entries.\n```bash\nchainsaw analyse shimcache .\u002FSYSTEM \\\n  --regexfile .\u002Fshimcache_patterns.txt \\\n  --amcache .\u002FAmcache.hve --tspair \\\n  --output .\u002Fshimcache_analysis.csv\n```\n\n### 7. Analyse SRUM and event-log gaps\nDetect program\u002Fnetwork usage and identify suspicious logging gaps (possible log clearing or timestomp).\n```bash\n# SRUM database analysis\nchainsaw analyse srum --software .\u002FSOFTWARE .\u002FSRUDB.dat -o srum.json\n\n# Event-log gaps that may indicate cleared\u002Ftampered logs\nchainsaw analyse gaps .\u002Fcollected_evtx --min-time-gap-minutes 30 --json\n```\n\n### 8. Dump and lint\nInspect raw artifact content and validate custom rules before a hunt.\n```bash\nchainsaw dump .\u002FSOFTWARE --json --output dump.json\nchainsaw lint -r .\u002Frules --kind sigma\n```\n\n## Tools and Resources\n\n| Tool | Purpose | Source |\n|------|---------|--------|\n| Chainsaw | Fast EVTX\u002Fartifact hunting and search | https:\u002F\u002Fgithub.com\u002FWithSecureLabs\u002Fchainsaw |\n| SigmaHQ rules | Community detection rules | https:\u002F\u002Fgithub.com\u002FSigmaHQ\u002Fsigma |\n| Chainsaw mappings | Sigma-to-EVTX field mappings | https:\u002F\u002Fgithub.com\u002FWithSecureLabs\u002Fchainsaw\u002Ftree\u002Fmaster\u002Fmappings |\n| Hayabusa | Alternative Sigma EVTX timeline tool | https:\u002F\u002Fgithub.com\u002FYamato-Security\u002Fhayabusa |\n| Timeline Explorer | Review CSV output | https:\u002F\u002Fericzimmerman.github.io\u002F |\n\n## Validation Criteria\n\n- [ ] Chainsaw binary installed and `--version` confirmed.\n- [ ] SigmaHQ rules and the correct mapping file available.\n- [ ] Sigma hunt run against the collected EVTX directory.\n- [ ] Chainsaw built-in rules combined with Sigma where appropriate.\n- [ ] Detections filtered by level\u002Fstatus\u002Fkind to reduce noise.\n- [ ] CSV and\u002For JSON output produced for reporting.\n- [ ] Targeted keyword\u002Fregex\u002FTau searches run to confirm findings.\n- [ ] Shimcache analysed with Amcache timestamp pairing.\n- [ ] SRUM and event-log-gap analysis performed where artifacts exist.\n- [ ] Findings (e.g., PowerShell T1059.001) documented for the hunt report.\n","# Hunting EVTX with Chainsaw\n\n## Overview\n\nChainsaw is a fast, Rust-based forensic artifact search and hunting tool from WithSecure Labs. It provides first-response capability to rapidly identify threats within Windows Event Logs (`.evtx`) and other artifacts. Chainsaw can hunt with the full SigmaHQ rule corpus (translating Sigma to its internal Tau engine), run its own built-in detection rules, perform high-speed keyword\u002Fregex search across logs, and analyse specialized artifacts such as the AppCompatCache (shimcache), SRUM database, and event-log gaps. Output can be a colorized table, CSV, or JSON for downstream tooling.\n\nChainsaw's strength is speed and flexibility during initial triage: an analyst can drop a folder of collected EVTX onto the tool and get back a prioritized set of detections in seconds, then pivot with targeted `search` queries to confirm a hypothesis. Unlike a SIEM, it needs no ingestion pipeline, runs as a single binary, and works fully offline against acquired evidence — ideal for the field or an air-gapped analysis VM. The `--mapping` file tells Chainsaw how Sigma fields translate to Windows event fields, which is what enables broad Sigma coverage over EVTX.\n\nA common hunt outcome is detecting suspicious PowerShell — MITRE ATT&CK **T1059.001 (Command and Scripting Interpreter: PowerShell)** — by running Sigma rules against PowerShell operational logs (Event ID 4104 script-block logging) or searching for encoded-command patterns. This skill maps to NIST CSF **DE.AE-02** (potentially adverse events are analyzed to better understand associated activities).\n\n## When to Use\n\n- During first-response triage to rapidly hunt threats across collected Windows event logs.\n- When you need offline Sigma-based detection over `.evtx` without standing up a SIEM.\n- To run fast keyword\u002Fregex searches confirming or refuting a hunt hypothesis.\n- To analyse shimcache, SRUM, or event-log time gaps for execution evidence and tampering.\n- To produce CSV\u002FJSON detection output for reporting or pipeline ingestion.\n\n## Prerequisites\n\n- Chainsaw binary. Download a release from GitHub or build from source:\n  ```bash\n  # Build from source (Rust toolchain required)\n  git clone https:\u002F\u002Fgithub.com\u002FWithSecureLabs\u002Fchainsaw.git\n  cd chainsaw && cargo build --release\n  .\u002Ftarget\u002Frelease\u002Fchainsaw --version\n  # or: nix profile install github:WithSecureLabs\u002Fchainsaw\n  ```\n- The Chainsaw repo ships `mappings\u002F` (Sigma field mappings) and `rules\u002F` (Chainsaw rules).\n- A copy of the SigmaHQ rules for full Sigma coverage:\n  ```bash\n  git clone https:\u002F\u002Fgithub.com\u002FSigmaHQ\u002Fsigma.git\n  ```\n- Collected Windows `.evtx` files (and registry hives like `SYSTEM`\u002F`Amcache.hve` for shimcache analysis).\n\n## Objectives\n\n- Hunt collected EVTX with Sigma rules using the correct mapping file.\n- Filter detections by rule level, status, and kind to reduce noise.\n- Search logs by keyword, regex, and Tau expression for targeted confirmation.\n- Output detections as table, CSV, and JSON.\n- Analyse shimcache (with Amcache timestamp pairing), SRUM, and event-log gaps.\n\n## MITRE ATT&CK Mapping\n\n| Technique ID | Official Name | Why Chainsaw Detects It |\n|--------------|---------------|-------------------------|\n| T1059.001 | Command and Scripting Interpreter: PowerShell | Sigma rules over EID 4104\u002F4103 and search flag malicious PowerShell |\n| T1059.003 | Command and Scripting Interpreter: Windows Command Shell | Process-creation Sigma rules surface suspicious cmd usage |\n| T1547.001 | Boot or Logon Autostart Execution: Registry Run Keys \u002F Startup Folder | Sigma rules over registry events flag persistence |\n| T1053.005 | Scheduled Task\u002FJob: Scheduled Task | Rules over EID 4698\u002F106 detect task creation |\n| T1070.006 | Indicator Removal: Timestomp | `analyse gaps` and shimcache analysis reveal tampering\u002Ftime gaps |\n| T1204.002 | User Execution: Malicious File | Shimcache analysis shows executed binaries |\n\n## Workflow\n\n### 1. Hunt EVTX with Sigma rules\nRun the SigmaHQ corpus against collected logs using the bundled mapping file. The mapping translates Sigma fields to EVTX fields.\n```bash\nchainsaw hunt .\u002Fcollected_evtx \\\n  -s .\u002Fsigma\u002Frules \\\n  --mapping .\u002Fmappings\u002Fsigma-event-logs-all.yml\n```\n\n### 2. Hunt with Chainsaw built-in rules plus Sigma\nCombine Chainsaw's own rules (`-r`) with Sigma (`-s`) for broader coverage.\n```bash\nchainsaw hunt .\u002Fcollected_evtx \\\n  -r .\u002Frules \\\n  -s .\u002Fsigma\u002Frules \\\n  --mapping .\u002Fmappings\u002Fsigma-event-logs-all.yml\n```\n\n### 3. Filter to reduce noise\nLimit results by Sigma rule level, status, and detection kind.\n```bash\nchainsaw hunt .\u002Fcollected_evtx -s .\u002Fsigma\u002Frules \\\n  --mapping .\u002Fmappings\u002Fsigma-event-logs-all.yml \\\n  --level high --status stable --kind evtx\n```\n\n### 4. Output to CSV and JSON\nWrite structured output for reporting and pipelines.\n```bash\n# JSON to stdout\u002Ffile\nchainsaw hunt .\u002Fcollected_evtx -s .\u002Fsigma\u002Frules \\\n  --mapping .\u002Fmappings\u002Fsigma-event-logs-all.yml --json > detections.json\n\n# CSV into a directory (one file per detection group)\nchainsaw hunt .\u002Fcollected_evtx -s .\u002Fsigma\u002Frules \\\n  --mapping .\u002Fmappings\u002Fsigma-event-logs-all.yml --csv --output .\u002Fcsv_out\n```\n\n### 5. Targeted keyword and regex search\nConfirm a hypothesis by searching raw events independent of rules.\n```bash\n# Case-insensitive keyword search\nchainsaw search \"mimikatz\" -i .\u002Fcollected_evtx\n\n# Regex for base64-encoded PowerShell commands, as JSON\nchainsaw search -e \"-[Ee]nc(odedCommand)?\\s+[A-Za-z0-9+\u002F=]{20,}\" .\u002Fcollected_evtx --json\n\n# Time-bounded search using a Tau expression\nchainsaw search .\u002Fcollected_evtx -t 'Event.System.EventID: =4624' \\\n  --from \"2026-06-01T00:00:00\" --to \"2026-06-20T00:00:00\"\n```\n\n### 6. Analyse shimcache for execution evidence\nParse the AppCompatCache from the SYSTEM hive, pair it with Amcache timestamps, and pattern-match suspicious entries.\n```bash\nchainsaw analyse shimcache .\u002FSYSTEM \\\n  --regexfile .\u002Fshimcache_patterns.txt \\\n  --amcache .\u002FAmcache.hve --tspair \\\n  --output .\u002Fshimcache_analysis.csv\n```\n\n### 7. Analyse SRUM and event-log gaps\nDetect program\u002Fnetwork usage and identify suspicious logging gaps (possible log clearing or timestomp).\n```bash\n# SRUM database analysis\nchainsaw analyse srum --software .\u002FSOFTWARE .\u002FSRUDB.dat -o srum.json\n\n# Event-log gaps that may indicate cleared\u002Ftampered logs\nchainsaw analyse gaps .\u002Fcollected_evtx --min-time-gap-minutes 30 --json\n```\n\n### 8. Dump and lint\nInspect raw artifact content and validate custom rules before a hunt.\n```bash\nchainsaw dump .\u002FSOFTWARE --json --output dump.json\nchainsaw lint -r .\u002Frules --kind sigma\n```\n\n## Tools and Resources\n\n| Tool | Purpose | Source |\n|------|---------|--------|\n| Chainsaw | Fast EVTX\u002Fartifact hunting and search | https:\u002F\u002Fgithub.com\u002FWithSecureLabs\u002Fchainsaw |\n| SigmaHQ rules | Community detection rules | https:\u002F\u002Fgithub.com\u002FSigmaHQ\u002Fsigma |\n| Chainsaw mappings | Sigma-to-EVTX field mappings | https:\u002F\u002Fgithub.com\u002FWithSecureLabs\u002Fchainsaw\u002Ftree\u002Fmaster\u002Fmappings |\n| Hayabusa | Alternative Sigma EVTX timeline tool | https:\u002F\u002Fgithub.com\u002FYamato-Security\u002Fhayabusa |\n| Timeline Explorer | Review CSV output | https:\u002F\u002Fericzimmerman.github.io\u002F |\n\n## Validation Criteria\n\n- [ ] Chainsaw binary installed and `--version` confirmed.\n- [ ] SigmaHQ rules and the correct mapping file available.\n- [ ] Sigma hunt run against the collected EVTX directory.\n- [ ] Chainsaw built-in rules combined with Sigma where appropriate.\n- [ ] Detections filtered by level\u002Fstatus\u002Fkind to reduce noise.\n- [ ] CSV and\u002For JSON output produced for reporting.\n- [ ] Targeted keyword\u002Fregex\u002FTau searches run to confirm findings.\n- [ ] Shimcache analysed with Amcache timestamp pairing.\n- [ ] SRUM and event-log-gap analysis performed where artifacts exist.\n- [ ] Findings (e.g., PowerShell T1059.001) documented for the hunt report.\n",{"name":5,"tags":25,"author":34,"domain":35,"license":15,"version":36,"nist_csf":37,"subdomain":27,"description":7,"mitre_attack":39},[26,27,28,29,30,31,32,33],"chainsaw","threat-hunting","evtx","sigma","windows-event-logs","dfir","detection","shimcache","mahipal","cybersecurity","1.0",[38],"DE.AE-02",[40],"T1059.001","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fhunting-evtx-with-chainsaw","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena","Currently exploring the intersection of tech","2026-09-11 03:02:31",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add NeelakshSaxena\u002FVayu --skill hunting-evtx-with-chainsaw",{"tool":54,"command":55},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill hunting-evtx-with-chainsaw",{"tool":57,"command":58},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill hunting-evtx-with-chainsaw","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fhunting-evtx-with-chainsaw\u002FSKILL.md",true,[62,66,72,76],{"path":63,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fapi-reference.md","REFERENCE","参考文档",2204,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fhunting-evtx-with-chainsaw\u002Freferences\u002Fapi-reference.md",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fstandards.md",1771,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fhunting-evtx-with-chainsaw\u002Freferences\u002Fstandards.md",{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"scripts\u002Fagent.py","SCRIPT","脚本",4803,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fhunting-evtx-with-chainsaw\u002Fscripts\u002Fagent.py",[83,90,97,104,111,118],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":20},"01M7ACCCVNCFKMA9X6D15X6G98","runpodctl","Runpod CLI for managing GPU\u002FCPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send\u002Freceive). Use for terminal\u002FCI\u002Fscripting, Hub browse\u002Fdeploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpodctl\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":20},"01M7ACC63SRHEA5KMCHSMZK2TC","runpod","Start here for any Runpod task — running GPU\u002FCPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":20},"01M7ACC0Q1C89N9BZBV91CTQTF","runpod-usage","How Runpod works and how to work it — pods vs serverless, GPU\u002FVRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv\u002Fapt). Use to answer \"how does X work\", \"which GPU\", \"how do I build a container\", or \"how do I stand up a workload on a pod\". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-usage\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":20},"01M7ACBRPE345GF5GM5B8P8RRC","runpod-templates","Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says \"run \u003CX> on a pod\" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-templates\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":20},"01M7ACBJATHKVX1TWES2F44GY8","runpod-migrate","Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-migrate\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},"01M7ACBC7GHVH6T9YEAPCG2AP8","runpod-mcp","Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU\u002FCPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-mcp\u002FSKILL.md",[],[]]