[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ESXQ0RKQTY9P6AMSF3ECW8":3,"skill-same:01M6ESXQ0RKQTY9P6AMSF3ECW8":121},{"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":64,"commitSha":65,"skillDirectory":66,"forksCount":14,"repositoryHtmlUrl":67,"repositoryHomepageUrl":68,"ownerHtmlUrl":69,"ownerBlogUrl":6,"ownerDescription":70,"updatedAt":71,"install":72,"resources":85},"01M6ESXQ0RKQTY9P6AMSF3ECW8","building-patch-tuesday-response-process",null,"Establish a structured operational process to triage, test, and deploy Microsoft Patch Tuesday security updates within risk-based remediation SLAs.","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\u002Fbuilding-patch-tuesday-response-process\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],"patch","process","building patch tuesday response process","windows-update","id","vulnerability","risk-based","risk","remediation","vulnerability-management","security","vulnerability-remediation","sccm","wsus","patch-tuesday","patch-management","update","windows","test","cybersecurity","2026-11-10 10:12:30",false,"---\nname: building-patch-tuesday-response-process\ndescription: Establish a structured operational process to triage, test, and deploy\n  Microsoft Patch Tuesday security updates within risk-based remediation SLAs.\ndomain: cybersecurity\nsubdomain: vulnerability-management\ntags:\n- patch-management\n- patch-tuesday\n- microsoft\n- wsus\n- sccm\n- vulnerability-remediation\n- windows-update\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- ID.RA-01\n- ID.RA-02\n- ID.IM-02\n- ID.RA-06\nmitre_attack:\n- T1190\n- T1203\n- T1068\n- T1210\n- T1588.006\n---\n# Building Patch Tuesday Response Process\n\n## Overview\nMicrosoft releases security updates on the second Tuesday of each month (\"Patch Tuesday\"), addressing vulnerabilities across Windows, Office, Exchange, SQL Server, Azure services, and other products. In 2025, Microsoft patched over 1,129 vulnerabilities across the year -- an 11.9% increase from 2024 -- making a structured response process critical. The leading risk types include elevation of privilege (49%), remote code execution (34%), and information disclosure (7%). This skill covers building a repeatable Patch Tuesday response workflow from initial advisory review through testing, deployment, and validation.\n\n\n## When to Use\n\n- When deploying or configuring building patch tuesday response process capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n- Access to Microsoft Security Response Center (MSRC) update guide\n- Vulnerability management platform (Qualys VMDR, Rapid7, Tenable)\n- Patch deployment infrastructure (WSUS, SCCM\u002FMECM, Intune, or third-party)\n- Test environment mirroring production configurations\n- Change management process (ITIL-based or equivalent)\n- Communication channels for cross-team coordination\n\n## Core Concepts\n\n### Patch Tuesday Timeline\n\n| Day | Activity | Owner |\n|-----|----------|-------|\n| T+0 (Tuesday 10 AM PT) | Microsoft releases patches and advisories | Microsoft |\n| T+0 (Tuesday afternoon) | Security team reviews advisories and triages | Security Ops |\n| T+1 (Wednesday) | Qualys\u002Fvendor scan signatures updated | VM Platform |\n| T+1-T+2 | Emergency patches deployed for zero-days | IT Operations |\n| T+2-T+5 | Test patches in staging environment | QA\u002FIT Ops |\n| T+5-T+7 | Deploy to Pilot group (5-10% of fleet) | IT Operations |\n| T+7-T+14 | Deploy to Production Ring 1 (servers) | IT Operations |\n| T+14-T+21 | Deploy to Production Ring 2 (workstations) | IT Operations |\n| T+21-T+30 | Validation scanning and compliance reporting | Security Ops |\n\n### Patch Categorization Framework\n\n| Category | Criteria | Response SLA |\n|----------|----------|-------------|\n| Zero-Day \u002F Exploited | Active exploitation confirmed, CISA KEV listed | 24-48 hours |\n| Critical RCE | CVSS >= 9.0, remote code execution, no auth required | 3-5 days |\n| Critical with Exploit | Public exploit code or EPSS > 0.7 | 7 days |\n| High Severity | CVSS 7.0-8.9, privilege escalation | 14 days |\n| Medium Severity | CVSS 4.0-6.9 | 30 days |\n| Low \u002F Informational | CVSS \u003C 4.0, defense-in-depth | Next maintenance window |\n\n### Microsoft Product Categories to Monitor\n\n| Category | Products | Risk Level |\n|----------|----------|------------|\n| Windows OS | Windows 10, 11, Server 2016-2025 | Critical |\n| Exchange Server | Exchange 2016, 2019, Online | Critical |\n| SQL Server | SQL 2016-2022 | High |\n| Office Suite | Microsoft 365, Office 2019-2024 | High |\n| .NET Framework | .NET 4.x, .NET 6-9 | Medium |\n| Azure Services | Azure AD, Entra ID, Azure Stack | High |\n| Edge\u002FBrowser | Edge Chromium, IE mode | Medium |\n| Development Tools | Visual Studio, VS Code | Low |\n\n## Workflow\n\n### Step 1: Pre-Patch Tuesday Preparation (Monday before)\n```\nPreparation Checklist:\n  [ ] Confirm WSUS\u002FSCCM sync schedules are active\n  [ ] Verify test environment is available and current\n  [ ] Review outstanding patches from previous month\n  [ ] Confirm monitoring dashboards are operational\n  [ ] Pre-stage communication templates\n  [ ] Ensure rollback procedures are documented\n  [ ] Verify backup jobs ran successfully on critical servers\n```\n\n### Step 2: Day-of Triage (Patch Tuesday)\n\n```\nTriage Process:\n  1. Monitor MSRC Update Guide (https:\u002F\u002Fmsrc.microsoft.com\u002Fupdate-guide)\n  2. Review Microsoft Security Blog for advisory summaries\n  3. Cross-reference with CISA KEV additions (same day)\n  4. Check vendor advisories (Qualys, Rapid7, CrowdStrike analysis)\n  5. Identify zero-day and actively exploited vulnerabilities\n  6. Classify each CVE by severity and applicability\n  7. Determine deployment rings and timeline for each patch\n  8. Submit emergency change request for zero-day patches\n  9. Communicate triage results to IT Operations and management\n```\n\n### Step 3: Scan and Gap Analysis\n\n```python\n# Post-Patch-Tuesday scan workflow\ndef run_patch_tuesday_scan(scanner_api, target_groups):\n    \"\"\"Trigger vulnerability scans after Patch Tuesday updates.\"\"\"\n    for group in target_groups:\n        print(f\"[*] Scanning {group['name']}...\")\n        scan_id = scanner_api.launch_scan(\n            target=group[\"targets\"],\n            template=\"patch-tuesday-focused\",\n            credentials=group[\"creds\"]\n        )\n        print(f\"    Scan launched: {scan_id}\")\n\n    # Wait for scan completion, then generate report\n    results = scanner_api.get_scan_results(scan_id)\n    missing_patches = [r for r in results if r[\"status\"] == \"missing\"]\n\n    # Categorize by Patch Tuesday release\n    current_month = [p for p in missing_patches\n                     if p[\"vendor_advisory_date\"] >= patch_tuesday_date]\n\n    return {\n        \"total_missing\": len(missing_patches),\n        \"current_month\": len(current_month),\n        \"zero_day\": [p for p in current_month if p.get(\"actively_exploited\")],\n        \"critical\": [p for p in current_month if p[\"cvss\"] >= 9.0],\n    }\n```\n\n### Step 4: Ring-Based Deployment Strategy\n\n```\nRing 0 - Emergency (0-48 hours):\n    Scope:     Zero-day and actively exploited CVEs only\n    Method:    Manual or targeted push (SCCM expedite)\n    Targets:   Internet-facing servers, critical infrastructure\n    Approval:  Emergency change, verbal CISO approval\n    Rollback:  Immediate rollback if service degradation\n\nRing 1 - Pilot (Day 2-7):\n    Scope:     All critical and high patches\n    Method:    WSUS\u002FSCCM automatic deployment\n    Targets:   IT department machines, test group (5-10%)\n    Approval:  Standard change with CAB notification\n    Monitoring: 48-hour soak period, check for BSOD, app crashes\n\nRing 2 - Production Servers (Day 7-14):\n    Scope:     All security patches\n    Method:    SCCM maintenance windows (off-hours)\n    Targets:   Production servers by tier\n    Approval:  Standard change with CAB approval\n    Monitoring: Application health checks, performance baseline\n\nRing 3 - Workstations (Day 14-21):\n    Scope:     All security patches + quality updates\n    Method:    Windows Update for Business \u002F Intune\n    Targets:   All managed workstations\n    Approval:  Pre-approved standard change\n    Monitoring: Help desk ticket monitoring for issues\n\nRing 4 - Stragglers (Day 21-30):\n    Scope:     Catch remaining unpatched systems\n    Method:    Forced deployment with restart\n    Targets:   Systems that missed prior rings\n    Approval:  Compliance-driven enforcement\n```\n\n### Step 5: Validation and Reporting\n\n```\nPost-Deployment Validation:\n  1. Re-scan environment with updated vulnerability signatures\n  2. Compare pre-patch and post-patch scan results\n  3. Calculate patch compliance rate per ring and department\n  4. Identify failed patches and investigate root causes\n  5. Generate compliance report for management review\n  6. Update risk register with residual unpatched vulnerabilities\n  7. Document exceptions and compensating controls\n```\n\n## Best Practices\n1. Subscribe to MSRC notifications and vendor analysis blogs for early intelligence\n2. Maintain a dedicated Patch Tuesday war room or Slack\u002FTeams channel\n3. Always patch zero-day vulnerabilities outside the normal ring schedule\n4. Test patches against critical business applications before broad deployment\n5. Track patch compliance metrics month-over-month for trend analysis\n6. Maintain rollback procedures for every deployment ring\n7. Coordinate with application owners for compatibility testing\n8. Document all exceptions with compensating controls and review dates\n\n## Common Pitfalls\n- Deploying all patches simultaneously without ring-based testing\n- Not scanning after patching to validate remediation\n- Treating all patches equally without risk-based prioritization\n- Ignoring cumulative update dependencies causing patch failures\n- Not accounting for server reboot requirements in maintenance windows\n- Failing to communicate patch status to business stakeholders\n\n## Related Skills\n- implementing-rapid7-insightvm-for-scanning\n- performing-cve-prioritization-with-kev-catalog\n- implementing-vulnerability-remediation-sla\n- implementing-patch-management-workflow\n","# Building Patch Tuesday Response Process\n\n## Overview\nMicrosoft releases security updates on the second Tuesday of each month (\"Patch Tuesday\"), addressing vulnerabilities across Windows, Office, Exchange, SQL Server, Azure services, and other products. In 2025, Microsoft patched over 1,129 vulnerabilities across the year -- an 11.9% increase from 2024 -- making a structured response process critical. The leading risk types include elevation of privilege (49%), remote code execution (34%), and information disclosure (7%). This skill covers building a repeatable Patch Tuesday response workflow from initial advisory review through testing, deployment, and validation.\n\n\n## When to Use\n\n- When deploying or configuring building patch tuesday response process capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n- Access to Microsoft Security Response Center (MSRC) update guide\n- Vulnerability management platform (Qualys VMDR, Rapid7, Tenable)\n- Patch deployment infrastructure (WSUS, SCCM\u002FMECM, Intune, or third-party)\n- Test environment mirroring production configurations\n- Change management process (ITIL-based or equivalent)\n- Communication channels for cross-team coordination\n\n## Core Concepts\n\n### Patch Tuesday Timeline\n\n| Day | Activity | Owner |\n|-----|----------|-------|\n| T+0 (Tuesday 10 AM PT) | Microsoft releases patches and advisories | Microsoft |\n| T+0 (Tuesday afternoon) | Security team reviews advisories and triages | Security Ops |\n| T+1 (Wednesday) | Qualys\u002Fvendor scan signatures updated | VM Platform |\n| T+1-T+2 | Emergency patches deployed for zero-days | IT Operations |\n| T+2-T+5 | Test patches in staging environment | QA\u002FIT Ops |\n| T+5-T+7 | Deploy to Pilot group (5-10% of fleet) | IT Operations |\n| T+7-T+14 | Deploy to Production Ring 1 (servers) | IT Operations |\n| T+14-T+21 | Deploy to Production Ring 2 (workstations) | IT Operations |\n| T+21-T+30 | Validation scanning and compliance reporting | Security Ops |\n\n### Patch Categorization Framework\n\n| Category | Criteria | Response SLA |\n|----------|----------|-------------|\n| Zero-Day \u002F Exploited | Active exploitation confirmed, CISA KEV listed | 24-48 hours |\n| Critical RCE | CVSS >= 9.0, remote code execution, no auth required | 3-5 days |\n| Critical with Exploit | Public exploit code or EPSS > 0.7 | 7 days |\n| High Severity | CVSS 7.0-8.9, privilege escalation | 14 days |\n| Medium Severity | CVSS 4.0-6.9 | 30 days |\n| Low \u002F Informational | CVSS \u003C 4.0, defense-in-depth | Next maintenance window |\n\n### Microsoft Product Categories to Monitor\n\n| Category | Products | Risk Level |\n|----------|----------|------------|\n| Windows OS | Windows 10, 11, Server 2016-2025 | Critical |\n| Exchange Server | Exchange 2016, 2019, Online | Critical |\n| SQL Server | SQL 2016-2022 | High |\n| Office Suite | Microsoft 365, Office 2019-2024 | High |\n| .NET Framework | .NET 4.x, .NET 6-9 | Medium |\n| Azure Services | Azure AD, Entra ID, Azure Stack | High |\n| Edge\u002FBrowser | Edge Chromium, IE mode | Medium |\n| Development Tools | Visual Studio, VS Code | Low |\n\n## Workflow\n\n### Step 1: Pre-Patch Tuesday Preparation (Monday before)\n```\nPreparation Checklist:\n  [ ] Confirm WSUS\u002FSCCM sync schedules are active\n  [ ] Verify test environment is available and current\n  [ ] Review outstanding patches from previous month\n  [ ] Confirm monitoring dashboards are operational\n  [ ] Pre-stage communication templates\n  [ ] Ensure rollback procedures are documented\n  [ ] Verify backup jobs ran successfully on critical servers\n```\n\n### Step 2: Day-of Triage (Patch Tuesday)\n\n```\nTriage Process:\n  1. Monitor MSRC Update Guide (https:\u002F\u002Fmsrc.microsoft.com\u002Fupdate-guide)\n  2. Review Microsoft Security Blog for advisory summaries\n  3. Cross-reference with CISA KEV additions (same day)\n  4. Check vendor advisories (Qualys, Rapid7, CrowdStrike analysis)\n  5. Identify zero-day and actively exploited vulnerabilities\n  6. Classify each CVE by severity and applicability\n  7. Determine deployment rings and timeline for each patch\n  8. Submit emergency change request for zero-day patches\n  9. Communicate triage results to IT Operations and management\n```\n\n### Step 3: Scan and Gap Analysis\n\n```python\n# Post-Patch-Tuesday scan workflow\ndef run_patch_tuesday_scan(scanner_api, target_groups):\n    \"\"\"Trigger vulnerability scans after Patch Tuesday updates.\"\"\"\n    for group in target_groups:\n        print(f\"[*] Scanning {group['name']}...\")\n        scan_id = scanner_api.launch_scan(\n            target=group[\"targets\"],\n            template=\"patch-tuesday-focused\",\n            credentials=group[\"creds\"]\n        )\n        print(f\"    Scan launched: {scan_id}\")\n\n    # Wait for scan completion, then generate report\n    results = scanner_api.get_scan_results(scan_id)\n    missing_patches = [r for r in results if r[\"status\"] == \"missing\"]\n\n    # Categorize by Patch Tuesday release\n    current_month = [p for p in missing_patches\n                     if p[\"vendor_advisory_date\"] >= patch_tuesday_date]\n\n    return {\n        \"total_missing\": len(missing_patches),\n        \"current_month\": len(current_month),\n        \"zero_day\": [p for p in current_month if p.get(\"actively_exploited\")],\n        \"critical\": [p for p in current_month if p[\"cvss\"] >= 9.0],\n    }\n```\n\n### Step 4: Ring-Based Deployment Strategy\n\n```\nRing 0 - Emergency (0-48 hours):\n    Scope:     Zero-day and actively exploited CVEs only\n    Method:    Manual or targeted push (SCCM expedite)\n    Targets:   Internet-facing servers, critical infrastructure\n    Approval:  Emergency change, verbal CISO approval\n    Rollback:  Immediate rollback if service degradation\n\nRing 1 - Pilot (Day 2-7):\n    Scope:     All critical and high patches\n    Method:    WSUS\u002FSCCM automatic deployment\n    Targets:   IT department machines, test group (5-10%)\n    Approval:  Standard change with CAB notification\n    Monitoring: 48-hour soak period, check for BSOD, app crashes\n\nRing 2 - Production Servers (Day 7-14):\n    Scope:     All security patches\n    Method:    SCCM maintenance windows (off-hours)\n    Targets:   Production servers by tier\n    Approval:  Standard change with CAB approval\n    Monitoring: Application health checks, performance baseline\n\nRing 3 - Workstations (Day 14-21):\n    Scope:     All security patches + quality updates\n    Method:    Windows Update for Business \u002F Intune\n    Targets:   All managed workstations\n    Approval:  Pre-approved standard change\n    Monitoring: Help desk ticket monitoring for issues\n\nRing 4 - Stragglers (Day 21-30):\n    Scope:     Catch remaining unpatched systems\n    Method:    Forced deployment with restart\n    Targets:   Systems that missed prior rings\n    Approval:  Compliance-driven enforcement\n```\n\n### Step 5: Validation and Reporting\n\n```\nPost-Deployment Validation:\n  1. Re-scan environment with updated vulnerability signatures\n  2. Compare pre-patch and post-patch scan results\n  3. Calculate patch compliance rate per ring and department\n  4. Identify failed patches and investigate root causes\n  5. Generate compliance report for management review\n  6. Update risk register with residual unpatched vulnerabilities\n  7. Document exceptions and compensating controls\n```\n\n## Best Practices\n1. Subscribe to MSRC notifications and vendor analysis blogs for early intelligence\n2. Maintain a dedicated Patch Tuesday war room or Slack\u002FTeams channel\n3. Always patch zero-day vulnerabilities outside the normal ring schedule\n4. Test patches against critical business applications before broad deployment\n5. Track patch compliance metrics month-over-month for trend analysis\n6. Maintain rollback procedures for every deployment ring\n7. Coordinate with application owners for compatibility testing\n8. Document all exceptions with compensating controls and review dates\n\n## Common Pitfalls\n- Deploying all patches simultaneously without ring-based testing\n- Not scanning after patching to validate remediation\n- Treating all patches equally without risk-based prioritization\n- Ignoring cumulative update dependencies causing patch failures\n- Not accounting for server reboot requirements in maintenance windows\n- Failing to communicate patch status to business stakeholders\n\n## Related Skills\n- implementing-rapid7-insightvm-for-scanning\n- performing-cve-prioritization-with-kev-catalog\n- implementing-vulnerability-remediation-sla\n- implementing-patch-management-workflow\n",{"name":5,"tags":49,"author":51,"domain":43,"license":15,"version":52,"nist_csf":53,"subdomain":33,"description":7,"mitre_attack":58},[39,38,50,37,36,35,27],"microsoft","mahipal","1.0",[54,55,56,57],"ID.RA-01","ID.RA-02","ID.IM-02","ID.RA-06",[59,60,61,62,63],"T1190","T1203","T1068","T1210","T1588.006","main","7925716f065257435fdb12e97f7e52842147d5ad",".claude\u002Fskills\u002Fbuilding-patch-tuesday-response-process","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":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add henriquescastilho\u002Fmy-claude --skill building-patch-tuesday-response-process",{"tool":78,"command":79},"bunx","bunx skills add henriquescastilho\u002Fmy-claude --skill building-patch-tuesday-response-process",{"tool":81,"command":82},"pnpm","pnpm dlx skills add henriquescastilho\u002Fmy-claude --skill building-patch-tuesday-response-process","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbuilding-patch-tuesday-response-process\u002FSKILL.md",true,[86,92,97,103,107,111,117],{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"assets\u002Ftemplate.md","ASSET","资产文件",1044,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbuilding-patch-tuesday-response-process\u002Fassets\u002Ftemplate.md",{"path":93,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbuilding-patch-tuesday-response-process\u002FLICENSE",{"path":98,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fapi-reference.md","REFERENCE","参考文档",1861,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbuilding-patch-tuesday-response-process\u002Freferences\u002Fapi-reference.md",{"path":104,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fstandards.md",1410,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbuilding-patch-tuesday-response-process\u002Freferences\u002Fstandards.md",{"path":108,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fworkflows.md",2905,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbuilding-patch-tuesday-response-process\u002Freferences\u002Fworkflows.md",{"path":112,"resourceType":113,"resourceTypeDesc":114,"sizeBytes":115,"sourceHtmlUrl":116},"scripts\u002Fagent.py","SCRIPT","脚本",6492,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbuilding-patch-tuesday-response-process\u002Fscripts\u002Fagent.py",{"path":118,"resourceType":113,"resourceTypeDesc":114,"sizeBytes":119,"sourceHtmlUrl":120},"scripts\u002Fprocess.py",7182,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbuilding-patch-tuesday-response-process\u002Fscripts\u002Fprocess.py",[122,163,172,181,203,229],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":126,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":143,"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",[129,132,135,138],{"categoryNo":130,"categoryName":131,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":133,"categoryName":134,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":136,"categoryName":137,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000004","电子表格",{"categoryNo":139,"categoryName":140,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[124,144,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159,160,161,162],"docx","PDF","pptx","xlsx","documents","csv","ocr","Audio","Bash","markdown","convert","read","write","edit","html","images","files","youtube","with",{"skillNo":164,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":126,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":171,"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",[167,168,169,170],{"categoryNo":130,"categoryName":131,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":133,"categoryName":134,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":136,"categoryName":137,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":139,"categoryName":140,"taxonomyType":141,"taxonomyTypeDesc":142},[124,144,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159,160,161,162],{"skillNo":173,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":126,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":180,"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",[176,177,178,179],{"categoryNo":130,"categoryName":131,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":133,"categoryName":134,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":136,"categoryName":137,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":139,"categoryName":140,"taxonomyType":141,"taxonomyTypeDesc":142},[124,144,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159,160,161,162],{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":126,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":187,"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",[],[188,189,190,191,192,193,194,195,196,197,198,199,200,201,202],"python","zarr python","storage","integration","s3","gcs","cloud","dask","parallel","pipelines","arrays","numpy","scientific computing","scale","scientific",{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":126,"licenseFileUrl":6,"sourceHtmlUrl":207,"categories":208,"keywords":210,"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",[209],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[211,212,213,214,215,216,217,218,219,220,221,155,156,222,223,224,225,226,227,228],"oracle","what if oracle","go","run","ux","futures","analysis","explore","decision","branch","question","idea","exploration","options","stress-test","strategies","scenario","stress",{"skillNo":230,"name":231,"nameZh":6,"description":232,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":126,"licenseFileUrl":6,"sourceHtmlUrl":233,"categories":234,"keywords":245,"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",[235,238,241,242],{"categoryNo":236,"categoryName":237,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":239,"categoryName":240,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":243,"categoryName":244,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000036","内容创作者",[246,247,248,249,250,251,252,253,152,254,155,156,157,255,256,257,258,259,202,260],"templates","venue templates","research","guidelines","NeurIPS","ICML","LaTeX","science","access","proposals","Academic","requirements","formatting","journal","chi"]