[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ESR820P4DPZCXD4M03M6MQ":3,"skill-same:01M6ESR820P4DPZCXD4M03M6MQ":102},{"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":63,"commitSha":64,"skillDirectory":65,"forksCount":14,"repositoryHtmlUrl":66,"repositoryHomepageUrl":67,"ownerHtmlUrl":68,"ownerBlogUrl":6,"ownerDescription":69,"updatedAt":70,"install":71,"resources":84},"01M6ESR820P4DPZCXD4M03M6MQ","analyzing-ransomware-payment-wallets",null,"Traces ransomware cryptocurrency payment flows using blockchain analysis tools such as Chainalysis Reactor, WalletExplorer, and blockchain.com APIs. Identifies wallet clusters, tracks fund movement through mixers and exchanges, and supports law enforcement attribution. Activates for requests involving ransomware payment tracing, bitcoin wallet analysis, cryptocurrency forensics, or blockchain intelligence gathering.","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\u002Fanalyzing-ransomware-payment-wallets\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],"payment","analyzing","ransomware","analyzing ransomware payment wallets","flows","cybersecurity","as","intelligence","Wallet","enforcement","fund","analysis","defense","bitcoin","cryptocurrency","attribution","threat-intelligence","forensics","tracing","pr","2026-11-10 10:12:30",false,"---\nname: analyzing-ransomware-payment-wallets\ndescription: 'Traces ransomware cryptocurrency payment flows using blockchain analysis\n  tools such as Chainalysis Reactor, WalletExplorer, and blockchain.com APIs. Identifies\n  wallet clusters, tracks fund movement through mixers and exchanges, and supports\n  law enforcement attribution. Activates for requests involving ransomware payment\n  tracing, bitcoin wallet analysis, cryptocurrency forensics, or blockchain intelligence\n  gathering.\n\n  '\ndomain: cybersecurity\nsubdomain: ransomware-defense\ntags:\n- ransomware\n- blockchain\n- cryptocurrency\n- forensics\n- threat-intelligence\n- bitcoin\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- T1657\n- T1486\n---\n\n# Analyzing Ransomware Payment Wallets\n\n## When to Use\n\n- An organization has been hit by ransomware and the ransom note contains a Bitcoin or cryptocurrency wallet address that needs investigation\n- Law enforcement or incident responders need to trace where ransom payments flowed after the victim paid\n- Threat intelligence analysts are attributing ransomware campaigns by clustering payment infrastructure across incidents\n- Investigators need to determine if a ransomware group is reusing wallet infrastructure across multiple victims\n- Compliance or legal teams need evidence of fund flows for prosecution, sanctions enforcement, or insurance claims\n\n**Do not use** this skill for live payment interception or to interact directly with ransomware operators. All analysis should be passive and read-only against public blockchain data.\n\n## Prerequisites\n\n- Python 3.8+ with `requests`, `json`, and `hashlib` libraries\n- Access to blockchain explorer APIs (blockchain.com, WalletExplorer.com, Blockstream.info)\n- Familiarity with Bitcoin transaction model (UTXOs, inputs, outputs, change addresses)\n- Understanding of common obfuscation techniques (mixers, tumblers, peel chains, cross-chain swaps)\n- Optional: Chainalysis Reactor license for enterprise-grade cluster analysis\n- Optional: OXT.me for advanced transaction graph visualization\n\n## Workflow\n\n### Step 1: Extract Wallet Address from Ransom Note\n\nParse the ransom note to identify the payment address(es):\n\n```\nCommon address formats:\n  Bitcoin (P2PKH):   1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa  (starts with 1)\n  Bitcoin (P2SH):    3J98t1WpEZ73CNmQviecrnyiWrnqRhWNLy  (starts with 3)\n  Bitcoin (Bech32):  bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq (starts with bc1)\n  Monero:            4... (95 characters, much harder to trace)\n  Ethereum:          0x... (40 hex chars)\n```\n\n### Step 2: Query Blockchain Explorer for Transaction History\n\nRetrieve all transactions associated with the wallet:\n\n```python\nimport requests\n\ndef get_wallet_transactions(address):\n    \"\"\"Query blockchain.com API for address transactions.\"\"\"\n    url = f\"https:\u002F\u002Fblockchain.info\u002Frawaddr\u002F{address}\"\n    resp = requests.get(url, timeout=30)\n    resp.raise_for_status()\n    data = resp.json()\n    return {\n        \"address\": address,\n        \"n_tx\": data.get(\"n_tx\", 0),\n        \"total_received_satoshi\": data.get(\"total_received\", 0),\n        \"total_sent_satoshi\": data.get(\"total_sent\", 0),\n        \"final_balance_satoshi\": data.get(\"final_balance\", 0),\n        \"transactions\": data.get(\"txs\", []),\n    }\n```\n\n### Step 3: Map Fund Flow and Identify Clusters\n\nTrace outputs from the ransom wallet to downstream addresses:\n\n```\nFund Flow Analysis:\n━━━━━━━━━━━━━━━━━━\nVictim Payment ──► Ransom Wallet ──► Consolidation Wallet\n                                  ├─► Mixer\u002FTumbler Service\n                                  ├─► Exchange Deposit Address\n                                  └─► Peel Chain (sequential small outputs)\n\nKey indicators:\n  - Consolidation: Multiple ransom payments aggregated into one wallet\n  - Peel chains: Sequential transactions with diminishing outputs\n  - Mixer usage: Funds sent to known mixer addresses (Wasabi, Samourai, ChipMixer)\n  - Exchange cashout: Deposits to known exchange wallets (Binance, Kraken hot wallets)\n```\n\n### Step 4: Cross-Reference with Known Wallet Databases\n\nCheck addresses against known ransomware infrastructure:\n\n```python\n# Check WalletExplorer for entity identification\ndef check_wallet_explorer(address):\n    url = f\"https:\u002F\u002Fwww.walletexplorer.com\u002Fapi\u002F1\u002Faddress?address={address}&caller=research\"\n    resp = requests.get(url, timeout=30)\n    data = resp.json()\n    return {\n        \"wallet_id\": data.get(\"wallet_id\"),\n        \"label\": data.get(\"label\", \"Unknown\"),\n        \"is_exchange\": data.get(\"is_exchange\", False),\n    }\n```\n\n### Step 5: Generate Attribution Report\n\nCompile findings into a structured intelligence report:\n\n```\nRANSOMWARE WALLET ANALYSIS REPORT\n====================================\nRansom Address:      bc1q...xyz\nFamily Attribution:  LockBit 3.0 (based on ransom note format)\nTotal Received:      4.25 BTC ($178,500 at time of payment)\nTotal Sent:          4.25 BTC (wallet fully drained)\nNumber of Payments:  3 (likely 3 separate victims)\n\nFUND FLOW:\n  Payment 1: 1.5 BTC → Consolidation wallet → Binance deposit\n  Payment 2: 1.0 BTC → Wasabi Mixer → Unknown\n  Payment 3: 1.75 BTC → Peel chain (12 hops) → OKX deposit\n\nCLUSTER ANALYSIS:\n  Related wallets: 47 addresses identified in same cluster\n  Total cluster volume: 156.3 BTC ($6.5M USD)\n  First activity: 2024-01-15\n  Last activity: 2024-09-22\n```\n\n## Verification\n\n- Confirm wallet address format is valid before querying APIs\n- Cross-reference transaction timestamps with known incident timelines\n- Validate cluster associations by checking common-input-ownership heuristic\n- Compare findings against OFAC SDN list for sanctioned addresses\n- Verify exchange attribution against multiple sources (WalletExplorer, OXT, Chainalysis)\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| **UTXO** | Unspent Transaction Output; the fundamental unit of Bitcoin that tracks ownership through a chain of transactions |\n| **Cluster Analysis** | Grouping multiple Bitcoin addresses believed to be controlled by the same entity using common-input-ownership and change-address heuristics |\n| **Peel Chain** | A laundering pattern where funds are sent through many sequential transactions, each peeling off a small amount to a new address |\n| **CoinJoin\u002FMixer** | Privacy techniques that combine multiple users' transactions to obscure the link between sender and receiver |\n| **Common Input Ownership** | Heuristic that assumes all inputs to a single transaction are controlled by the same entity |\n\n## Tools & Systems\n\n- **Chainalysis Reactor**: Enterprise blockchain investigation platform with entity attribution and cross-chain tracing\n- **WalletExplorer**: Free tool that clusters Bitcoin addresses and labels known services (exchanges, mixers, markets)\n- **OXT.me**: Advanced Bitcoin transaction visualization with UTXO graph analysis\n- **Blockstream.info**: Open-source Bitcoin block explorer with full API access\n- **blockchain.com API**: Free API for querying Bitcoin address balances and transaction histories\n- **OFAC SDN List**: U.S. Treasury sanctioned address list for compliance checking\n","# Analyzing Ransomware Payment Wallets\n\n## When to Use\n\n- An organization has been hit by ransomware and the ransom note contains a Bitcoin or cryptocurrency wallet address that needs investigation\n- Law enforcement or incident responders need to trace where ransom payments flowed after the victim paid\n- Threat intelligence analysts are attributing ransomware campaigns by clustering payment infrastructure across incidents\n- Investigators need to determine if a ransomware group is reusing wallet infrastructure across multiple victims\n- Compliance or legal teams need evidence of fund flows for prosecution, sanctions enforcement, or insurance claims\n\n**Do not use** this skill for live payment interception or to interact directly with ransomware operators. All analysis should be passive and read-only against public blockchain data.\n\n## Prerequisites\n\n- Python 3.8+ with `requests`, `json`, and `hashlib` libraries\n- Access to blockchain explorer APIs (blockchain.com, WalletExplorer.com, Blockstream.info)\n- Familiarity with Bitcoin transaction model (UTXOs, inputs, outputs, change addresses)\n- Understanding of common obfuscation techniques (mixers, tumblers, peel chains, cross-chain swaps)\n- Optional: Chainalysis Reactor license for enterprise-grade cluster analysis\n- Optional: OXT.me for advanced transaction graph visualization\n\n## Workflow\n\n### Step 1: Extract Wallet Address from Ransom Note\n\nParse the ransom note to identify the payment address(es):\n\n```\nCommon address formats:\n  Bitcoin (P2PKH):   1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa  (starts with 1)\n  Bitcoin (P2SH):    3J98t1WpEZ73CNmQviecrnyiWrnqRhWNLy  (starts with 3)\n  Bitcoin (Bech32):  bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq (starts with bc1)\n  Monero:            4... (95 characters, much harder to trace)\n  Ethereum:          0x... (40 hex chars)\n```\n\n### Step 2: Query Blockchain Explorer for Transaction History\n\nRetrieve all transactions associated with the wallet:\n\n```python\nimport requests\n\ndef get_wallet_transactions(address):\n    \"\"\"Query blockchain.com API for address transactions.\"\"\"\n    url = f\"https:\u002F\u002Fblockchain.info\u002Frawaddr\u002F{address}\"\n    resp = requests.get(url, timeout=30)\n    resp.raise_for_status()\n    data = resp.json()\n    return {\n        \"address\": address,\n        \"n_tx\": data.get(\"n_tx\", 0),\n        \"total_received_satoshi\": data.get(\"total_received\", 0),\n        \"total_sent_satoshi\": data.get(\"total_sent\", 0),\n        \"final_balance_satoshi\": data.get(\"final_balance\", 0),\n        \"transactions\": data.get(\"txs\", []),\n    }\n```\n\n### Step 3: Map Fund Flow and Identify Clusters\n\nTrace outputs from the ransom wallet to downstream addresses:\n\n```\nFund Flow Analysis:\n━━━━━━━━━━━━━━━━━━\nVictim Payment ──► Ransom Wallet ──► Consolidation Wallet\n                                  ├─► Mixer\u002FTumbler Service\n                                  ├─► Exchange Deposit Address\n                                  └─► Peel Chain (sequential small outputs)\n\nKey indicators:\n  - Consolidation: Multiple ransom payments aggregated into one wallet\n  - Peel chains: Sequential transactions with diminishing outputs\n  - Mixer usage: Funds sent to known mixer addresses (Wasabi, Samourai, ChipMixer)\n  - Exchange cashout: Deposits to known exchange wallets (Binance, Kraken hot wallets)\n```\n\n### Step 4: Cross-Reference with Known Wallet Databases\n\nCheck addresses against known ransomware infrastructure:\n\n```python\n# Check WalletExplorer for entity identification\ndef check_wallet_explorer(address):\n    url = f\"https:\u002F\u002Fwww.walletexplorer.com\u002Fapi\u002F1\u002Faddress?address={address}&caller=research\"\n    resp = requests.get(url, timeout=30)\n    data = resp.json()\n    return {\n        \"wallet_id\": data.get(\"wallet_id\"),\n        \"label\": data.get(\"label\", \"Unknown\"),\n        \"is_exchange\": data.get(\"is_exchange\", False),\n    }\n```\n\n### Step 5: Generate Attribution Report\n\nCompile findings into a structured intelligence report:\n\n```\nRANSOMWARE WALLET ANALYSIS REPORT\n====================================\nRansom Address:      bc1q...xyz\nFamily Attribution:  LockBit 3.0 (based on ransom note format)\nTotal Received:      4.25 BTC ($178,500 at time of payment)\nTotal Sent:          4.25 BTC (wallet fully drained)\nNumber of Payments:  3 (likely 3 separate victims)\n\nFUND FLOW:\n  Payment 1: 1.5 BTC → Consolidation wallet → Binance deposit\n  Payment 2: 1.0 BTC → Wasabi Mixer → Unknown\n  Payment 3: 1.75 BTC → Peel chain (12 hops) → OKX deposit\n\nCLUSTER ANALYSIS:\n  Related wallets: 47 addresses identified in same cluster\n  Total cluster volume: 156.3 BTC ($6.5M USD)\n  First activity: 2024-01-15\n  Last activity: 2024-09-22\n```\n\n## Verification\n\n- Confirm wallet address format is valid before querying APIs\n- Cross-reference transaction timestamps with known incident timelines\n- Validate cluster associations by checking common-input-ownership heuristic\n- Compare findings against OFAC SDN list for sanctioned addresses\n- Verify exchange attribution against multiple sources (WalletExplorer, OXT, Chainalysis)\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| **UTXO** | Unspent Transaction Output; the fundamental unit of Bitcoin that tracks ownership through a chain of transactions |\n| **Cluster Analysis** | Grouping multiple Bitcoin addresses believed to be controlled by the same entity using common-input-ownership and change-address heuristics |\n| **Peel Chain** | A laundering pattern where funds are sent through many sequential transactions, each peeling off a small amount to a new address |\n| **CoinJoin\u002FMixer** | Privacy techniques that combine multiple users' transactions to obscure the link between sender and receiver |\n| **Common Input Ownership** | Heuristic that assumes all inputs to a single transaction are controlled by the same entity |\n\n## Tools & Systems\n\n- **Chainalysis Reactor**: Enterprise blockchain investigation platform with entity attribution and cross-chain tracing\n- **WalletExplorer**: Free tool that clusters Bitcoin addresses and labels known services (exchanges, mixers, markets)\n- **OXT.me**: Advanced Bitcoin transaction visualization with UTXO graph analysis\n- **Blockstream.info**: Open-source Bitcoin block explorer with full API access\n- **blockchain.com API**: Free API for querying Bitcoin address balances and transaction histories\n- **OFAC SDN List**: U.S. Treasury sanctioned address list for compliance checking\n",{"name":5,"tags":49,"author":51,"domain":29,"license":15,"version":52,"nist_csf":53,"subdomain":58,"description":59,"mitre_attack":60},[26,50,38,41,40,37],"blockchain","mahipal","1.0.0",[54,55,56,57],"PR.DS-11","RS.MA-01","RC.RP-01","PR.IR-01","ransomware-defense","Traces ransomware cryptocurrency payment flows using blockchain analysis tools such as Chainalysis Reactor, WalletExplorer, and blockchain.com APIs. Identifies wallet clusters, tracks fund movement through mixers and exchanges, and supports law enforcement attribution. Activates for requests involving ransomware payment tracing, bitcoin wallet analysis, cryptocurrency forensics, or blockchain intelligence gathering.\n",[61,62],"T1657","T1486","main","7925716f065257435fdb12e97f7e52842147d5ad",".claude\u002Fskills\u002Fanalyzing-ransomware-payment-wallets","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":72,"prompt":82,"zipAvailable":83},[73,76,79],{"tool":74,"command":75},"npx","npx skills add henriquescastilho\u002Fmy-claude --skill analyzing-ransomware-payment-wallets",{"tool":77,"command":78},"bunx","bunx skills add henriquescastilho\u002Fmy-claude --skill analyzing-ransomware-payment-wallets",{"tool":80,"command":81},"pnpm","pnpm dlx skills add henriquescastilho\u002Fmy-claude --skill analyzing-ransomware-payment-wallets","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fanalyzing-ransomware-payment-wallets\u002FSKILL.md",true,[85,90,96],{"path":86,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fanalyzing-ransomware-payment-wallets\u002FLICENSE",{"path":91,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fapi-reference.md","REFERENCE","参考文档",3058,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fanalyzing-ransomware-payment-wallets\u002Freferences\u002Fapi-reference.md",{"path":97,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":100,"sourceHtmlUrl":101},"scripts\u002Fagent.py","SCRIPT","脚本",7968,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fanalyzing-ransomware-payment-wallets\u002Fscripts\u002Fagent.py",[103,144,153,162,184,209],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":107,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":124,"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",[110,113,116,119],{"categoryNo":111,"categoryName":112,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":114,"categoryName":115,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":117,"categoryName":118,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000004","电子表格",{"categoryNo":120,"categoryName":121,"taxonomyType":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[105,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143],"docx","PDF","pptx","xlsx","documents","csv","ocr","Audio","Bash","markdown","convert","read","write","edit","html","images","files","youtube","with",{"skillNo":145,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":107,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":152,"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",[148,149,150,151],{"categoryNo":111,"categoryName":112,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":114,"categoryName":115,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":117,"categoryName":118,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":120,"categoryName":121,"taxonomyType":122,"taxonomyTypeDesc":123},[105,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143],{"skillNo":154,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":107,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":161,"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",[157,158,159,160],{"categoryNo":111,"categoryName":112,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":114,"categoryName":115,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":117,"categoryName":118,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":120,"categoryName":121,"taxonomyType":122,"taxonomyTypeDesc":123},[105,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143],{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":107,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":168,"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",[],[169,170,171,172,173,174,175,176,177,178,179,180,181,182,183],"python","zarr python","storage","integration","s3","gcs","cloud","dask","parallel","pipelines","arrays","numpy","scientific computing","scale","scientific",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":107,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":191,"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",[190],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[192,193,194,195,196,197,35,198,199,200,201,136,137,202,203,204,205,206,207,208],"oracle","what if oracle","go","run","ux","futures","explore","decision","branch","question","idea","exploration","options","stress-test","strategies","scenario","stress",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":107,"licenseFileUrl":6,"sourceHtmlUrl":213,"categories":214,"keywords":225,"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",[215,218,221,222],{"categoryNo":216,"categoryName":217,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":219,"categoryName":220,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":223,"categoryName":224,"taxonomyType":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000036","内容创作者",[226,227,228,229,230,231,232,233,133,234,136,137,138,235,236,237,238,239,183,240],"templates","venue templates","research","guidelines","NeurIPS","ICML","LaTeX","science","access","proposals","Academic","requirements","formatting","journal","chi"]