[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78MMSXYGN7VMWPXVAAPATE7":3,"skill-same:01M78MMSXYGN7VMWPXVAAPATE7":56},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M78MMSXYGN7VMWPXVAAPATE7","planning-disaster-recovery",null,"Execute use when you need to work with backup and recovery.\nThis skill provides backup automation and disaster recovery with comprehensive guidance and automation.\nTrigger with phrases like \"create backups\", \"automate backups\",\nor \"implement disaster recovery\".","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdevops--disaster-recovery-planner--planning-disaster-recovery\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: planning-disaster-recovery\ndescription: |\n  Execute use when you need to work with backup and recovery.\n  This skill provides backup automation and disaster recovery with comprehensive guidance and automation.\n  Trigger with phrases like \"create backups\", \"automate backups\",\n  or \"implement disaster recovery\".\n\nallowed-tools: Read, Write, Edit, Grep, Glob, Bash(tar:*), Bash(rsync:*), Bash(aws:s3:*)\nversion: 1.0.0\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\nlicense: MIT\ncompatible-with: claude-code, codex, openclaw\ntags: [devops, backup, disaster-recovery]\n---\n# Planning Disaster Recovery\n\n## Overview\n\nDesign disaster recovery (DR) plans for cloud infrastructure covering RTO\u002FRPO requirements, multi-region failover, data replication, and automated recovery procedures. Generate runbooks, Terraform for standby infrastructure, and automated failover scripts for databases, compute, and networking.\n\n## Prerequisites\n\n- Complete inventory of production infrastructure components and dependencies\n- Defined RTO (Recovery Time Objective) and RPO (Recovery Point Objective) per service tier\n- Cloud provider CLI authenticated with permissions for multi-region resource management\n- Cross-region networking configured (VPC peering, Transit Gateway, or VPN)\n- Backup and replication mechanisms already in place or planned\n\n## Instructions\n\n1. Catalog all production services with their criticality tier (Tier 1: \u003C 15 min RTO, Tier 2: \u003C 1 hour, Tier 3: \u003C 24 hours)\n2. Map dependencies between services to identify single points of failure and cascading failure paths\n3. Design the DR strategy per tier: active-active for Tier 1, pilot light or warm standby for Tier 2, backup-restore for Tier 3\n4. Generate Terraform for standby region infrastructure: VPC, subnets, security groups, and scaled-down compute\n5. Configure database replication: RDS cross-region read replicas, DynamoDB global tables, or Cloud SQL cross-region replicas\n6. Set up DNS failover using Route 53 health checks, Cloud DNS routing policies, or global load balancers\n7. Create automated failover scripts: promote read replica to primary, update DNS records, scale up standby compute\n8. Document the DR runbook with step-by-step procedures, responsible parties, and communication plans\n9. Schedule quarterly DR drills: simulate region failure, execute the runbook, measure actual RTO\u002FRPO, and document gaps\n10. Set up monitoring for replication lag, backup freshness, and standby infrastructure health\n\n## Output\n\n- DR plan document with service tiers, RTO\u002FRPO targets, and recovery procedures\n- Terraform modules for standby region infrastructure\n- Automated failover scripts (database promotion, DNS switching, compute scaling)\n- DR drill checklist and post-drill assessment template\n- Monitoring dashboards for replication lag and backup status\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|---------|\n| `Replication lag exceeds RPO` | Network throughput insufficient or write volume too high | Increase replication instance size, enable compression, or implement write throttling during peak |\n| `DNS failover not triggering` | Health check misconfigured or TTL too high | Verify health check endpoint returns proper status; reduce DNS TTL to 60 seconds before drill |\n| `Standby database promotion failed` | Replication broken or standby in inconsistent state | Check replication status; if broken, restore from latest snapshot and re-establish replication |\n| `Insufficient capacity in DR region` | Instance types unavailable in standby region | Pre-provision reserved capacity in DR region or use multiple instance type options |\n| `Application cannot connect after failover` | Connection strings hardcoded to primary region endpoints | Use DNS-based endpoints (CNAME\u002FRoute 53) instead of direct IPs; parameterize region in config |\n\n## Examples\n\n- \"Create a disaster recovery plan for a 3-tier web application on AWS with \u003C 15 minute RTO for the API layer and \u003C 1 hour for batch processing.\"\n- \"Generate Terraform for a warm standby in us-west-2 with RDS cross-region read replica, scaled-down ECS cluster, and Route 53 failover routing.\"\n- \"Design a DR drill that simulates primary region failure, executes automated failover, and validates data integrity in the standby region.\"\n\n## Resources\n\n- AWS Disaster Recovery: https:\u002F\u002Fdocs.aws.amazon.com\u002Fwhitepapers\u002Flatest\u002Fdisaster-recovery-workloads-on-aws\u002F\n- GCP DR planning: https:\u002F\u002Fcloud.google.com\u002Farchitecture\u002Fdr-scenarios-planning-guide\n- Azure Business Continuity: https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fazure\u002Freliability\u002F\n- DR strategy patterns: https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Farchitecture\u002Fdisaster-recovery-dr-architecture-on-aws-part-i\u002F","# Planning Disaster Recovery\n\n## Overview\n\nDesign disaster recovery (DR) plans for cloud infrastructure covering RTO\u002FRPO requirements, multi-region failover, data replication, and automated recovery procedures. Generate runbooks, Terraform for standby infrastructure, and automated failover scripts for databases, compute, and networking.\n\n## Prerequisites\n\n- Complete inventory of production infrastructure components and dependencies\n- Defined RTO (Recovery Time Objective) and RPO (Recovery Point Objective) per service tier\n- Cloud provider CLI authenticated with permissions for multi-region resource management\n- Cross-region networking configured (VPC peering, Transit Gateway, or VPN)\n- Backup and replication mechanisms already in place or planned\n\n## Instructions\n\n1. Catalog all production services with their criticality tier (Tier 1: \u003C 15 min RTO, Tier 2: \u003C 1 hour, Tier 3: \u003C 24 hours)\n2. Map dependencies between services to identify single points of failure and cascading failure paths\n3. Design the DR strategy per tier: active-active for Tier 1, pilot light or warm standby for Tier 2, backup-restore for Tier 3\n4. Generate Terraform for standby region infrastructure: VPC, subnets, security groups, and scaled-down compute\n5. Configure database replication: RDS cross-region read replicas, DynamoDB global tables, or Cloud SQL cross-region replicas\n6. Set up DNS failover using Route 53 health checks, Cloud DNS routing policies, or global load balancers\n7. Create automated failover scripts: promote read replica to primary, update DNS records, scale up standby compute\n8. Document the DR runbook with step-by-step procedures, responsible parties, and communication plans\n9. Schedule quarterly DR drills: simulate region failure, execute the runbook, measure actual RTO\u002FRPO, and document gaps\n10. Set up monitoring for replication lag, backup freshness, and standby infrastructure health\n\n## Output\n\n- DR plan document with service tiers, RTO\u002FRPO targets, and recovery procedures\n- Terraform modules for standby region infrastructure\n- Automated failover scripts (database promotion, DNS switching, compute scaling)\n- DR drill checklist and post-drill assessment template\n- Monitoring dashboards for replication lag and backup status\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|---------|\n| `Replication lag exceeds RPO` | Network throughput insufficient or write volume too high | Increase replication instance size, enable compression, or implement write throttling during peak |\n| `DNS failover not triggering` | Health check misconfigured or TTL too high | Verify health check endpoint returns proper status; reduce DNS TTL to 60 seconds before drill |\n| `Standby database promotion failed` | Replication broken or standby in inconsistent state | Check replication status; if broken, restore from latest snapshot and re-establish replication |\n| `Insufficient capacity in DR region` | Instance types unavailable in standby region | Pre-provision reserved capacity in DR region or use multiple instance type options |\n| `Application cannot connect after failover` | Connection strings hardcoded to primary region endpoints | Use DNS-based endpoints (CNAME\u002FRoute 53) instead of direct IPs; parameterize region in config |\n\n## Examples\n\n- \"Create a disaster recovery plan for a 3-tier web application on AWS with \u003C 15 minute RTO for the API layer and \u003C 1 hour for batch processing.\"\n- \"Generate Terraform for a warm standby in us-west-2 with RDS cross-region read replica, scaled-down ECS cluster, and Route 53 failover routing.\"\n- \"Design a DR drill that simulates primary region failure, executes automated failover, and validates data integrity in the standby region.\"\n\n## Resources\n\n- AWS Disaster Recovery: https:\u002F\u002Fdocs.aws.amazon.com\u002Fwhitepapers\u002Flatest\u002Fdisaster-recovery-workloads-on-aws\u002F\n- GCP DR planning: https:\u002F\u002Fcloud.google.com\u002Farchitecture\u002Fdr-scenarios-planning-guide\n- Azure Business Continuity: https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fazure\u002Freliability\u002F\n- DR strategy patterns: https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Farchitecture\u002Fdisaster-recovery-dr-architecture-on-aws-part-i\u002F",{"name":5,"tags":24,"author":28,"license":15,"version":29,"description":30,"allowed-tools":31,"compatible-with":32},[25,26,27],"devops","backup","disaster-recovery","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Execute use when you need to work with backup and recovery.\nThis skill provides backup automation and disaster recovery with comprehensive guidance and automation.\nTrigger with phrases like \"create backups\", \"automate backups\",\nor \"implement disaster recovery\".\n","Read, Write, Edit, Grep, Glob, Bash(tar:*), Bash(rsync:*), Bash(aws:s3:*)","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fdevops--disaster-recovery-planner--planning-disaster-recovery",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill planning-disaster-recovery",{"tool":48,"command":49},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill planning-disaster-recovery",{"tool":51,"command":52},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill planning-disaster-recovery","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdevops--disaster-recovery-planner--planning-disaster-recovery\u002FSKILL.md",true,[],[57,64,71,78,85,93],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]