[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AEKNGQQ1D9Z2S5PZ37V76T":3,"skill-same:01M6AEKNGQQ1D9Z2S5PZ37V76T":67},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6AEKNGQQ1D9Z2S5PZ37V76T","google-cloud-waf-reliability",null,"Generates reliability-focused guidance for Google Cloud workloads based on the Google Cloud Well-Architected Framework. Use to evaluate a workload, identify reliability requirements, and provide actionable recommendations for building resilient, highly available systems.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33481,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fgoogle-cloud-waf-reliability\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"google cloud","google cloud waf reliability","google","cloud","waf","reliability","evaluate","for","actionable","systems","recommendations","requirements","guidance","use","apache","framework","workload","2026-11-10 10:12:30",false,"---\nname: google-cloud-waf-reliability\ndescription: Generates reliability-focused guidance for Google Cloud workloads based on the Google Cloud Well-Architected Framework. Use to evaluate a workload, identify reliability requirements, and provide actionable recommendations for building resilient, highly available systems.\nmetadata:\n  source: google\u002Fskills (Apache 2.0)\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,"metadata":41,"description":7},{"source":42},"google\u002Fskills (Apache 2.0)","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fgoogle-cloud-waf-reliability",3931,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-14 06:14:46",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add davila7\u002Fclaude-code-templates --skill google-cloud-waf-reliability",{"tool":59,"command":60},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill google-cloud-waf-reliability",{"tool":62,"command":63},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill google-cloud-waf-reliability","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fgoogle-cloud-waf-reliability\u002FSKILL.md",true,[],[68,98,125,158,193,217],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":79,"publishedAt":36},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[74],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[80,81,82,83,84,26,85,86,32,87,88,89,90,91,92,93,94,95,96,97],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","when","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":105,"publishedAt":36},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[104],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},[106,107,108,109,110,111,112,113,114,115,116,87,117,118,119,120,121,122,123,124],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":140,"publishedAt":36},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[131,134,135],{"categoryNo":132,"categoryName":133,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},{"categoryNo":136,"categoryName":137,"taxonomyType":138,"taxonomyTypeDesc":139},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[141,142,143,144,145,146,147,26,148,149,150,151,152,153,154,32,155,156,87,157],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":162,"licenseFileUrl":163,"sourceHtmlUrl":164,"categories":165,"keywords":169,"publishedAt":36},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[166],{"categoryNo":167,"categoryName":168,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000009","前端开发",[170,171,172,173,174,175,176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,26,192],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":162,"licenseFileUrl":197,"sourceHtmlUrl":198,"categories":199,"keywords":204,"publishedAt":36},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[200,203],{"categoryNo":201,"categoryName":202,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":167,"categoryName":168,"taxonomyType":77,"taxonomyTypeDesc":78},[205,206,207,208,209,171,210,180,181,211,212,213,214,26,215,89,216],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":162,"licenseFileUrl":221,"sourceHtmlUrl":222,"categories":223,"keywords":231,"publishedAt":36},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[224,227,228],{"categoryNo":225,"categoryName":226,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},{"categoryNo":229,"categoryName":230,"taxonomyType":138,"taxonomyTypeDesc":139},"01JBSEEDCAT000000000000036","内容创作者",[232,233,234,235,236,237,238,239,173,240,183,117,241,242,243,244,245,153,246,87,247,248,249,250,251,95,29],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble"]