[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ET78WFW6DSF2RH0DNZ8AS9":3,"skill-same:01M6ET78WFW6DSF2RH0DNZ8AS9":105},{"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":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":66,"commitSha":67,"skillDirectory":68,"forksCount":14,"repositoryHtmlUrl":69,"repositoryHomepageUrl":70,"ownerHtmlUrl":71,"ownerBlogUrl":6,"ownerDescription":72,"updatedAt":73,"install":74,"resources":87},"01M6ET78WFW6DSF2RH0DNZ8AS9","deploying-decoy-files-for-ransomware-detection",null,"Deploys canary files (honeytokens) across file systems to detect ransomware encryption activity in real time. Uses strategically placed decoy documents monitored via file integrity monitoring or OS-level watchdogs to trigger alerts when ransomware modifies or encrypts them. Activates for requests involving ransomware canary deployment, honeyfile setup, deception-based ransomware detection, or file integrity monitoring for encryption.","henriquescastilho\u002Fmy-claude","henriquescastilho","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F153296945?v=4","01M6ESH7EXPXTH9CVQ4K16SRG8","Henrique Scheer","01M6ESH7JHEK2PTNNH4HEH787Z",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdeploying-decoy-files-for-ransomware-detection\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"ransomware","detection","deploying decoy files for ransomware detection","files","t1490","activity","os","alerts","across","time","canary deployment","canary","integrity","cybersecurity","defense","file-integrity","canary-files","encryption","monitoring","documents","2026-11-10 10:12:30",false,"---\nname: deploying-decoy-files-for-ransomware-detection\ndescription: 'Deploys canary files (honeytokens) across file systems to detect ransomware\n  encryption activity in real time. Uses strategically placed decoy documents monitored\n  via file integrity monitoring or OS-level watchdogs to trigger alerts when ransomware\n  modifies or encrypts them. Activates for requests involving ransomware canary deployment,\n  honeyfile setup, deception-based ransomware detection, or file integrity monitoring\n  for encryption.\n\n  '\ndomain: cybersecurity\nsubdomain: ransomware-defense\ntags:\n- ransomware\n- detection\n- canary-files\n- honeytokens\n- deception\n- file-integrity\nversion: 1.0.0\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.DS-11\n- RS.MA-01\n- RC.RP-01\n- PR.IR-01\nmitre_attack:\n- T1486\n- T1083\n- T1490\n- T1485\n---\n\n# Deploying Decoy Files for Ransomware Detection\n\n## When to Use\n\n- Setting up early-warning detection for ransomware on file servers or endpoints\n- Supplementing EDR\u002FAV with a deception-based detection layer that catches unknown ransomware variants\n- Creating high-fidelity ransomware alerts that have very low false-positive rates (legitimate users have no reason to touch decoy files)\n- Testing ransomware response procedures by validating that canary file modifications trigger the expected alerting pipeline\n- Protecting high-value file shares (finance, HR, legal) with tripwire files that indicate unauthorized encryption activity\n\n**Do not use** decoy files as the sole ransomware defense. They are a detection mechanism, not a prevention mechanism, and should complement backups, EDR, and access controls.\n\n## Prerequisites\n\n- Python 3.8+ with `watchdog` library for cross-platform file system monitoring\n- Administrative access to target file shares or endpoints for canary placement\n- File integrity monitoring (FIM) tool or SIEM integration for alert routing\n- Understanding of target directory structure to place canaries in high-value locations\n- Windows: NTFS change journal or ReadDirectoryChangesW API access\n- Linux: inotify support in kernel (standard in modern kernels)\n\n## Workflow\n\n### Step 1: Design Canary File Strategy\n\nPlan file placement for maximum detection coverage:\n\n```\nCanary File Placement Strategy:\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nNaming Convention:\n  - Use names that sort FIRST and LAST alphabetically in each directory\n  - Ransomware typically enumerates directories A-Z or Z-A\n  - Examples: _AAAA_budget_2024.docx, ~zzzz_report_final.xlsx\n\nPlacement Locations:\n  - Root of every file share (\\\\server\\share\\_AAAA_canary.docx)\n  - Desktop, Documents, Downloads on each endpoint\n  - Department-specific shares (Finance, HR, Legal)\n  - Backup staging directories\n  - Home directories of high-privilege accounts\n\nFile Types:\n  - .docx, .xlsx, .pdf (most targeted by ransomware)\n  - .sql, .bak (database files, high value)\n  - Mix of file types to detect ransomware that targets specific extensions\n```\n\n### Step 2: Generate Realistic Canary Files\n\nCreate decoy files with realistic content and metadata:\n\n```python\nimport os\nimport time\n\ndef create_canary_docx(filepath, content=\"Q4 Financial Summary - Confidential\"):\n    \"\"\"Create a realistic .docx canary file using python-docx.\"\"\"\n    from docx import Document\n    doc = Document()\n    doc.add_heading(\"Financial Report - CONFIDENTIAL\", level=1)\n    doc.add_paragraph(content)\n    doc.add_paragraph(f\"Generated: {time.strftime('%Y-%m-%d')}\")\n    doc.save(filepath)\n\ndef create_canary_txt(filepath):\n    \"\"\"Create a simple text canary with known content for hash verification.\"\"\"\n    content = \"CANARY_TOKEN_DO_NOT_MODIFY\\n\"\n    content += f\"Created: {time.strftime('%Y-%m-%dT%H:%M:%S')}\\n\"\n    content += \"This file is monitored for unauthorized changes.\\n\"\n    with open(filepath, \"w\") as f:\n        f.write(content)\n```\n\n### Step 3: Deploy File System Watcher\n\nMonitor canary files for any modification, rename, or deletion:\n\n```python\nfrom watchdog.observers import Observer\nfrom watchdog.events import FileSystemEventHandler\n\nclass CanaryHandler(FileSystemEventHandler):\n    def __init__(self, canary_paths, alert_callback):\n        self.canary_paths = set(canary_paths)\n        self.alert_callback = alert_callback\n\n    def on_modified(self, event):\n        if event.src_path in self.canary_paths:\n            self.alert_callback(\"MODIFIED\", event.src_path)\n\n    def on_deleted(self, event):\n        if event.src_path in self.canary_paths:\n            self.alert_callback(\"DELETED\", event.src_path)\n\n    def on_moved(self, event):\n        if event.src_path in self.canary_paths:\n            self.alert_callback(\"RENAMED\", event.src_path)\n```\n\n### Step 4: Configure Alerting and Response\n\nDefine automated responses when canary files are triggered:\n\n```\nAlert Response Matrix:\n━━━━━━━━━━━━━━━━━━━━━\nEvent: Canary MODIFIED\n  → Severity: CRITICAL\n  → Action: Alert SOC, identify modifying process (PID), isolate endpoint\n\nEvent: Canary DELETED\n  → Severity: HIGH\n  → Action: Alert SOC, check for ransomware note in same directory\n\nEvent: Canary RENAMED (new extension added)\n  → Severity: CRITICAL\n  → Action: Alert SOC, check extension against known ransomware extensions\n  → Automated: Kill modifying process, disable network interface\n\nEvent: Multiple canaries triggered within 60 seconds\n  → Severity: EMERGENCY\n  → Action: Network-wide isolation, activate incident response plan\n```\n\n### Step 5: Validate Detection Coverage\n\nTest that canary files detect actual ransomware behavior:\n\n```bash\n# Simulate ransomware encryption (safe test - modifies canary content)\necho \"ENCRYPTED_BY_TEST\" > \u002Fpath\u002Fto\u002Fcanary\u002F_AAAA_budget.docx\n\n# Simulate ransomware rename (adds extension)\nmv \u002Fpath\u002Fto\u002Fcanary\u002Freport.xlsx \u002Fpath\u002Fto\u002Fcanary\u002Freport.xlsx.locked\n\n# Verify alerts were generated in SIEM\u002Falerting system\n```\n\n## Verification\n\n- Confirm all canary files are present and unmodified using stored hash baselines\n- Verify that modifying any canary file generates an alert within the expected timeframe (under 30 seconds)\n- Test that alert routing to SOC\u002FSIEM is functional with a controlled modification\n- Validate that automated response actions (process kill, network isolation) execute correctly\n- Check that canary files survive normal backup and restore operations\n- Ensure legitimate users and processes are excluded from false-positive alerts (backup agents, AV scans)\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| **Canary File** | A decoy file placed in a directory that is monitored for any access or modification, serving as a tripwire for unauthorized activity |\n| **Honeytoken** | A broader category of deception artifacts (files, credentials, database records) designed to alert when accessed |\n| **File Integrity Monitoring** | Continuous monitoring of file attributes (hash, size, permissions, timestamps) to detect unauthorized changes |\n| **ReadDirectoryChangesW** | Windows API for monitoring file system changes in a directory; used by the watchdog library on Windows |\n| **inotify** | Linux kernel subsystem for monitoring file system events; provides near-instant notification of file changes |\n\n## Tools & Systems\n\n- **watchdog (Python)**: Cross-platform file system event monitoring library supporting Windows, Linux, and macOS\n- **Canarytokens (Thinkst)**: Free hosted service for generating various types of canary tokens including files, URLs, and DNS tokens\n- **OSSEC\u002FWazuh**: Open-source HIDS with built-in file integrity monitoring and alerting capabilities\n- **Elastic Endpoint**: Uses canary files internally for ransomware protection and key capture\n- **Sysmon**: Windows system monitor that logs file creation events (Event ID 11) for canary file monitoring\n","# Deploying Decoy Files for Ransomware Detection\n\n## When to Use\n\n- Setting up early-warning detection for ransomware on file servers or endpoints\n- Supplementing EDR\u002FAV with a deception-based detection layer that catches unknown ransomware variants\n- Creating high-fidelity ransomware alerts that have very low false-positive rates (legitimate users have no reason to touch decoy files)\n- Testing ransomware response procedures by validating that canary file modifications trigger the expected alerting pipeline\n- Protecting high-value file shares (finance, HR, legal) with tripwire files that indicate unauthorized encryption activity\n\n**Do not use** decoy files as the sole ransomware defense. They are a detection mechanism, not a prevention mechanism, and should complement backups, EDR, and access controls.\n\n## Prerequisites\n\n- Python 3.8+ with `watchdog` library for cross-platform file system monitoring\n- Administrative access to target file shares or endpoints for canary placement\n- File integrity monitoring (FIM) tool or SIEM integration for alert routing\n- Understanding of target directory structure to place canaries in high-value locations\n- Windows: NTFS change journal or ReadDirectoryChangesW API access\n- Linux: inotify support in kernel (standard in modern kernels)\n\n## Workflow\n\n### Step 1: Design Canary File Strategy\n\nPlan file placement for maximum detection coverage:\n\n```\nCanary File Placement Strategy:\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nNaming Convention:\n  - Use names that sort FIRST and LAST alphabetically in each directory\n  - Ransomware typically enumerates directories A-Z or Z-A\n  - Examples: _AAAA_budget_2024.docx, ~zzzz_report_final.xlsx\n\nPlacement Locations:\n  - Root of every file share (\\\\server\\share\\_AAAA_canary.docx)\n  - Desktop, Documents, Downloads on each endpoint\n  - Department-specific shares (Finance, HR, Legal)\n  - Backup staging directories\n  - Home directories of high-privilege accounts\n\nFile Types:\n  - .docx, .xlsx, .pdf (most targeted by ransomware)\n  - .sql, .bak (database files, high value)\n  - Mix of file types to detect ransomware that targets specific extensions\n```\n\n### Step 2: Generate Realistic Canary Files\n\nCreate decoy files with realistic content and metadata:\n\n```python\nimport os\nimport time\n\ndef create_canary_docx(filepath, content=\"Q4 Financial Summary - Confidential\"):\n    \"\"\"Create a realistic .docx canary file using python-docx.\"\"\"\n    from docx import Document\n    doc = Document()\n    doc.add_heading(\"Financial Report - CONFIDENTIAL\", level=1)\n    doc.add_paragraph(content)\n    doc.add_paragraph(f\"Generated: {time.strftime('%Y-%m-%d')}\")\n    doc.save(filepath)\n\ndef create_canary_txt(filepath):\n    \"\"\"Create a simple text canary with known content for hash verification.\"\"\"\n    content = \"CANARY_TOKEN_DO_NOT_MODIFY\\n\"\n    content += f\"Created: {time.strftime('%Y-%m-%dT%H:%M:%S')}\\n\"\n    content += \"This file is monitored for unauthorized changes.\\n\"\n    with open(filepath, \"w\") as f:\n        f.write(content)\n```\n\n### Step 3: Deploy File System Watcher\n\nMonitor canary files for any modification, rename, or deletion:\n\n```python\nfrom watchdog.observers import Observer\nfrom watchdog.events import FileSystemEventHandler\n\nclass CanaryHandler(FileSystemEventHandler):\n    def __init__(self, canary_paths, alert_callback):\n        self.canary_paths = set(canary_paths)\n        self.alert_callback = alert_callback\n\n    def on_modified(self, event):\n        if event.src_path in self.canary_paths:\n            self.alert_callback(\"MODIFIED\", event.src_path)\n\n    def on_deleted(self, event):\n        if event.src_path in self.canary_paths:\n            self.alert_callback(\"DELETED\", event.src_path)\n\n    def on_moved(self, event):\n        if event.src_path in self.canary_paths:\n            self.alert_callback(\"RENAMED\", event.src_path)\n```\n\n### Step 4: Configure Alerting and Response\n\nDefine automated responses when canary files are triggered:\n\n```\nAlert Response Matrix:\n━━━━━━━━━━━━━━━━━━━━━\nEvent: Canary MODIFIED\n  → Severity: CRITICAL\n  → Action: Alert SOC, identify modifying process (PID), isolate endpoint\n\nEvent: Canary DELETED\n  → Severity: HIGH\n  → Action: Alert SOC, check for ransomware note in same directory\n\nEvent: Canary RENAMED (new extension added)\n  → Severity: CRITICAL\n  → Action: Alert SOC, check extension against known ransomware extensions\n  → Automated: Kill modifying process, disable network interface\n\nEvent: Multiple canaries triggered within 60 seconds\n  → Severity: EMERGENCY\n  → Action: Network-wide isolation, activate incident response plan\n```\n\n### Step 5: Validate Detection Coverage\n\nTest that canary files detect actual ransomware behavior:\n\n```bash\n# Simulate ransomware encryption (safe test - modifies canary content)\necho \"ENCRYPTED_BY_TEST\" > \u002Fpath\u002Fto\u002Fcanary\u002F_AAAA_budget.docx\n\n# Simulate ransomware rename (adds extension)\nmv \u002Fpath\u002Fto\u002Fcanary\u002Freport.xlsx \u002Fpath\u002Fto\u002Fcanary\u002Freport.xlsx.locked\n\n# Verify alerts were generated in SIEM\u002Falerting system\n```\n\n## Verification\n\n- Confirm all canary files are present and unmodified using stored hash baselines\n- Verify that modifying any canary file generates an alert within the expected timeframe (under 30 seconds)\n- Test that alert routing to SOC\u002FSIEM is functional with a controlled modification\n- Validate that automated response actions (process kill, network isolation) execute correctly\n- Check that canary files survive normal backup and restore operations\n- Ensure legitimate users and processes are excluded from false-positive alerts (backup agents, AV scans)\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| **Canary File** | A decoy file placed in a directory that is monitored for any access or modification, serving as a tripwire for unauthorized activity |\n| **Honeytoken** | A broader category of deception artifacts (files, credentials, database records) designed to alert when accessed |\n| **File Integrity Monitoring** | Continuous monitoring of file attributes (hash, size, permissions, timestamps) to detect unauthorized changes |\n| **ReadDirectoryChangesW** | Windows API for monitoring file system changes in a directory; used by the watchdog library on Windows |\n| **inotify** | Linux kernel subsystem for monitoring file system events; provides near-instant notification of file changes |\n\n## Tools & Systems\n\n- **watchdog (Python)**: Cross-platform file system event monitoring library supporting Windows, Linux, and macOS\n- **Canarytokens (Thinkst)**: Free hosted service for generating various types of canary tokens including files, URLs, and DNS tokens\n- **OSSEC\u002FWazuh**: Open-source HIDS with built-in file integrity monitoring and alerting capabilities\n- **Elastic Endpoint**: Uses canary files internally for ransomware protection and key capture\n- **Sysmon**: Windows system monitor that logs file creation events (Event ID 11) for canary file monitoring\n",{"name":5,"tags":49,"author":52,"domain":37,"license":15,"version":53,"nist_csf":54,"subdomain":59,"description":60,"mitre_attack":61},[24,25,40,50,51,39],"honeytokens","deception","mahipal","1.0.0",[55,56,57,58],"PR.DS-11","RS.MA-01","RC.RP-01","PR.IR-01","ransomware-defense","Deploys canary files (honeytokens) across file systems to detect ransomware encryption activity in real time. Uses strategically placed decoy documents monitored via file integrity monitoring or OS-level watchdogs to trigger alerts when ransomware modifies or encrypts them. Activates for requests involving ransomware canary deployment, honeyfile setup, deception-based ransomware detection, or file integrity monitoring for encryption.\n",[62,63,64,65],"T1486","T1083","T1490","T1485","main","7925716f065257435fdb12e97f7e52842147d5ad",".claude\u002Fskills\u002Fdeploying-decoy-files-for-ransomware-detection","https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude","https:\u002F\u002Fclaude.com\u002Fclaude-code","https:\u002F\u002Fgithub.com\u002Fhenriquescastilho","Software · Applied AI · Quantitative Modeling · Building with Claude.","2026-06-10 12:24:46",{"source":8,"skillName":5,"commands":75,"prompt":85,"zipAvailable":86},[76,79,82],{"tool":77,"command":78},"npx","npx skills add henriquescastilho\u002Fmy-claude --skill deploying-decoy-files-for-ransomware-detection",{"tool":80,"command":81},"bunx","bunx skills add henriquescastilho\u002Fmy-claude --skill deploying-decoy-files-for-ransomware-detection",{"tool":83,"command":84},"pnpm","pnpm dlx skills add henriquescastilho\u002Fmy-claude --skill deploying-decoy-files-for-ransomware-detection","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdeploying-decoy-files-for-ransomware-detection\u002FSKILL.md",true,[88,93,99],{"path":89,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdeploying-decoy-files-for-ransomware-detection\u002FLICENSE",{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fapi-reference.md","REFERENCE","参考文档",3201,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdeploying-decoy-files-for-ransomware-detection\u002Freferences\u002Fapi-reference.md",{"path":100,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":103,"sourceHtmlUrl":104},"scripts\u002Fagent.py","SCRIPT","脚本",9424,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdeploying-decoy-files-for-ransomware-detection\u002Fscripts\u002Fagent.py",[106,145,154,163,185,211],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":110,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":127,"publishedAt":44},"01M6F0B6XPQ65AX2X0DWK8KT3E","markitdown","Convert files and office documents to Markdown. Supports PDF, DOCX, PPTX, XLSX, images (with OCR), audio (with transcription), HTML, CSV, JSON, XML, ZIP, YouTube URLs, EPubs and more.","MIT","https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.codex\u002Fvendor_imports\u002Fclaude\u002Fmarketplaces\u002Fclaude-scientific-writer\u002Fskills\u002Fmarkitdown\u002FSKILL.md",[113,116,119,122],{"categoryNo":114,"categoryName":115,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":117,"categoryName":118,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":120,"categoryName":121,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000004","电子表格",{"categoryNo":123,"categoryName":124,"taxonomyType":125,"taxonomyTypeDesc":126},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[108,128,129,130,131,43,132,133,134,135,136,137,138,139,140,141,142,27,143,144],"docx","PDF","pptx","xlsx","csv","ocr","Audio","Bash","markdown","convert","read","write","edit","html","images","youtube","with",{"skillNo":146,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":110,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":153,"publishedAt":44},"01M6F06SBHR9F0SDWE282Y8075","https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.codex\u002Fvendor_imports\u002Fclaude\u002Fmarketplaces\u002Fclaude-scientific-writer\u002Fscientific_writer\u002F.claude\u002Fskills\u002Fmarkitdown\u002FSKILL.md",[149,150,151,152],{"categoryNo":114,"categoryName":115,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":117,"categoryName":118,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":120,"categoryName":121,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":123,"categoryName":124,"taxonomyType":125,"taxonomyTypeDesc":126},[108,128,129,130,131,43,132,133,134,135,136,137,138,139,140,141,142,27,143,144],{"skillNo":155,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":110,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":162,"publishedAt":44},"01M6F02D4R14EJAPBWVDF9J9VQ","https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.codex\u002Fvendor_imports\u002Fclaude\u002Fmarketplaces\u002Fclaude-scientific-writer\u002F.claude\u002Fskills\u002Fmarkitdown\u002FSKILL.md",[158,159,160,161],{"categoryNo":114,"categoryName":115,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":117,"categoryName":118,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":120,"categoryName":121,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":123,"categoryName":124,"taxonomyType":125,"taxonomyTypeDesc":126},[108,128,129,130,131,43,132,133,134,135,136,137,138,139,140,141,142,27,143,144],{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":110,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":44},"01M6F000KS6YB4MKS774G4R8ND","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.codex\u002Fvendor_imports\u002Fclaude\u002Fmarketplaces\u002Fclaude-scientific-skills\u002Fscientific-skills\u002Fzarr-python\u002FSKILL.md",[],[170,171,172,173,174,175,176,177,178,179,180,181,182,183,184],"python","zarr python","storage","integration","s3","gcs","cloud","dask","parallel","pipelines","arrays","numpy","scientific computing","scale","scientific",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":110,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":192,"publishedAt":44},"01M6EZZJWFXM1GR78KTW6J0DN8","what-if-oracle","Run structured What-If scenario analysis with multi-branch possibility exploration. Use this skill when the user asks speculative questions like \"what if...\", \"what would happen if...\", \"what are the possibilities\", \"explore scenarios\", \"scenario analysis\", \"possibility space\", \"what could go wrong\", \"best case \u002F worst case\", \"risk analysis\", \"contingency planning\", \"strategic options\", or any question about uncertain futures. Also trigger when the user faces a fork-in-the-road decision, wants to stress-test an idea, or needs to think through consequences before committing.","https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.codex\u002Fvendor_imports\u002Fclaude\u002Fmarketplaces\u002Fclaude-scientific-skills\u002Fscientific-skills\u002Fwhat-if-oracle\u002FSKILL.md",[191],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[193,194,195,196,197,198,199,200,201,202,203,138,139,204,205,206,207,208,209,210],"oracle","what if oracle","go","run","ux","futures","analysis","explore","decision","branch","question","idea","exploration","options","stress-test","strategies","scenario","stress",{"skillNo":212,"name":213,"nameZh":6,"description":214,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":110,"licenseFileUrl":6,"sourceHtmlUrl":215,"categories":216,"keywords":227,"publishedAt":44},"01M6EZZCXAEB49RXGQCJX5E8GB","venue-templates","Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.","https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.codex\u002Fvendor_imports\u002Fclaude\u002Fmarketplaces\u002Fclaude-scientific-skills\u002Fscientific-skills\u002Fvenue-templates\u002FSKILL.md",[217,220,223,224],{"categoryNo":218,"categoryName":219,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":221,"categoryName":222,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":225,"categoryName":226,"taxonomyType":125,"taxonomyTypeDesc":126},"01JBSEEDCAT000000000000036","内容创作者",[228,229,230,231,232,233,234,235,135,236,138,139,140,237,238,239,240,241,184,242],"templates","venue templates","research","guidelines","NeurIPS","ICML","LaTeX","science","access","proposals","Academic","requirements","formatting","journal","chi"]