[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E3Z0PCKHCS7H0GJJSRWAMG":3,"skill-same:01M7E3Z0PCKHCS7H0GJJSRWAMG":84},{"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":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M7E3Z0PCKHCS7H0GJJSRWAMG","generating-forensic-timelines-with-hayabusa",null,"Run Hayabusa against collected Windows EVTX files to apply Sigma detection rules and produce a prioritized, chronological CSV\u002FJSON timeline with severity levels, MITRE ATT&CK mappings, and per-host\u002Fper-Event-ID metrics. Use during DFIR triage to turn raw event logs into a fast, SIEM-free incident timeline, or to export results into Timesketch or Timeline Explorer for collaborative analysis.","sanjeevafk\u002Fagent-skills","sanjeevafk","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F230678117?v=4","01M7C540EFY46ETG1NNWKS5X3Q","Sanjeev","01M7C540F366J5C1D587BMKH9Q",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fgenerating-forensic-timelines-with-hayabusa\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fgenerating-forensic-timelines-with-hayabusa\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: generating-forensic-timelines-with-hayabusa\ndescription: Run Hayabusa against collected Windows EVTX files to apply Sigma detection rules and produce a prioritized, chronological CSV\u002FJSON timeline with severity levels, MITRE ATT&CK mappings, and per-host\u002Fper-Event-ID metrics. Use during DFIR triage to turn raw event logs into a fast, SIEM-free incident timeline, or to export results into Timesketch or Timeline Explorer for collaborative analysis.\ndomain: cybersecurity\nsubdomain: digital-forensics\ntags:\n- hayabusa\n- dfir\n- evtx\n- sigma\n- timeline\n- threat-hunting\n- windows-event-logs\n- forensics\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- RS.AN-03\nmitre_attack:\n- T1059.001\n---\n# Generating Forensic Timelines with Hayabusa\n\n## Overview\n\nHayabusa (隼, Japanese for \"peregrine falcon\") is a Sigma-based threat-hunting and fast-forensics timeline generator for Windows event logs, developed by Yamato Security in Rust. It parses `.evtx` files (offline or via live analysis of a local host), applies a large built-in library of Sigma detection rules plus Hayabusa-specific rules, and produces a single, readable, chronological timeline of high-signal events with severity levels, MITRE ATT&CK tactics, and rule references. This collapses thousands of raw event-log records into a prioritized incident timeline that an analyst can review quickly.\n\nHayabusa is purpose-built for DFIR triage. Instead of loading EVTX into a SIEM, an investigator runs a single binary against a directory of collected logs and gets a CSV or JSON timeline plus metrics (events per computer, per Event ID, per channel). Because detections are Sigma-based, coverage tracks the open detection-engineering community, and rules can be updated on demand with `update-rules`. The tool's output integrates with downstream analysis: CSV opens in Timeline Explorer, JSONL feeds into `jq`, and `timesketch-*` profiles export directly into Timesketch.\n\nA frequent finding in Hayabusa timelines is malicious PowerShell — MITRE ATT&CK **T1059.001 (Command and Scripting Interpreter: PowerShell)** — surfaced via Sigma rules over Event ID 4104 (script-block logging), 4103, and Sysmon process creation. This skill maps to NIST CSF **RS.AN-03** (analysis is performed to establish what has taken place during an incident).\n\n## When to Use\n\n- During incident-response triage, to turn a pile of collected `.evtx` files into a prioritized timeline.\n- When you need fast, SIEM-free detection over Windows event logs with community Sigma coverage.\n- To enumerate suspicious activity (PowerShell, account changes, lateral movement) across many hosts' logs.\n- To produce metrics (events per computer\u002FEvent ID\u002Fchannel) and pivot keywords for deeper hunting.\n- To export an incident timeline into Timesketch or Timeline Explorer for collaborative analysis.\n\n## Prerequisites\n\n- Hayabusa binary. Download a pre-compiled release (Windows\u002FLinux\u002FmacOS) from GitHub:\n  ```bash\n  # Linux example\n  curl -LO https:\u002F\u002Fgithub.com\u002FYamato-Security\u002Fhayabusa\u002Freleases\u002Flatest\u002Fdownload\u002Fhayabusa-3.0.0-lin-x64-gnu.zip\n  unzip hayabusa-*.zip && cd hayabusa-*\n  .\u002Fhayabusa-3.0.0-lin-x64-gnu --version\n  ```\n  Or build from source (rules are a submodule):\n  ```bash\n  git clone https:\u002F\u002Fgithub.com\u002FYamato-Security\u002Fhayabusa.git --recursive\n  cd hayabusa && cargo build --release\n  ```\n- Collected Windows `.evtx` files (or run with `--live-analysis` on the host, as Administrator).\n- Updated detection rules:\n  ```bash\n  .\u002Fhayabusa update-rules\n  ```\n- Optional: Timeline Explorer (Windows) or Timesketch for visualizing output; `jq` for JSONL.\n\n## Objectives\n\n- Build a CSV or JSON forensic timeline from a directory of `.evtx` files.\n- Update and tune the Sigma rule set used for detection.\n- Select an output profile appropriate to the investigation (minimal vs. verbose vs. timesketch).\n- Generate metrics (computer, Event ID, log) and pivot keywords for hunting leads.\n- Filter the timeline by minimum severity to focus triage.\n- Search logs for specific IOCs by keyword or regex.\n\n## MITRE ATT&CK Mapping\n\n| Technique ID | Official Name | Why Hayabusa Detects It |\n|--------------|---------------|-------------------------|\n| T1059.001 | Command and Scripting Interpreter: PowerShell | Sigma rules over Event IDs 4104\u002F4103 and Sysmon flag malicious PowerShell |\n| T1059.003 | Command and Scripting Interpreter: Windows Command Shell | Rules over process-creation events surface suspicious cmd usage |\n| T1078 | Valid Accounts | Logon events (4624\u002F4625\u002F4672) reveal anomalous authentication |\n| T1547.001 | Boot or Logon Autostart Execution: Registry Run Keys \u002F Startup Folder | Rules over registry-modification events flag persistence |\n| T1053.005 | Scheduled Task\u002FJob: Scheduled Task | Event ID 4698\u002F106 rules surface task creation |\n| T1003 | OS Credential Dumping | Rules flag LSASS access and credential-dumping patterns |\n\n## Workflow\n\n### 1. Update the rule set\nPull the latest Sigma and Hayabusa rules before every investigation.\n```bash\n.\u002Fhayabusa update-rules\n```\n\n### 2. Build a CSV timeline from collected logs\nPoint Hayabusa at a directory of `.evtx` files and write a CSV timeline. `-w` skips the interactive wizard for scripted runs.\n```bash\n.\u002Fhayabusa csv-timeline -d .\u002Fcollected_evtx -o timeline.csv -w\n# UTC timestamps for cross-host correlation\n.\u002Fhayabusa csv-timeline -d .\u002Fcollected_evtx -o timeline_utc.csv -U -w\n```\n\n### 3. Choose an output profile\nProfiles control detail. Use `verbose` to include MITRE ATT&CK tactics, tags, and the source rule\u002FEVTX file; `all-field-info` to retain every original field.\n```bash\n# Verbose: adds MITRE tactics, tags, rule file, evtx file\n.\u002Fhayabusa csv-timeline -d .\u002Fcollected_evtx -o timeline_verbose.csv -p verbose -w\n# Preserve all original event fields\n.\u002Fhayabusa csv-timeline -d .\u002Fcollected_evtx -o timeline_full.csv -p all-field-info -w\n```\nAvailable profiles: `minimal`, `standard` (default), `verbose`, `all-field-info`, `all-field-info-verbose`, `super-verbose`, `timesketch-minimal`, `timesketch-verbose`.\n\n### 4. Filter by minimum severity\nFocus triage on the highest-confidence detections with `-m`\u002F`--min-level`.\n```bash\n.\u002Fhayabusa csv-timeline -d .\u002Fcollected_evtx -o critical.csv -m high -w\n```\nLevels: `informational`, `low`, `medium`, `high`, `critical`.\n\n### 5. Produce a JSON\u002FJSONL timeline for tooling\nJSONL feeds cleanly into `jq` and downstream pipelines.\n```bash\n.\u002Fhayabusa json-timeline -d .\u002Fcollected_evtx -L -o timeline.jsonl -w\n# Example: top rule titles\njq -r '.RuleTitle' timeline.jsonl | sort | uniq -c | sort -rn | head\n```\n\n### 6. Generate metrics and pivot keywords\nSummaries reveal which hosts and Event IDs dominate, and pivot keywords give hunting leads.\n```bash\n.\u002Fhayabusa computer-metrics -d .\u002Fcollected_evtx -o computers.csv\n.\u002Fhayabusa eid-metrics -d .\u002Fcollected_evtx -o eid.csv\n.\u002Fhayabusa log-metrics -d .\u002Fcollected_evtx -o logs.csv\n.\u002Fhayabusa pivot-keywords-list -d .\u002Fcollected_evtx -m medium -o pivots\n```\n\n### 7. Search logs for specific IOCs\nUse the `search` command for keyword or regex hunting independent of detection rules.\n```bash\n# Keyword search (case-insensitive) for a suspicious binary\n.\u002Fhayabusa search -d .\u002Fcollected_evtx -k \"powershell\" -i\n# Regex search for base64-looking PowerShell encoded commands\n.\u002Fhayabusa search -d .\u002Fcollected_evtx -r \"-[Ee]nc(odedCommand)?\\s+[A-Za-z0-9+\u002F=]{20,}\"\n```\n\n### 8. Live triage on a running host\nOn the affected machine (Administrator), analyze local logs without exporting first.\n```bash\n.\u002Fhayabusa csv-timeline -l -o live_timeline.csv -m high -w\n```\n\n## Tools and Resources\n\n| Tool | Purpose | Source |\n|------|---------|--------|\n| Hayabusa | Sigma-based EVTX timeline\u002Fthreat hunting | https:\u002F\u002Fgithub.com\u002FYamato-Security\u002Fhayabusa |\n| hayabusa-rules | Sigma + Hayabusa detection rules | https:\u002F\u002Fgithub.com\u002FYamato-Security\u002Fhayabusa-rules |\n| Takajō | Hayabusa results analyzer | https:\u002F\u002Fgithub.com\u002FYamato-Security\u002Ftakajo |\n| Timeline Explorer | Review CSV timelines | https:\u002F\u002Fericzimmerman.github.io\u002F |\n| Timesketch | Collaborative timeline analysis | https:\u002F\u002Ftimesketch.org\u002F |\n| Sigma | Generic detection rule format | https:\u002F\u002Fgithub.com\u002FSigmaHQ\u002Fsigma |\n\n## Validation Criteria\n\n- [ ] Hayabusa binary installed and `--version` confirmed.\n- [ ] Rules updated with `update-rules` before analysis.\n- [ ] CSV timeline generated from the collected `.evtx` directory.\n- [ ] Appropriate output profile selected for the investigation goal.\n- [ ] Timeline filtered by minimum severity for triage focus.\n- [ ] JSON\u002FJSONL timeline produced for downstream tooling where needed.\n- [ ] Computer\u002FEID\u002Flog metrics generated.\n- [ ] Pivot keywords list produced for hunting leads.\n- [ ] Targeted IOC searches run with keyword\u002Fregex.\n- [ ] Findings (e.g., PowerShell T1059.001 detections) documented in the incident timeline.\n","# Generating Forensic Timelines with Hayabusa\n\n## Overview\n\nHayabusa (隼, Japanese for \"peregrine falcon\") is a Sigma-based threat-hunting and fast-forensics timeline generator for Windows event logs, developed by Yamato Security in Rust. It parses `.evtx` files (offline or via live analysis of a local host), applies a large built-in library of Sigma detection rules plus Hayabusa-specific rules, and produces a single, readable, chronological timeline of high-signal events with severity levels, MITRE ATT&CK tactics, and rule references. This collapses thousands of raw event-log records into a prioritized incident timeline that an analyst can review quickly.\n\nHayabusa is purpose-built for DFIR triage. Instead of loading EVTX into a SIEM, an investigator runs a single binary against a directory of collected logs and gets a CSV or JSON timeline plus metrics (events per computer, per Event ID, per channel). Because detections are Sigma-based, coverage tracks the open detection-engineering community, and rules can be updated on demand with `update-rules`. The tool's output integrates with downstream analysis: CSV opens in Timeline Explorer, JSONL feeds into `jq`, and `timesketch-*` profiles export directly into Timesketch.\n\nA frequent finding in Hayabusa timelines is malicious PowerShell — MITRE ATT&CK **T1059.001 (Command and Scripting Interpreter: PowerShell)** — surfaced via Sigma rules over Event ID 4104 (script-block logging), 4103, and Sysmon process creation. This skill maps to NIST CSF **RS.AN-03** (analysis is performed to establish what has taken place during an incident).\n\n## When to Use\n\n- During incident-response triage, to turn a pile of collected `.evtx` files into a prioritized timeline.\n- When you need fast, SIEM-free detection over Windows event logs with community Sigma coverage.\n- To enumerate suspicious activity (PowerShell, account changes, lateral movement) across many hosts' logs.\n- To produce metrics (events per computer\u002FEvent ID\u002Fchannel) and pivot keywords for deeper hunting.\n- To export an incident timeline into Timesketch or Timeline Explorer for collaborative analysis.\n\n## Prerequisites\n\n- Hayabusa binary. Download a pre-compiled release (Windows\u002FLinux\u002FmacOS) from GitHub:\n  ```bash\n  # Linux example\n  curl -LO https:\u002F\u002Fgithub.com\u002FYamato-Security\u002Fhayabusa\u002Freleases\u002Flatest\u002Fdownload\u002Fhayabusa-3.0.0-lin-x64-gnu.zip\n  unzip hayabusa-*.zip && cd hayabusa-*\n  .\u002Fhayabusa-3.0.0-lin-x64-gnu --version\n  ```\n  Or build from source (rules are a submodule):\n  ```bash\n  git clone https:\u002F\u002Fgithub.com\u002FYamato-Security\u002Fhayabusa.git --recursive\n  cd hayabusa && cargo build --release\n  ```\n- Collected Windows `.evtx` files (or run with `--live-analysis` on the host, as Administrator).\n- Updated detection rules:\n  ```bash\n  .\u002Fhayabusa update-rules\n  ```\n- Optional: Timeline Explorer (Windows) or Timesketch for visualizing output; `jq` for JSONL.\n\n## Objectives\n\n- Build a CSV or JSON forensic timeline from a directory of `.evtx` files.\n- Update and tune the Sigma rule set used for detection.\n- Select an output profile appropriate to the investigation (minimal vs. verbose vs. timesketch).\n- Generate metrics (computer, Event ID, log) and pivot keywords for hunting leads.\n- Filter the timeline by minimum severity to focus triage.\n- Search logs for specific IOCs by keyword or regex.\n\n## MITRE ATT&CK Mapping\n\n| Technique ID | Official Name | Why Hayabusa Detects It |\n|--------------|---------------|-------------------------|\n| T1059.001 | Command and Scripting Interpreter: PowerShell | Sigma rules over Event IDs 4104\u002F4103 and Sysmon flag malicious PowerShell |\n| T1059.003 | Command and Scripting Interpreter: Windows Command Shell | Rules over process-creation events surface suspicious cmd usage |\n| T1078 | Valid Accounts | Logon events (4624\u002F4625\u002F4672) reveal anomalous authentication |\n| T1547.001 | Boot or Logon Autostart Execution: Registry Run Keys \u002F Startup Folder | Rules over registry-modification events flag persistence |\n| T1053.005 | Scheduled Task\u002FJob: Scheduled Task | Event ID 4698\u002F106 rules surface task creation |\n| T1003 | OS Credential Dumping | Rules flag LSASS access and credential-dumping patterns |\n\n## Workflow\n\n### 1. Update the rule set\nPull the latest Sigma and Hayabusa rules before every investigation.\n```bash\n.\u002Fhayabusa update-rules\n```\n\n### 2. Build a CSV timeline from collected logs\nPoint Hayabusa at a directory of `.evtx` files and write a CSV timeline. `-w` skips the interactive wizard for scripted runs.\n```bash\n.\u002Fhayabusa csv-timeline -d .\u002Fcollected_evtx -o timeline.csv -w\n# UTC timestamps for cross-host correlation\n.\u002Fhayabusa csv-timeline -d .\u002Fcollected_evtx -o timeline_utc.csv -U -w\n```\n\n### 3. Choose an output profile\nProfiles control detail. Use `verbose` to include MITRE ATT&CK tactics, tags, and the source rule\u002FEVTX file; `all-field-info` to retain every original field.\n```bash\n# Verbose: adds MITRE tactics, tags, rule file, evtx file\n.\u002Fhayabusa csv-timeline -d .\u002Fcollected_evtx -o timeline_verbose.csv -p verbose -w\n# Preserve all original event fields\n.\u002Fhayabusa csv-timeline -d .\u002Fcollected_evtx -o timeline_full.csv -p all-field-info -w\n```\nAvailable profiles: `minimal`, `standard` (default), `verbose`, `all-field-info`, `all-field-info-verbose`, `super-verbose`, `timesketch-minimal`, `timesketch-verbose`.\n\n### 4. Filter by minimum severity\nFocus triage on the highest-confidence detections with `-m`\u002F`--min-level`.\n```bash\n.\u002Fhayabusa csv-timeline -d .\u002Fcollected_evtx -o critical.csv -m high -w\n```\nLevels: `informational`, `low`, `medium`, `high`, `critical`.\n\n### 5. Produce a JSON\u002FJSONL timeline for tooling\nJSONL feeds cleanly into `jq` and downstream pipelines.\n```bash\n.\u002Fhayabusa json-timeline -d .\u002Fcollected_evtx -L -o timeline.jsonl -w\n# Example: top rule titles\njq -r '.RuleTitle' timeline.jsonl | sort | uniq -c | sort -rn | head\n```\n\n### 6. Generate metrics and pivot keywords\nSummaries reveal which hosts and Event IDs dominate, and pivot keywords give hunting leads.\n```bash\n.\u002Fhayabusa computer-metrics -d .\u002Fcollected_evtx -o computers.csv\n.\u002Fhayabusa eid-metrics -d .\u002Fcollected_evtx -o eid.csv\n.\u002Fhayabusa log-metrics -d .\u002Fcollected_evtx -o logs.csv\n.\u002Fhayabusa pivot-keywords-list -d .\u002Fcollected_evtx -m medium -o pivots\n```\n\n### 7. Search logs for specific IOCs\nUse the `search` command for keyword or regex hunting independent of detection rules.\n```bash\n# Keyword search (case-insensitive) for a suspicious binary\n.\u002Fhayabusa search -d .\u002Fcollected_evtx -k \"powershell\" -i\n# Regex search for base64-looking PowerShell encoded commands\n.\u002Fhayabusa search -d .\u002Fcollected_evtx -r \"-[Ee]nc(odedCommand)?\\s+[A-Za-z0-9+\u002F=]{20,}\"\n```\n\n### 8. Live triage on a running host\nOn the affected machine (Administrator), analyze local logs without exporting first.\n```bash\n.\u002Fhayabusa csv-timeline -l -o live_timeline.csv -m high -w\n```\n\n## Tools and Resources\n\n| Tool | Purpose | Source |\n|------|---------|--------|\n| Hayabusa | Sigma-based EVTX timeline\u002Fthreat hunting | https:\u002F\u002Fgithub.com\u002FYamato-Security\u002Fhayabusa |\n| hayabusa-rules | Sigma + Hayabusa detection rules | https:\u002F\u002Fgithub.com\u002FYamato-Security\u002Fhayabusa-rules |\n| Takajō | Hayabusa results analyzer | https:\u002F\u002Fgithub.com\u002FYamato-Security\u002Ftakajo |\n| Timeline Explorer | Review CSV timelines | https:\u002F\u002Fericzimmerman.github.io\u002F |\n| Timesketch | Collaborative timeline analysis | https:\u002F\u002Ftimesketch.org\u002F |\n| Sigma | Generic detection rule format | https:\u002F\u002Fgithub.com\u002FSigmaHQ\u002Fsigma |\n\n## Validation Criteria\n\n- [ ] Hayabusa binary installed and `--version` confirmed.\n- [ ] Rules updated with `update-rules` before analysis.\n- [ ] CSV timeline generated from the collected `.evtx` directory.\n- [ ] Appropriate output profile selected for the investigation goal.\n- [ ] Timeline filtered by minimum severity for triage focus.\n- [ ] JSON\u002FJSONL timeline produced for downstream tooling where needed.\n- [ ] Computer\u002FEID\u002Flog metrics generated.\n- [ ] Pivot keywords list produced for hunting leads.\n- [ ] Targeted IOC searches run with keyword\u002Fregex.\n- [ ] Findings (e.g., PowerShell T1059.001 detections) documented in the incident timeline.\n",{"name":5,"tags":25,"author":34,"domain":35,"license":15,"version":36,"nist_csf":37,"subdomain":39,"description":7,"mitre_attack":40},[26,27,28,29,30,31,32,33],"hayabusa","dfir","evtx","sigma","timeline","threat-hunting","windows-event-logs","forensics","mahipal","cybersecurity","1.0",[38],"RS.AN-03","digital-forensics",[41],"T1059.001","main","4e084e84eb42fc53e144c89c0f7f48b39c8a4b0f","collections\u002Fcybersecurity-skills\u002Fskills\u002Fgenerating-forensic-timelines-with-hayabusa",1,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills","https:\u002F\u002Fgithub.com\u002Fsanjeevafk","First make it work. Then make it right. Then make it fast.","2026-11-14 13:36:16",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add sanjeevafk\u002Fagent-skills --skill generating-forensic-timelines-with-hayabusa",{"tool":56,"command":57},"bunx","bunx skills add sanjeevafk\u002Fagent-skills --skill generating-forensic-timelines-with-hayabusa",{"tool":59,"command":60},"pnpm","pnpm dlx skills add sanjeevafk\u002Fagent-skills --skill generating-forensic-timelines-with-hayabusa","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fgenerating-forensic-timelines-with-hayabusa\u002FSKILL.md",true,[64,68,74,78],{"path":65,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fapi-reference.md","REFERENCE","参考文档",2114,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fgenerating-forensic-timelines-with-hayabusa\u002Freferences\u002Fapi-reference.md",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fstandards.md",1962,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fgenerating-forensic-timelines-with-hayabusa\u002Freferences\u002Fstandards.md",{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"scripts\u002Fagent.py","SCRIPT","脚本",4584,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fgenerating-forensic-timelines-with-hayabusa\u002Fscripts\u002Fagent.py",[85,93,101,109,117,124],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":20},"01M7EFHX67M3KKXT1BXVPA5ADT","zarr-python","Chunked N-D arrays for cloud storage (Zarr-Python 3). Compressed arrays, parallel I\u002FO, S3\u002FGCS via fsspec, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","MIT","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":20},"01M7EFFQGM51TZBGRENXY50ZYM","whiteboard-diagrams","Create accurate, simple, hand-drawn whiteboard diagrams from a user's process, system, architecture, learning workflow, comparison, or causal explanation. Use when the user asks for a scribbly whiteboard visual, educational workflow graphic, hand-drawn explainer, or diagram like the bundled reference; ask one focused clarification question when the subject or relationships are missing, then generate and visually verify the final image.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwhiteboard-diagrams\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwhiteboard-diagrams\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":20},"01M7EFF1CSQNTDMHFK4ZGY6NYK","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":20},"01M7EFE8106X6C28FT8PA74427","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":20},"01M7EFCSNZM9G7ZHS6F127Q71X","verification-loop","A comprehensive verification system for Claude Code sessions.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":20},"01M7EFCE7EZMKPRYDDNKBQ9EEH","vercel-deploy","Deploy applications and websites to Vercel. Use when the user requests deployment actions like \"deploy my app\", \"deploy and give me the link\", \"push this live\", or \"create a preview deployment\".","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-deploy\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-deploy\u002FSKILL.md",[],[]]