[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MMW22VBJKHN9SC1BNTACWP":3,"skill-same:01M6MMW22VBJKHN9SC1BNTACWP":65},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M6MMW22VBJKHN9SC1BNTACWP","google-cloud-waf-reliability",null,"Generates reliability-focused guidance for Google Cloud workloads based on the design principles and recommendations in the Google Cloud Well-Architected Framework. Use this skill to evaluate a workload, identify reliability requirements, and provide actionable recommendations for build, deploy, and manage the workload reliably in Google Cloud.","arkhe-genesis\u002FArkhe-OS","arkhe-genesis","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F272629719?v=4","01M6KJDTSTJD2AD5RFPVZNGYCP","Rafael Oliveira","01M6KJDTXSTA997KDK184EA55A",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgoogle-cloud-waf-reliability\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"google","google cloud","google cloud waf reliability","cloud","waf","reliability","evaluate","design","for","principles","actionable","recommendations","requirements","build","manage","design principles","guidance","use","workload","deploy","2026-11-10 10:12:30",false,"---\nname: google-cloud-waf-reliability\ndescription: Generates reliability-focused guidance for Google Cloud workloads based on the design principles and recommendations in the Google Cloud Well-Architected Framework. Use this skill to evaluate a workload, identify reliability requirements, and provide actionable recommendations for build, deploy, and manage the workload reliably in Google Cloud.\n---\n\n# Google Cloud Well-Architected Framework skill for the Reliability pillar\n\n## Overview\n\nThe Reliability pillar of the Google Cloud Well-Architected Framework provides\nprinciples and recommendations to help you design, deploy, and manage reliable,\nresilient, and highly available workloads in Google Cloud. A reliable system\nconsistently performs its intended functions under defined conditions, is\nresilient to failures, and recovers gracefully from disruptions, thereby\nminimizing downtime, enhancing user experience, and ensuring data integrity.\n\n## Core principles\n\nThe recommendations in the reliability pillar of the Well-Architected Framework\nare aligned with the following core principles:\n\n-  **Define reliability based on user-experience goals**: Measurement of\n   reliability should reflect the actual experience of the system's users rather\n   than merely relying on infrastructure metrics. Focus on outcomes that matter\n   most to users. Grounding document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fdefine-reliability-based-on-user-experience-goals\n\n-  **Set realistic targets for reliability**: Determine appropriate Service\n   Level Objectives (SLOs) that balance the cost and complexity of maximizing\n   availability against business requirements. Utilize error budgets to manage\n   feature velocity. Grounding document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fset-targets\n\n-  **Build highly available systems through resource redundancy**: Eliminate\n   single points of failure by duplicating critical components across zones and\n   regions to maintain operations during localized outages. Grounding document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fbuild-highly-available-systems\n\n-  **Take advantage of horizontal scalability**: Design system architectures to\n   scale horizontally (adding more instances) to seamlessly accommodate load\n   fluctuations and improve overall fault tolerance. Grounding document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fhorizontal-scalability\n\n-  **Detect potential failures by using observability**: Implement thorough\n   monitoring, logging, and alerting systems to proactively detect, diagnose,\n   and address anomalies before they cause user-facing issues. Grounding\n   document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fobservability\n\n-  **Design for graceful degradation**: Architect systems to maintain critical\n   functionality, even if at reduced performance or with limited features, when\n   dependencies fail or the system experiences extreme stress. Grounding\n   document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fgraceful-degradation\n\n-  **Perform testing for recovery from failures**: Build confidence in system\n   resilience by continuously simulating failures and verifying the\n   effectiveness of automated and manual recovery procedures. Grounding\n   document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fperform-testing-for-recovery-from-failures\n\n-  **Perform testing for recovery from data loss**: Regularly test backup and\n   restore protocols to ensure rapid recovery from data corruption or loss,\n   remaining within the defined Recovery Time Objective (RTO) and Recovery Point\n   Objective (RPO). Grounding document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fperform-testing-for-recovery-from-data-loss\n\n-  **Conduct thorough postmortems**: Foster a blameless culture by investigating\n   outages comprehensively to understand root causes, followed by implementing\n   measures that prevent recurrence. Grounding document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fconduct-postmortems\n\n## Relevant Google Cloud products\n\nThe following are _examples_ of Google Cloud products and features that are\nrelevant to reliability:\n\n- **Compute**: Compute Engine Managed Instance Groups (MIGs), Google Kubernetes\n  Engine (GKE), Cloud Run\n- **Networking**: Cloud Load Balancing, Cloud CDN, Cloud DNS\n- **Storage and databases**: Cloud Storage (multi-region), Cloud SQL High\n  Availability, Spanner, Filestore, Firestore\n- **Operations**: Cloud Monitoring, Cloud Logging, Google Cloud Managed Service\n  for Prometheus\n- **Disaster recovery**: Backup and DR Service, Filestore backups\n\n## Workload assessment questions\n\nAsk appropriate questions to understand the reliability-related requirements and\nconstraints of the workload and the user's organization. Choose questions from\nthe following list:\n\n- How does your organization define and measure the reliability of your systems\n  in relation to user experience?\n- How does your organization approach setting reliability targets for your\n  services?\n- What is your organization's strategy for ensuring high availability through\n  resource redundancy?\n- How does your organization leverage horizontal scalability to maintain\n  performance and reliability?\n- How does your organization utilize observability (metrics, logs, traces) to\n  gain insights and detect potential failures?\n- How does your organization manage alerting based on observability data to\n  ensure timely responses to significant issues without causing alert fatigue?\n- What measures does your organization take to ensure systems can gracefully\n  degrade during high load or partial failures?\n- How frequently and comprehensively does your organization test for recovery\n  from system failures (e.g., regional failovers, release rollbacks)?\n- What is your organization's approach to testing for recovery from data loss?\n- How does your organization conduct and utilize postmortems after incidents?\n\n## Validation checklist\n\nUse the following checklist to evaluate the architecture's alignment with\nreliability recommendations:\n\n- User-focused SLIs and SLOs are explicitly defined and actively monitored.\n- The architecture avoids single points of failure through cross-zone or\n  cross-region redundancy.\n- Autoscaling is enabled to handle variable demand without manual intervention.\n- Application and infrastructure health checks are configured to trigger\n  automated failovers.\n- Regular backup schedules are in place, and restoration processes are routinely\n  tested.\n- The system architecture incorporates patterns like circuit breakers, retries\n  with exponential backoff, and rate limiting to support graceful degradation.\n- Game days or chaos engineering practices are regularly held to validate\n  failure recovery.\n- A formalized, blameless postmortem process exists to ensure organizational\n  learning from operational incidents.\n","# Google Cloud Well-Architected Framework skill for the Reliability pillar\n\n## Overview\n\nThe Reliability pillar of the Google Cloud Well-Architected Framework provides\nprinciples and recommendations to help you design, deploy, and manage reliable,\nresilient, and highly available workloads in Google Cloud. A reliable system\nconsistently performs its intended functions under defined conditions, is\nresilient to failures, and recovers gracefully from disruptions, thereby\nminimizing downtime, enhancing user experience, and ensuring data integrity.\n\n## Core principles\n\nThe recommendations in the reliability pillar of the Well-Architected Framework\nare aligned with the following core principles:\n\n-  **Define reliability based on user-experience goals**: Measurement of\n   reliability should reflect the actual experience of the system's users rather\n   than merely relying on infrastructure metrics. Focus on outcomes that matter\n   most to users. Grounding document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fdefine-reliability-based-on-user-experience-goals\n\n-  **Set realistic targets for reliability**: Determine appropriate Service\n   Level Objectives (SLOs) that balance the cost and complexity of maximizing\n   availability against business requirements. Utilize error budgets to manage\n   feature velocity. Grounding document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fset-targets\n\n-  **Build highly available systems through resource redundancy**: Eliminate\n   single points of failure by duplicating critical components across zones and\n   regions to maintain operations during localized outages. Grounding document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fbuild-highly-available-systems\n\n-  **Take advantage of horizontal scalability**: Design system architectures to\n   scale horizontally (adding more instances) to seamlessly accommodate load\n   fluctuations and improve overall fault tolerance. Grounding document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fhorizontal-scalability\n\n-  **Detect potential failures by using observability**: Implement thorough\n   monitoring, logging, and alerting systems to proactively detect, diagnose,\n   and address anomalies before they cause user-facing issues. Grounding\n   document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fobservability\n\n-  **Design for graceful degradation**: Architect systems to maintain critical\n   functionality, even if at reduced performance or with limited features, when\n   dependencies fail or the system experiences extreme stress. Grounding\n   document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fgraceful-degradation\n\n-  **Perform testing for recovery from failures**: Build confidence in system\n   resilience by continuously simulating failures and verifying the\n   effectiveness of automated and manual recovery procedures. Grounding\n   document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fperform-testing-for-recovery-from-failures\n\n-  **Perform testing for recovery from data loss**: Regularly test backup and\n   restore protocols to ensure rapid recovery from data corruption or loss,\n   remaining within the defined Recovery Time Objective (RTO) and Recovery Point\n   Objective (RPO). Grounding document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fperform-testing-for-recovery-from-data-loss\n\n-  **Conduct thorough postmortems**: Foster a blameless culture by investigating\n   outages comprehensively to understand root causes, followed by implementing\n   measures that prevent recurrence. Grounding document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fconduct-postmortems\n\n## Relevant Google Cloud products\n\nThe following are _examples_ of Google Cloud products and features that are\nrelevant to reliability:\n\n- **Compute**: Compute Engine Managed Instance Groups (MIGs), Google Kubernetes\n  Engine (GKE), Cloud Run\n- **Networking**: Cloud Load Balancing, Cloud CDN, Cloud DNS\n- **Storage and databases**: Cloud Storage (multi-region), Cloud SQL High\n  Availability, Spanner, Filestore, Firestore\n- **Operations**: Cloud Monitoring, Cloud Logging, Google Cloud Managed Service\n  for Prometheus\n- **Disaster recovery**: Backup and DR Service, Filestore backups\n\n## Workload assessment questions\n\nAsk appropriate questions to understand the reliability-related requirements and\nconstraints of the workload and the user's organization. Choose questions from\nthe following list:\n\n- How does your organization define and measure the reliability of your systems\n  in relation to user experience?\n- How does your organization approach setting reliability targets for your\n  services?\n- What is your organization's strategy for ensuring high availability through\n  resource redundancy?\n- How does your organization leverage horizontal scalability to maintain\n  performance and reliability?\n- How does your organization utilize observability (metrics, logs, traces) to\n  gain insights and detect potential failures?\n- How does your organization manage alerting based on observability data to\n  ensure timely responses to significant issues without causing alert fatigue?\n- What measures does your organization take to ensure systems can gracefully\n  degrade during high load or partial failures?\n- How frequently and comprehensively does your organization test for recovery\n  from system failures (e.g., regional failovers, release rollbacks)?\n- What is your organization's approach to testing for recovery from data loss?\n- How does your organization conduct and utilize postmortems after incidents?\n\n## Validation checklist\n\nUse the following checklist to evaluate the architecture's alignment with\nreliability recommendations:\n\n- User-focused SLIs and SLOs are explicitly defined and actively monitored.\n- The architecture avoids single points of failure through cross-zone or\n  cross-region redundancy.\n- Autoscaling is enabled to handle variable demand without manual intervention.\n- Application and infrastructure health checks are configured to trigger\n  automated failovers.\n- Regular backup schedules are in place, and restoration processes are routinely\n  tested.\n- The system architecture incorporates patterns like circuit breakers, retries\n  with exponential backoff, and rate limiting to support graceful degradation.\n- Game days or chaos engineering practices are regularly held to validate\n  failure recovery.\n- A formalized, blameless postmortem process exists to ensure organizational\n  learning from operational incidents.\n",{"name":5,"description":7},"main","74cd3c4137064fdcde71ed9fe5c4bff58921d899",".agents\u002Fskills\u002Fgoogle-cloud-waf-reliability",0,"https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS","https:\u002F\u002Fgithub.com\u002Farkhe-genesis","2026-11-08 09:08:55",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add arkhe-genesis\u002FArkhe-OS --skill google-cloud-waf-reliability",{"tool":57,"command":58},"bunx","bunx skills add arkhe-genesis\u002FArkhe-OS --skill google-cloud-waf-reliability",{"tool":60,"command":61},"pnpm","pnpm dlx skills add arkhe-genesis\u002FArkhe-OS --skill google-cloud-waf-reliability","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgoogle-cloud-waf-reliability\u002FSKILL.md",true,[],[66,88,106,127,150,169],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":39},"01M6MN97RPP1Q9BG489WHW70R8","career-ops","AI job search command center -- evaluate offers, generate CVs, scan portals, track applications","https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Ftools\u002F.ai-integrations\u002Fvscode\u002F.claude\u002Fskills\u002Fcareer-ops\u002FSKILL.md",[],[73,74,75,76,77,25,78,79,80,81,82,83,84,85,86,87],"ops","career","career ops","track","applications","mode","true","command center","cvs","scan","command","offers","Job Search","search","generate",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":39},"01M6MN93GFX8W9J1PCKDKZVD3N","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Ftools\u002F.agents\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[95,96,36,97,98,99,100,101,79,102,103,104,105],"zoom out","zoom","how","context","code","it","perspective","re","you","with","understand",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":117,"publishedAt":39},"01M6MN8Y2ETBC91BGREF4D39JH","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.","https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Ftools\u002F.agents\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[112],{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[118,119,120,104,121,122,123,124,32,36,125,126],"write","write a skill","progressive disclosure","resources","new agent","structure","new skill","user","create",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":134,"publishedAt":39},"01M6MN8RWE2V2PPFVPD0G8FHKF","triage","Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.","https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Ftools\u002F.agents\u002Fskills\u002Ftriage\u002FSKILL.md",[133],{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},[129,135,136,126,137,138,139,140,141,33,142,36,143,144,27,145,146,147,148,149],"bugs","state machine","requests","machine","feature","roles","issue workflow","issue","issues","state","feature requests","prepare","triage issues","workflow","review",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":161,"publishedAt":39},"01M6MN8KVDBD28672WMER7HPXM","to-prd","Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.","https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Ftools\u002F.agents\u002Fskills\u002Fto-prd\u002FSKILL.md",[156],{"categoryNo":157,"categoryName":158,"taxonomyType":159,"taxonomyTypeDesc":160},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[162,163,36,125,98,164,126,142,165,100,166,167,168],"to prd","prd","publish","issue tracker","project","conversation","tracker",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":175,"publishedAt":39},"01M6MN8E9CGYVWVDDR0NJEFDBB","to-issues","Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.","https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Ftools\u002F.agents\u002Fskills\u002Fto-issues\u002FSKILL.md",[],[143,176,177,166,178,179,165,180,181,168,142,182,36,125,183,184,185,163,126],"to issues","spec","down","break","break down","tickets","implementation","work","convert","plan"]