[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EVS9AS4BRCX49AXJWCFW3M":3,"skill-same:01M6EVS9AS4BRCX49AXJWCFW3M":125},{"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":26,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":68,"commitSha":69,"skillDirectory":70,"forksCount":14,"repositoryHtmlUrl":71,"repositoryHomepageUrl":72,"ownerHtmlUrl":73,"ownerBlogUrl":6,"ownerDescription":74,"updatedAt":75,"install":76,"resources":89},"01M6EVS9AS4BRCX49AXJWCFW3M","performing-dmarc-policy-enforcement-rollout",null,"Execute a phased DMARC rollout from p=none monitoring through p=quarantine to p=reject enforcement, ensuring all legitimate email sources are authenticated before blocking unauthorized senders.","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\u002Fperforming-dmarc-policy-enforcement-rollout\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"enforcement","policy enforcement","rollout","performing dmarc policy enforcement rollout","dmarc","policy","t1566","sources","de","cm","email-authentication","anti-spoofing","email-security","dns","phishing","email","monitoring","authentication","pr","cybersecurity","2026-11-10 10:12:30",false,"---\nname: performing-dmarc-policy-enforcement-rollout\ndescription: Execute a phased DMARC rollout from p=none monitoring through p=quarantine\n  to p=reject enforcement, ensuring all legitimate email sources are authenticated\n  before blocking unauthorized senders.\ndomain: cybersecurity\nsubdomain: phishing-defense\ntags:\n- dmarc\n- spf\n- dkim\n- email-authentication\n- anti-spoofing\n- phishing\n- dns\n- email-security\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.AT-01\n- DE.CM-09\n- RS.CO-02\n- DE.AE-02\nmitre_attack:\n- T1566\n- T1598\n- T1534\n- T1036\n---\n# Performing DMARC Policy Enforcement Rollout\n\n## Overview\nDomain-based Message Authentication, Reporting and Conformance (DMARC) is the cornerstone of email anti-spoofing protection. A DMARC rollout progresses through three phases: monitoring (p=none), quarantine (p=quarantine), and full enforcement (p=reject). When configured at p=reject, any email that fails both SPF and DKIM checks is outright rejected. Google and Yahoo now require DMARC for bulk senders (5,000+ emails), driving a 65% reduction in unauthenticated messages. The rollout typically takes 3-6 months for safe deployment.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing dmarc policy enforcement rollout\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n- Administrative access to DNS management for the domain\n- Understanding of SPF, DKIM, and DMARC protocols (RFC 7208, 6376, 7489)\n- Complete inventory of all legitimate email sending sources\n- DMARC reporting analysis tool (EasyDMARC, DMARCLY, Valimail, or dmarcian)\n- Email gateway with DMARC enforcement capability\n\n## Key Concepts\n\n### DMARC Policy Levels\n| Policy | Behavior | Use Case |\n|---|---|---|\n| p=none | Monitor only, no action on failures | Discovery phase |\n| p=quarantine | Send failing messages to spam\u002Fjunk | Transition phase |\n| p=reject | Block failing messages entirely | Full enforcement |\n\n### DMARC Record Anatomy\n```\nv=DMARC1; p=quarantine; pct=25; rua=mailto:dmarc-agg@company.com; ruf=mailto:dmarc-forensic@company.com; adkim=r; aspf=r; fo=1\n```\n- **p**: Policy for organizational domain\n- **sp**: Policy for subdomains\n- **pct**: Percentage of messages subject to policy (for gradual rollout)\n- **rua**: Aggregate report destination (daily XML reports)\n- **ruf**: Forensic report destination (per-failure reports)\n- **adkim**: DKIM alignment mode (r=relaxed, s=strict)\n- **aspf**: SPF alignment mode (r=relaxed, s=strict)\n- **fo**: Failure reporting options (0=both fail, 1=either fails)\n\n### SPF and DKIM Alignment\n- **SPF Alignment**: The domain in the Return-Path (envelope sender) must match the From header domain\n- **DKIM Alignment**: The d= domain in the DKIM signature must match the From header domain\n- **Relaxed**: Organizational domain match (sub.example.com matches example.com)\n- **Strict**: Exact domain match required\n\n## Workflow\n\n### Step 1: Inventory All Sending Sources (Week 1-2)\n- Audit all systems sending email as your domain (marketing, CRM, ticketing, transactional)\n- Document third-party services: Salesforce, Mailchimp, SendGrid, Zendesk, etc.\n- Identify internal mail servers, applications, and relay hosts\n- Check for shadow IT email sending (departments using unauthorized services)\n\n### Step 2: Configure SPF and DKIM (Week 2-4)\n- Consolidate SPF record with all legitimate sending IPs and includes\n- Ensure SPF record stays under 10 DNS lookup limit\n- Generate and publish DKIM keys for each sending source\n- Verify DKIM signing works for all outbound mail paths\n- Test with MX Toolbox or dmarcian SPF\u002FDKIM validators\n\n### Step 3: Deploy DMARC in Monitoring Mode (Week 4-6)\n- Publish initial DMARC record: `v=DMARC1; p=none; rua=mailto:dmarc@company.com; fo=1`\n- Wait 1-2 weeks to collect representative aggregate reports\n- Analyze reports to identify unauthorized senders and alignment failures\n- Fix SPF\u002FDKIM for all legitimate sources showing failures\n- Iterate until all legitimate mail passes DMARC\n\n### Step 4: Move to Quarantine with pct Tag (Week 6-12)\n- Update to quarantine at 10%: `v=DMARC1; p=quarantine; pct=10; rua=...`\n- Monitor for false positives (legitimate mail being quarantined)\n- Increase pct gradually: 10% -> 25% -> 50% -> 75% -> 100%\n- Each increase: wait 1-2 weeks and review reports before advancing\n- Fix any remaining alignment issues discovered at each stage\n\n### Step 5: Advance to Reject Policy (Week 12-20)\n- After stable quarantine at 100%, move to reject at 10%: `v=DMARC1; p=reject; pct=10; rua=...`\n- Gradually increase pct: 10% -> 25% -> 50% -> 100%\n- Monitor closely for legitimate mail being rejected\n- Establish emergency rollback procedure (revert to quarantine)\n- Apply subdomain policy: `sp=reject` for subdomains\n\n### Step 6: Ongoing Monitoring and Maintenance\n- Continuously monitor DMARC aggregate reports\n- Add new sending sources before they start sending\n- Review forensic reports for spoofing attempts\n- Maintain SPF record as sending infrastructure changes\n- Rotate DKIM keys annually\n\n## Tools & Resources\n- **EasyDMARC**: DMARC monitoring dashboard with aggregate\u002Fforensic report analysis\n- **DMARCLY**: SPF, DKIM, DMARC monitoring with auto-DNS updates\n- **dmarcian**: DMARC deployment and management platform\n- **Valimail**: Automated DMARC enforcement with hosted authentication\n- **MX Toolbox**: DNS record lookup and DMARC validator\n- **Google Admin Toolbox**: DMARC check and diagnostic tools\n\n## Validation\n- DMARC record published and resolving correctly at _dmarc.domain.com\n- All legitimate sending sources pass SPF and\u002For DKIM alignment\n- Aggregate reports show >99% legitimate mail passing DMARC\n- Spoofed messages from unauthorized senders are rejected\n- No legitimate mail blocked after full p=reject enforcement\n- Subdomain policy (sp=) also set to reject\n","# Performing DMARC Policy Enforcement Rollout\n\n## Overview\nDomain-based Message Authentication, Reporting and Conformance (DMARC) is the cornerstone of email anti-spoofing protection. A DMARC rollout progresses through three phases: monitoring (p=none), quarantine (p=quarantine), and full enforcement (p=reject). When configured at p=reject, any email that fails both SPF and DKIM checks is outright rejected. Google and Yahoo now require DMARC for bulk senders (5,000+ emails), driving a 65% reduction in unauthenticated messages. The rollout typically takes 3-6 months for safe deployment.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing dmarc policy enforcement rollout\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n- Administrative access to DNS management for the domain\n- Understanding of SPF, DKIM, and DMARC protocols (RFC 7208, 6376, 7489)\n- Complete inventory of all legitimate email sending sources\n- DMARC reporting analysis tool (EasyDMARC, DMARCLY, Valimail, or dmarcian)\n- Email gateway with DMARC enforcement capability\n\n## Key Concepts\n\n### DMARC Policy Levels\n| Policy | Behavior | Use Case |\n|---|---|---|\n| p=none | Monitor only, no action on failures | Discovery phase |\n| p=quarantine | Send failing messages to spam\u002Fjunk | Transition phase |\n| p=reject | Block failing messages entirely | Full enforcement |\n\n### DMARC Record Anatomy\n```\nv=DMARC1; p=quarantine; pct=25; rua=mailto:dmarc-agg@company.com; ruf=mailto:dmarc-forensic@company.com; adkim=r; aspf=r; fo=1\n```\n- **p**: Policy for organizational domain\n- **sp**: Policy for subdomains\n- **pct**: Percentage of messages subject to policy (for gradual rollout)\n- **rua**: Aggregate report destination (daily XML reports)\n- **ruf**: Forensic report destination (per-failure reports)\n- **adkim**: DKIM alignment mode (r=relaxed, s=strict)\n- **aspf**: SPF alignment mode (r=relaxed, s=strict)\n- **fo**: Failure reporting options (0=both fail, 1=either fails)\n\n### SPF and DKIM Alignment\n- **SPF Alignment**: The domain in the Return-Path (envelope sender) must match the From header domain\n- **DKIM Alignment**: The d= domain in the DKIM signature must match the From header domain\n- **Relaxed**: Organizational domain match (sub.example.com matches example.com)\n- **Strict**: Exact domain match required\n\n## Workflow\n\n### Step 1: Inventory All Sending Sources (Week 1-2)\n- Audit all systems sending email as your domain (marketing, CRM, ticketing, transactional)\n- Document third-party services: Salesforce, Mailchimp, SendGrid, Zendesk, etc.\n- Identify internal mail servers, applications, and relay hosts\n- Check for shadow IT email sending (departments using unauthorized services)\n\n### Step 2: Configure SPF and DKIM (Week 2-4)\n- Consolidate SPF record with all legitimate sending IPs and includes\n- Ensure SPF record stays under 10 DNS lookup limit\n- Generate and publish DKIM keys for each sending source\n- Verify DKIM signing works for all outbound mail paths\n- Test with MX Toolbox or dmarcian SPF\u002FDKIM validators\n\n### Step 3: Deploy DMARC in Monitoring Mode (Week 4-6)\n- Publish initial DMARC record: `v=DMARC1; p=none; rua=mailto:dmarc@company.com; fo=1`\n- Wait 1-2 weeks to collect representative aggregate reports\n- Analyze reports to identify unauthorized senders and alignment failures\n- Fix SPF\u002FDKIM for all legitimate sources showing failures\n- Iterate until all legitimate mail passes DMARC\n\n### Step 4: Move to Quarantine with pct Tag (Week 6-12)\n- Update to quarantine at 10%: `v=DMARC1; p=quarantine; pct=10; rua=...`\n- Monitor for false positives (legitimate mail being quarantined)\n- Increase pct gradually: 10% -> 25% -> 50% -> 75% -> 100%\n- Each increase: wait 1-2 weeks and review reports before advancing\n- Fix any remaining alignment issues discovered at each stage\n\n### Step 5: Advance to Reject Policy (Week 12-20)\n- After stable quarantine at 100%, move to reject at 10%: `v=DMARC1; p=reject; pct=10; rua=...`\n- Gradually increase pct: 10% -> 25% -> 50% -> 100%\n- Monitor closely for legitimate mail being rejected\n- Establish emergency rollback procedure (revert to quarantine)\n- Apply subdomain policy: `sp=reject` for subdomains\n\n### Step 6: Ongoing Monitoring and Maintenance\n- Continuously monitor DMARC aggregate reports\n- Add new sending sources before they start sending\n- Review forensic reports for spoofing attempts\n- Maintain SPF record as sending infrastructure changes\n- Rotate DKIM keys annually\n\n## Tools & Resources\n- **EasyDMARC**: DMARC monitoring dashboard with aggregate\u002Fforensic report analysis\n- **DMARCLY**: SPF, DKIM, DMARC monitoring with auto-DNS updates\n- **dmarcian**: DMARC deployment and management platform\n- **Valimail**: Automated DMARC enforcement with hosted authentication\n- **MX Toolbox**: DNS record lookup and DMARC validator\n- **Google Admin Toolbox**: DMARC check and diagnostic tools\n\n## Validation\n- DMARC record published and resolving correctly at _dmarc.domain.com\n- All legitimate sending sources pass SPF and\u002For DKIM alignment\n- Aggregate reports show >99% legitimate mail passing DMARC\n- Spoofed messages from unauthorized senders are rejected\n- No legitimate mail blocked after full p=reject enforcement\n- Subdomain policy (sp=) also set to reject\n",{"name":5,"tags":52,"author":55,"domain":46,"license":15,"version":56,"nist_csf":57,"subdomain":62,"description":7,"mitre_attack":63},[31,53,54,37,38,41,40,39],"spf","dkim","mahipal","1.0",[58,59,60,61],"PR.AT-01","DE.CM-09","RS.CO-02","DE.AE-02","phishing-defense",[64,65,66,67],"T1566","T1598","T1534","T1036","main","7925716f065257435fdb12e97f7e52842147d5ad",".claude\u002Fskills\u002Fperforming-dmarc-policy-enforcement-rollout","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":77,"prompt":87,"zipAvailable":88},[78,81,84],{"tool":79,"command":80},"npx","npx skills add henriquescastilho\u002Fmy-claude --skill performing-dmarc-policy-enforcement-rollout",{"tool":82,"command":83},"bunx","bunx skills add henriquescastilho\u002Fmy-claude --skill performing-dmarc-policy-enforcement-rollout",{"tool":85,"command":86},"pnpm","pnpm dlx skills add henriquescastilho\u002Fmy-claude --skill performing-dmarc-policy-enforcement-rollout","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fperforming-dmarc-policy-enforcement-rollout\u002FSKILL.md",true,[90,96,101,107,111,115,121],{"path":91,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"assets\u002Ftemplate.md","ASSET","资产文件",1577,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fperforming-dmarc-policy-enforcement-rollout\u002Fassets\u002Ftemplate.md",{"path":97,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":99,"sourceHtmlUrl":100},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fperforming-dmarc-policy-enforcement-rollout\u002FLICENSE",{"path":102,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fapi-reference.md","REFERENCE","参考文档",907,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fperforming-dmarc-policy-enforcement-rollout\u002Freferences\u002Fapi-reference.md",{"path":108,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fstandards.md",1708,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fperforming-dmarc-policy-enforcement-rollout\u002Freferences\u002Fstandards.md",{"path":112,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":113,"sourceHtmlUrl":114},"references\u002Fworkflows.md",2772,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fperforming-dmarc-policy-enforcement-rollout\u002Freferences\u002Fworkflows.md",{"path":116,"resourceType":117,"resourceTypeDesc":118,"sizeBytes":119,"sourceHtmlUrl":120},"scripts\u002Fagent.py","SCRIPT","脚本",5543,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fperforming-dmarc-policy-enforcement-rollout\u002Fscripts\u002Fagent.py",{"path":122,"resourceType":117,"resourceTypeDesc":118,"sizeBytes":123,"sourceHtmlUrl":124},"scripts\u002Fprocess.py",12014,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fperforming-dmarc-policy-enforcement-rollout\u002Fscripts\u002Fprocess.py",[126,167,176,185,207,233],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":130,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":147,"publishedAt":47},"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",[133,136,139,142],{"categoryNo":134,"categoryName":135,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":137,"categoryName":138,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":140,"categoryName":141,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000004","电子表格",{"categoryNo":143,"categoryName":144,"taxonomyType":145,"taxonomyTypeDesc":146},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[128,148,149,150,151,152,153,154,155,156,157,158,159,160,161,162,163,164,165,166],"docx","PDF","pptx","xlsx","documents","csv","ocr","Audio","Bash","markdown","convert","read","write","edit","html","images","files","youtube","with",{"skillNo":168,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":130,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":175,"publishedAt":47},"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",[171,172,173,174],{"categoryNo":134,"categoryName":135,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":137,"categoryName":138,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":140,"categoryName":141,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":143,"categoryName":144,"taxonomyType":145,"taxonomyTypeDesc":146},[128,148,149,150,151,152,153,154,155,156,157,158,159,160,161,162,163,164,165,166],{"skillNo":177,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":130,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":184,"publishedAt":47},"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",[180,181,182,183],{"categoryNo":134,"categoryName":135,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":137,"categoryName":138,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":140,"categoryName":141,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":143,"categoryName":144,"taxonomyType":145,"taxonomyTypeDesc":146},[128,148,149,150,151,152,153,154,155,156,157,158,159,160,161,162,163,164,165,166],{"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":130,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":191,"publishedAt":47},"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",[],[192,193,194,195,196,197,198,199,200,201,202,203,204,205,206],"python","zarr python","storage","integration","s3","gcs","cloud","dask","parallel","pipelines","arrays","numpy","scientific computing","scale","scientific",{"skillNo":208,"name":209,"nameZh":6,"description":210,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":130,"licenseFileUrl":6,"sourceHtmlUrl":211,"categories":212,"keywords":214,"publishedAt":47},"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",[213],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[215,216,217,218,219,220,221,222,223,224,225,159,160,226,227,228,229,230,231,232],"oracle","what if oracle","go","run","ux","futures","analysis","explore","decision","branch","question","idea","exploration","options","stress-test","strategies","scenario","stress",{"skillNo":234,"name":235,"nameZh":6,"description":236,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":130,"licenseFileUrl":6,"sourceHtmlUrl":237,"categories":238,"keywords":249,"publishedAt":47},"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",[239,242,245,246],{"categoryNo":240,"categoryName":241,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":243,"categoryName":244,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":247,"categoryName":248,"taxonomyType":145,"taxonomyTypeDesc":146},"01JBSEEDCAT000000000000036","内容创作者",[250,251,252,253,254,255,256,257,156,258,159,160,161,259,260,261,262,263,206,264],"templates","venue templates","research","guidelines","NeurIPS","ICML","LaTeX","science","access","proposals","Academic","requirements","formatting","journal","chi"]