[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AEKKMDA061291HVM8TMNBS":3,"skill-same:01M6AEKKMDA061291HVM8TMNBS":75},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6AEKKMDA061291HVM8TMNBS","google-cloud-waf-cost-optimization",null,"Generates cost optimization guidance for Google Cloud workloads based on the Google Cloud Well-Architected Framework (WAF). Use to evaluate a workload, identify cost requirements and constraints, and provide actionable recommendations for building cost-efficient workloads on Google Cloud.","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-cost-optimization\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"google cloud","cost","Optimization","waf","cloud","cost optimization","google cloud waf cost optimization","google","framework","apache","workload","constraints","use","guidance","requirements","recommendations","actionable","for","evaluate","2026-11-10 10:12:30",false,"---\nname: google-cloud-waf-cost-optimization\ndescription: Generates cost optimization guidance for Google Cloud workloads based on the Google Cloud Well-Architected Framework (WAF). Use to evaluate a workload, identify cost requirements and constraints, and provide actionable recommendations for building cost-efficient workloads on Google Cloud.\nmetadata:\n  source: google\u002Fskills (Apache 2.0)\n---\n\n# Google Cloud Well-Architected Framework skill for the Cost Optimization pillar\n\n## Overview\n\nThe Cost Optimization pillar of the Google Cloud Well-Architected Framework\nprovides a structured approach to optimize the costs of your cloud workloads\nwhile maximizing business value. Cloud costs differ significantly from\non-premises capital expenditure (CapEx) models, requiring a shift to operational\nexpenditure (OpEx) management and a culture of accountability (FinOps).\n\n## Core principles\n\nThe recommendations in the cost optimization pillar of the Well-Architected\nFramework are aligned with the following core principles:\n\n-  **Align cloud spending with business value**: Ensure that your cloud\n   resources deliver measurable business value by aligning IT spending with\n   business objectives. Prioritize investments that directly contribute to\n   revenue, customer satisfaction, or operational efficiency. Grounding\n   document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Fcost-optimization\u002Falign-cloud-spending-business-value\n\n-  **Foster a culture of cost awareness**: Ensure that people across your\n   organization consider the cost impact of their decisions and activities.\n   Provide teams with the visibility and information they need to make informed,\n   cost-conscious choices. Grounding document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Fcost-optimization\u002Ffoster-culture-cost-awareness\n\n-  **Optimize resource usage**: Provision only the resources that you need and\n   pay only for what you consume. Select the most cost-effective resource types,\n   sizes, and locations that meet your technical and business requirements.\n   Grounding document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Fcost-optimization\u002Foptimize-resource-usage\n\n-  **Optimize continuously**: Continuously monitor your cloud resource usage and\n   costs, and proactively make adjustments as needed to optimize your spending.\n   This iterative approach helps identify and address inefficiencies before they\n   become significant. Grounding document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Fcost-optimization\u002Foptimize-continuously\n\n## Relevant Google Cloud products\n\nThe following are _examples_ of Google Cloud products and features that are\nrelevant to cost optimization:\n\n- **Visibility and monitoring**:\n\n  - **Cloud Billing reports**: Native dashboards for visualizing spending and\n    trends.\n  - **BigQuery billing export**: Enables granular, custom analysis of billing\n    data using SQL and BI tools.\n  - **Looker Studio**: Used for creating detailed, shared cost dashboards and\n    reports.\n  - **Billing alerts and budgets**: Automated notifications when spending\n    reaches predefined thresholds.\n\n- **Automation and optimization tools**:\n\n  - **Recommender \u002F Active Assist**: Automatically identifies idle resources,\n    rightsizing opportunities, and unused commitments.\n  - **Cloud Hub Optimization**: Integrates billing and resource utilization data\n    to help developers and application owners quickly identify their most\n    expensive, fluctuating, or underutilized cloud resources.\n  - **FinOps hub**: Presents active savings and optimization opportunities in\n    one dashboard.\n  - **Billing quotas**: Limits on resource consumption to prevent unexpected\n    cost spikes.\n\n- **Efficient infrastructure**:\n\n  - **Managed services and serverless services**: Services like Cloud Run, Cloud\n    Run functions, and GKE Autopilot reduce operational overhead and pay-per-use\n    scaling.\n  - **Compute Engine**: Use of Spot VMs for fault-tolerant workloads and\n    Committed Use Discounts (CUDs) for stable workloads.\n  - **Cloud Storage Lifecycle Policies**: Automatically moves data to lower-cost\n    storage classes (Nearline, Coldline, Archive) based on age or access.\n\n- **Organization and governance**:\n\n  - **Resource Manager**: Logical structure (Organizations, Folders, Projects)\n    for cost attribution.\n  - **Labels**: Metadata tags for categorizing and filtering costs by\n    environment, team, or application.\n  - **Organization Policy Service**: Enforces constraints (e.g., restricted\n    regions or machine types) to control costs.\n\n## Workload assessment questions\n\nAsk appropriate questions to understand the cost-related requirements and\nconstraints of the workload and the user's organization. Choose questions from\nthe following list:\n\n- How do you incorporate cost considerations into your cloud architecture design\n  process?\n- How do you foster a culture of cost awareness among your development teams?\n- How do you monitor and manage cloud costs across different projects or\n  departments?\n- What strategies do you use to optimize the cost of your compute resources?\n- How do you balance cost optimization with the need for agility and innovation?\n- How do you ensure that you are not over-provisioning cloud resources?\n- How do you use data and analytics to drive cost optimization decisions?\n- How do you optimize costs in different environments (e.g., development,\n  testing, production)?\n- How do you ensure that your cost optimization efforts are sustainable and\n  ongoing?\n- How do you measure the success of your cloud cost optimization initiatives?\n\n## Validation checklist\n\nUse the following checklist to evaluate the architecture's alignment with\ncost-optimization recommendations:\n\n- **Cost Attribution**: 100% of resources are labeled with key metadata\n  (e.g., `env`, `team`, `app`).\n- **Granular Visibility**: BigQuery billing export is enabled and used for\n  regular cost reviews.\n- **Budgets and Alerts**: Every project or business unit has defined budgets\n  and active alerts.\n- **Rightsizing**: Resources are regularly adjusted based on rightsizing\n  suggestions provided by Active Assist Recommender.\n- **Commitment Strategy**: Spend is reviewed monthly to optimize Committed\n  Use Discount coverage.\n- **Idle Resource Management**: Unused disks, IP addresses, and idle VMs are\n  identified and removed monthly.\n- **Managed Services**: Serverless options are preferred for new workloads\n  unless specific technical constraints exist.\n- **Storage Tiers**: Lifecycle policies are active for all major storage\n  buckets to minimize archival costs.\n","# Google Cloud Well-Architected Framework skill for the Cost Optimization pillar\n\n## Overview\n\nThe Cost Optimization pillar of the Google Cloud Well-Architected Framework\nprovides a structured approach to optimize the costs of your cloud workloads\nwhile maximizing business value. Cloud costs differ significantly from\non-premises capital expenditure (CapEx) models, requiring a shift to operational\nexpenditure (OpEx) management and a culture of accountability (FinOps).\n\n## Core principles\n\nThe recommendations in the cost optimization pillar of the Well-Architected\nFramework are aligned with the following core principles:\n\n-  **Align cloud spending with business value**: Ensure that your cloud\n   resources deliver measurable business value by aligning IT spending with\n   business objectives. Prioritize investments that directly contribute to\n   revenue, customer satisfaction, or operational efficiency. Grounding\n   document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Fcost-optimization\u002Falign-cloud-spending-business-value\n\n-  **Foster a culture of cost awareness**: Ensure that people across your\n   organization consider the cost impact of their decisions and activities.\n   Provide teams with the visibility and information they need to make informed,\n   cost-conscious choices. Grounding document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Fcost-optimization\u002Ffoster-culture-cost-awareness\n\n-  **Optimize resource usage**: Provision only the resources that you need and\n   pay only for what you consume. Select the most cost-effective resource types,\n   sizes, and locations that meet your technical and business requirements.\n   Grounding document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Fcost-optimization\u002Foptimize-resource-usage\n\n-  **Optimize continuously**: Continuously monitor your cloud resource usage and\n   costs, and proactively make adjustments as needed to optimize your spending.\n   This iterative approach helps identify and address inefficiencies before they\n   become significant. Grounding document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Fcost-optimization\u002Foptimize-continuously\n\n## Relevant Google Cloud products\n\nThe following are _examples_ of Google Cloud products and features that are\nrelevant to cost optimization:\n\n- **Visibility and monitoring**:\n\n  - **Cloud Billing reports**: Native dashboards for visualizing spending and\n    trends.\n  - **BigQuery billing export**: Enables granular, custom analysis of billing\n    data using SQL and BI tools.\n  - **Looker Studio**: Used for creating detailed, shared cost dashboards and\n    reports.\n  - **Billing alerts and budgets**: Automated notifications when spending\n    reaches predefined thresholds.\n\n- **Automation and optimization tools**:\n\n  - **Recommender \u002F Active Assist**: Automatically identifies idle resources,\n    rightsizing opportunities, and unused commitments.\n  - **Cloud Hub Optimization**: Integrates billing and resource utilization data\n    to help developers and application owners quickly identify their most\n    expensive, fluctuating, or underutilized cloud resources.\n  - **FinOps hub**: Presents active savings and optimization opportunities in\n    one dashboard.\n  - **Billing quotas**: Limits on resource consumption to prevent unexpected\n    cost spikes.\n\n- **Efficient infrastructure**:\n\n  - **Managed services and serverless services**: Services like Cloud Run, Cloud\n    Run functions, and GKE Autopilot reduce operational overhead and pay-per-use\n    scaling.\n  - **Compute Engine**: Use of Spot VMs for fault-tolerant workloads and\n    Committed Use Discounts (CUDs) for stable workloads.\n  - **Cloud Storage Lifecycle Policies**: Automatically moves data to lower-cost\n    storage classes (Nearline, Coldline, Archive) based on age or access.\n\n- **Organization and governance**:\n\n  - **Resource Manager**: Logical structure (Organizations, Folders, Projects)\n    for cost attribution.\n  - **Labels**: Metadata tags for categorizing and filtering costs by\n    environment, team, or application.\n  - **Organization Policy Service**: Enforces constraints (e.g., restricted\n    regions or machine types) to control costs.\n\n## Workload assessment questions\n\nAsk appropriate questions to understand the cost-related requirements and\nconstraints of the workload and the user's organization. Choose questions from\nthe following list:\n\n- How do you incorporate cost considerations into your cloud architecture design\n  process?\n- How do you foster a culture of cost awareness among your development teams?\n- How do you monitor and manage cloud costs across different projects or\n  departments?\n- What strategies do you use to optimize the cost of your compute resources?\n- How do you balance cost optimization with the need for agility and innovation?\n- How do you ensure that you are not over-provisioning cloud resources?\n- How do you use data and analytics to drive cost optimization decisions?\n- How do you optimize costs in different environments (e.g., development,\n  testing, production)?\n- How do you ensure that your cost optimization efforts are sustainable and\n  ongoing?\n- How do you measure the success of your cloud cost optimization initiatives?\n\n## Validation checklist\n\nUse the following checklist to evaluate the architecture's alignment with\ncost-optimization recommendations:\n\n- **Cost Attribution**: 100% of resources are labeled with key metadata\n  (e.g., `env`, `team`, `app`).\n- **Granular Visibility**: BigQuery billing export is enabled and used for\n  regular cost reviews.\n- **Budgets and Alerts**: Every project or business unit has defined budgets\n  and active alerts.\n- **Rightsizing**: Resources are regularly adjusted based on rightsizing\n  suggestions provided by Active Assist Recommender.\n- **Commitment Strategy**: Spend is reviewed monthly to optimize Committed\n  Use Discount coverage.\n- **Idle Resource Management**: Unused disks, IP addresses, and idle VMs are\n  identified and removed monthly.\n- **Managed Services**: Serverless options are preferred for new workloads\n  unless specific technical constraints exist.\n- **Storage Tiers**: Lifecycle policies are active for all major storage\n  buckets to minimize archival costs.\n",{"name":5,"metadata":43,"description":7},{"source":44},"google\u002Fskills (Apache 2.0)","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fgoogle-cloud-waf-cost-optimization",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":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add davila7\u002Fclaude-code-templates --skill google-cloud-waf-cost-optimization",{"tool":61,"command":62},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill google-cloud-waf-cost-optimization",{"tool":64,"command":65},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill google-cloud-waf-cost-optimization","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fgoogle-cloud-waf-cost-optimization\u002FSKILL.md",true,[69],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"reference\u002Fworkflows.md","REFERENCE","参考文档",4245,"https:\u002F\u002Fgithub.com\u002Fmatheusnorjosa\u002Faprender_sistema\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fci-github-actions\u002Freference\u002Fworkflows.md",[76,106,133,166,201,225],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":87,"publishedAt":38},"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",[82],{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[88,89,90,91,92,36,93,94,31,95,96,97,98,99,100,101,102,103,104,105],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","when","reduce","with","record","track","verdict","evm","solana","how","public","look",{"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":113,"publishedAt":38},"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",[112],{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},[114,115,116,117,118,119,120,121,122,123,124,95,125,126,127,128,129,130,131,132],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":148,"publishedAt":38},"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",[139,142,143],{"categoryNo":140,"categoryName":141,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},{"categoryNo":144,"categoryName":145,"taxonomyType":146,"taxonomyTypeDesc":147},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[149,150,151,152,153,154,155,36,156,157,158,159,160,161,162,31,163,164,95,165],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":170,"licenseFileUrl":171,"sourceHtmlUrl":172,"categories":173,"keywords":177,"publishedAt":38},"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",[174],{"categoryNo":175,"categoryName":176,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000009","前端开发",[178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,195,196,197,198,199,36,200],"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":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":170,"licenseFileUrl":205,"sourceHtmlUrl":206,"categories":207,"keywords":212,"publishedAt":38},"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",[208,211],{"categoryNo":209,"categoryName":210,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":175,"categoryName":176,"taxonomyType":85,"taxonomyTypeDesc":86},[213,214,215,216,217,179,218,188,189,219,220,221,222,36,223,97,224],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":226,"name":227,"nameZh":6,"description":228,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":170,"licenseFileUrl":229,"sourceHtmlUrl":230,"categories":231,"keywords":239,"publishedAt":38},"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",[232,235,236],{"categoryNo":233,"categoryName":234,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},{"categoryNo":237,"categoryName":238,"taxonomyType":146,"taxonomyTypeDesc":147},"01JBSEEDCAT000000000000036","内容创作者",[240,241,242,243,244,245,246,247,181,248,191,125,249,250,251,252,253,161,254,95,255,256,257,258,259,103,34],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble"]