[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79E4B3E66V47PJ361BSTMKB":3,"skill-same:01M79E4B3E66V47PJ361BSTMKB":50},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M79E4B3E66V47PJ361BSTMKB","google-cloud-waf-performance-optimization",null,"Generates performance-focused guidance for Google Cloud workloads based on the design principles and recommendations in the Performance Optimization pillar of the Google Cloud Well-Architected Framework (WAF). Use this skill to evaluate a workload, identify performance requirements, and provide actionable recommendations for resource allocation, modular design, and elasticity.","hamzabellouch\u002Fagent-skills","hamzabellouch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F237856042?v=4","01M79BRYW7XAMK3YDWQEMTWGWS","Hamza Bellouch","01M79BRYWXQV3JK2TGVTX8GN2A",8,"MIT","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FProgramming\u002FCloud_DevOps_and_Infrastructure\u002FGoogle_Cloud_and_GKE\u002Fgoogle-cloud-waf-performance-optimization\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: google-cloud-waf-performance-optimization\nmetadata:\n  category: WellArchitectedFramework\ndescription: >-\n  Generates performance-focused guidance for Google Cloud workloads based on the\n  design principles and recommendations in the Performance Optimization pillar\n  of the Google Cloud Well-Architected Framework (WAF). Use this skill\n  to evaluate a workload, identify performance requirements, and provide\n  actionable recommendations for resource allocation, modular design, and\n  elasticity.\n---\n\n# Google Cloud Well-Architected Framework skill for the Performance Optimization pillar\n\n## Overview\n\nThe Performance Optimization pillar of the Google Cloud Well-Architected\nFramework provides principles and recommendations to help you design, build, and\noperate high-performing workloads. It focuses on efficiently allocating\nresources, leveraging modular architectures, and using data-driven insights to\ncontinuously monitor and improve performance as your business needs evolve.\n\n## Core principles\n\nThe recommendations in the performance optimization pillar of the\nWell-Architected Framework are aligned with the following core principles:\n\n-   **Plan resource allocation**: Carefully select and configure the compute,\n    storage, and networking resources that best match the specific requirements\n    of your workload. Grounding document:\n    https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Fperformance-optimization\u002Fplan-resource-allocation.md.txt\n\n-   **Take advantage of elasticity**: Utilize automated scaling and serverless\n    technologies to dynamically adjust resource capacity in response to\n    real-time demand fluctuations. Grounding document:\n    https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Fperformance-optimization\u002Felasticity.md.txt\n\n-   **Promote modular design**: Architect systems using independent, loosely\n    coupled components to enhance scalability and allow individual parts to be\n    optimized without affecting the entire system. Grounding document:\n    https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Fperformance-optimization\u002Fpromote-modular-design.md.txt\n\n-   **Continuously monitor and improve performance**: Implement robust\n    observability to identify bottlenecks and use performance data to drive\n    iterative enhancements throughout the software development lifecycle.\n    Grounding document:\n    https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Fperformance-optimization\u002Fcontinuously-monitor-and-improve-performance.md.txt\n\n## Relevant Google Cloud products\n\nThe following are _examples_ of Google Cloud products and features that are\nrelevant to performance optimization:\n\n-   **Compute and scaling**\n    -   **Compute Engine (MIGs)**: Managed instance groups that support\n        autoscaling and load balancing for VM-based workloads.\n    -   **Google Kubernetes Engine (GKE)**: Provides container orchestration\n        with horizontal and vertical pod autoscaling.\n    -   **Cloud Run**: A fully managed serverless platform that automatically\n        scales containers to zero or up based on traffic.\n\n-   **Data and caching**\n    -   **Cloud CDN**: Low-latency content delivery network to cache static and\n        dynamic content closer to end-users.\n    -   **Memorystore**: Managed in-memory data store for Valkey and Redis to\n        provide sub-millisecond data access.\n    -   **Bigtable**: NoSQL database service for analytical and operational\n        workloads requiring low latency and high throughput.\n    -   **Spanner**: RDBMS that provides global consistency, high availability,\n        and horizontal scaling for mission-critical transactional applications.\n\n-   **Performance analysis and monitoring**\n    -   **Cloud Trace**: Distributed tracing system that helps identify latency\n        bottlenecks.\n    -   **Cloud Profiler**: Continuous CPU and memory profiling to identify\n        resource-heavy application code.\n    -   **Cloud Monitoring**: Provides dashboards and alerts based on\n        performance KPIs like latency and throughput.\n\n## Workload assessment questions\n\nAsk appropriate questions to understand the performance-related requirements and\nconstraints of the workload and the user's organization. Choose questions from\nthe following list:\n\n-   **Plan resource allocation**\n    -   When initially provisioning compute resources for a new application,\n        which approach do you use to determine the required capacity for\n        expected peak loads?\n    -   Which caching strategies (browser, in-memory, CDN, database) do you\n        utilize to improve performance and responsiveness?\n    -   How do you optimize the performance of your data storage solutions\n        (e.g., SSD vs HDD, storage classes) for your applications?\n\n-   **Promote modular design**\n    -   Which architectural patterns (microservices, asynchronous messaging,\n        stateless servers) do you employ to enhance performance and resilience?\n    -   How do you design your application to minimize the impact of failures in\n        one part of the system on other parts?\n\n-   **Continuously monitor and improve performance**\n    -   How frequently do you review and analyze the performance of your\n        production applications and infrastructure?\n    -   Which tools or techniques (APM, distributed tracing, load testing) do\n        you use to proactively identify and diagnose performance bottlenecks?\n    -   How do you incorporate performance considerations into your software\n        development lifecycle (SDLC)?\n\n-   **Take advantage of elasticity**\n    -   Which methods do you use to manage and optimize the cost of your cloud\n        resources while maintaining performance?\n    -   How do you typically handle sudden spikes in traffic or workload on your\n        applications?\n\n## Validation checklist\n\nUse the following checklist to evaluate the architecture's alignment with\nperformance optimization recommendations:\n\n-   **Resource allocation**\n    -   [ ] Initial provisioning is based on load testing or historical data\n        rather than general estimates.\n    -   [ ] Caching is implemented at multiple layers (CDN, in-memory, or\n        browser) to offload backend systems.\n    -   [ ] Storage types (SSD\u002FHDD) and classes are selected based on the\n        specific I\u002FO requirements of the workload.\n\n-   **Modular design**\n    -   [ ] The architecture uses microservices or decoupled components to allow\n        independent scaling.\n    -   [ ] Circuit breakers or bulkheads are implemented to isolate failures\n        and prevent performance degradation across the system.\n\n-   **Monitoring and continuous improvement**\n    -   [ ] Automated dashboards and alerts are configured for key performance\n        indicators (KPIs).\n    -   [ ] Distributed tracing and profiling tools are used to identify\n        code-level bottlenecks.\n    -   [ ] Performance testing (unit and integration) is integrated into the\n        software development lifecycle.\n\n-   **Elasticity**\n    -   [ ] Auto-scaling rules are configured and validated to handle variable\n        demand.\n    -   [ ] The architecture leverages serverless or managed services to\n        dynamically match capacity to load.\n    -   [ ] Resource utilization is reviewed regularly to eliminate idle\n        overhead and balance cost with performance.\n","# Google Cloud Well-Architected Framework skill for the Performance Optimization pillar\n\n## Overview\n\nThe Performance Optimization pillar of the Google Cloud Well-Architected\nFramework provides principles and recommendations to help you design, build, and\noperate high-performing workloads. It focuses on efficiently allocating\nresources, leveraging modular architectures, and using data-driven insights to\ncontinuously monitor and improve performance as your business needs evolve.\n\n## Core principles\n\nThe recommendations in the performance optimization pillar of the\nWell-Architected Framework are aligned with the following core principles:\n\n-   **Plan resource allocation**: Carefully select and configure the compute,\n    storage, and networking resources that best match the specific requirements\n    of your workload. Grounding document:\n    https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Fperformance-optimization\u002Fplan-resource-allocation.md.txt\n\n-   **Take advantage of elasticity**: Utilize automated scaling and serverless\n    technologies to dynamically adjust resource capacity in response to\n    real-time demand fluctuations. Grounding document:\n    https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Fperformance-optimization\u002Felasticity.md.txt\n\n-   **Promote modular design**: Architect systems using independent, loosely\n    coupled components to enhance scalability and allow individual parts to be\n    optimized without affecting the entire system. Grounding document:\n    https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Fperformance-optimization\u002Fpromote-modular-design.md.txt\n\n-   **Continuously monitor and improve performance**: Implement robust\n    observability to identify bottlenecks and use performance data to drive\n    iterative enhancements throughout the software development lifecycle.\n    Grounding document:\n    https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Fperformance-optimization\u002Fcontinuously-monitor-and-improve-performance.md.txt\n\n## Relevant Google Cloud products\n\nThe following are _examples_ of Google Cloud products and features that are\nrelevant to performance optimization:\n\n-   **Compute and scaling**\n    -   **Compute Engine (MIGs)**: Managed instance groups that support\n        autoscaling and load balancing for VM-based workloads.\n    -   **Google Kubernetes Engine (GKE)**: Provides container orchestration\n        with horizontal and vertical pod autoscaling.\n    -   **Cloud Run**: A fully managed serverless platform that automatically\n        scales containers to zero or up based on traffic.\n\n-   **Data and caching**\n    -   **Cloud CDN**: Low-latency content delivery network to cache static and\n        dynamic content closer to end-users.\n    -   **Memorystore**: Managed in-memory data store for Valkey and Redis to\n        provide sub-millisecond data access.\n    -   **Bigtable**: NoSQL database service for analytical and operational\n        workloads requiring low latency and high throughput.\n    -   **Spanner**: RDBMS that provides global consistency, high availability,\n        and horizontal scaling for mission-critical transactional applications.\n\n-   **Performance analysis and monitoring**\n    -   **Cloud Trace**: Distributed tracing system that helps identify latency\n        bottlenecks.\n    -   **Cloud Profiler**: Continuous CPU and memory profiling to identify\n        resource-heavy application code.\n    -   **Cloud Monitoring**: Provides dashboards and alerts based on\n        performance KPIs like latency and throughput.\n\n## Workload assessment questions\n\nAsk appropriate questions to understand the performance-related requirements and\nconstraints of the workload and the user's organization. Choose questions from\nthe following list:\n\n-   **Plan resource allocation**\n    -   When initially provisioning compute resources for a new application,\n        which approach do you use to determine the required capacity for\n        expected peak loads?\n    -   Which caching strategies (browser, in-memory, CDN, database) do you\n        utilize to improve performance and responsiveness?\n    -   How do you optimize the performance of your data storage solutions\n        (e.g., SSD vs HDD, storage classes) for your applications?\n\n-   **Promote modular design**\n    -   Which architectural patterns (microservices, asynchronous messaging,\n        stateless servers) do you employ to enhance performance and resilience?\n    -   How do you design your application to minimize the impact of failures in\n        one part of the system on other parts?\n\n-   **Continuously monitor and improve performance**\n    -   How frequently do you review and analyze the performance of your\n        production applications and infrastructure?\n    -   Which tools or techniques (APM, distributed tracing, load testing) do\n        you use to proactively identify and diagnose performance bottlenecks?\n    -   How do you incorporate performance considerations into your software\n        development lifecycle (SDLC)?\n\n-   **Take advantage of elasticity**\n    -   Which methods do you use to manage and optimize the cost of your cloud\n        resources while maintaining performance?\n    -   How do you typically handle sudden spikes in traffic or workload on your\n        applications?\n\n## Validation checklist\n\nUse the following checklist to evaluate the architecture's alignment with\nperformance optimization recommendations:\n\n-   **Resource allocation**\n    -   [ ] Initial provisioning is based on load testing or historical data\n        rather than general estimates.\n    -   [ ] Caching is implemented at multiple layers (CDN, in-memory, or\n        browser) to offload backend systems.\n    -   [ ] Storage types (SSD\u002FHDD) and classes are selected based on the\n        specific I\u002FO requirements of the workload.\n\n-   **Modular design**\n    -   [ ] The architecture uses microservices or decoupled components to allow\n        independent scaling.\n    -   [ ] Circuit breakers or bulkheads are implemented to isolate failures\n        and prevent performance degradation across the system.\n\n-   **Monitoring and continuous improvement**\n    -   [ ] Automated dashboards and alerts are configured for key performance\n        indicators (KPIs).\n    -   [ ] Distributed tracing and profiling tools are used to identify\n        code-level bottlenecks.\n    -   [ ] Performance testing (unit and integration) is integrated into the\n        software development lifecycle.\n\n-   **Elasticity**\n    -   [ ] Auto-scaling rules are configured and validated to handle variable\n        demand.\n    -   [ ] The architecture leverages serverless or managed services to\n        dynamically match capacity to load.\n    -   [ ] Resource utilization is reviewed regularly to eliminate idle\n        overhead and balance cost with performance.\n",{"name":5,"metadata":24,"description":7},{"category":25},"WellArchitectedFramework","main","e905af21e5f1e1c3ca605e9656c3a7930360a84e","Programming\u002FCloud_DevOps_and_Infrastructure\u002FGoogle_Cloud_and_GKE\u002Fgoogle-cloud-waf-performance-optimization",1,"https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills","https:\u002F\u002Fhamzabellouch.github.io\u002F","https:\u002F\u002Fgithub.com\u002Fhamzabellouch","hamzabellouch.github.io","CEO & Founder of @tknoglobal | Researcher in Technology & Applied Sciences.","2026-10-17 03:20:19",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add hamzabellouch\u002Fagent-skills --skill google-cloud-waf-performance-optimization",{"tool":42,"command":43},"bunx","bunx skills add hamzabellouch\u002Fagent-skills --skill google-cloud-waf-performance-optimization",{"tool":45,"command":46},"pnpm","pnpm dlx skills add hamzabellouch\u002Fagent-skills --skill google-cloud-waf-performance-optimization","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FProgramming\u002FCloud_DevOps_and_Infrastructure\u002FGoogle_Cloud_and_GKE\u002Fgoogle-cloud-waf-performance-optimization\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M79FHH2H815A9TAP6WNKH4Q8","security-audit","Comprehensive security guidance, source code audit, vulnerability assessment, and penetration test review for codebases, APIs, microservices, CLI tools, libraries, and LLM-backed applications. Triggers on requests to audit a codebase, conduct security reviews, find vulnerabilities or flaws, pen-test source code, or when the user asks in Arabic (فحص أمني، تدقيق الكود أمنياً، مراجعة الثغرات، فحص أمان المشروع). Supports Guidance mode (focused review) and Full Audit mode (deterministic 6-phase harness).","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FSecurity_Audit_and_Code_Review\u002Fsecurity-audit\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M79FHBGXVBY6VQ1X7ETAZMF1","malware-analysis-reversing","Production malware analysis workflows, reverse engineering methodologies, isolated sandbox triage, static\u002Fdynamic binary analysis, memory forensics, and YARA detection rule authoring.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FOffensive_Security_and_Pentesting\u002Fmalware-analysis-reversing\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M79FH6EACDR801TZCE4R8SAC","application-security-pentesting","Production Application Security (AppSec) standards, OWASP Top 10 vulnerability remediation, SAST\u002FDAST pipeline integration, secure code review, threat modeling, and defensive security posture.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FOffensive_Security_and_Pentesting\u002Fapplication-security-pentesting\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M79FH0VKVT44FK923K520ZQA","oauth2-oidc-security-flows","Implement enterprise OAuth 2.1 and OpenID Connect (OIDC) authorization code flow with Proof Key for Code Exchange (PKCE), state and nonce verification, refresh token rotation, token revocation, and centralized IdP federation (Keycloak, Auth0, Okta). Trigger when building secure authentication, single sign-on (SSO), or third-party delegated authorization.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FIdentity_and_Access_Management_IAM\u002Foauth2-oidc-security-flows\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M79FGVVB3R4T88XXD8FRSV5B","jwt-session-management-hardening","Harden JWT-based authentication and session lifecycles using asymmetric signing (RS256\u002FEdDSA), JWKS rotation, strict claims validation, Redis-backed sliding window sessions, revocation lists, and secure HttpOnly cookie storage. Trigger when implementing token validation, session revocation, or hardening API authentication.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FIdentity_and_Access_Management_IAM\u002Fjwt-session-management-hardening\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M79FGNCPZ85CVEY0B3NE4H3B","soc2-compliance-automation","Best practices for implementing SOC 2 Type II compliance controls, continuous evidence collection, infrastructure policy-as-code, and automated security monitoring. Use when automating Trust Services Criteria (Security, Availability, Confidentiality, Processing Integrity, Privacy), audit logging, IAM least privilege, or CI\u002FCD security gates.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FGovernance_Compliance_and_Legal_Tech\u002Fsoc2-compliance-automation\u002FSKILL.md",[],[]]