本文へ移動
cccskills
無料GitHub で公開

google-cloud-waf-cost-optimization

Generates cost optimization guidance for Google Cloud workloads based on the Google Cloud Well-Architected Framework (WAF). Use this skill to evaluate a workload, identify cost requirements and constraints, and provide actionable recommendations for build, deploy, and manage the workload cost-efficiently in Google Cloud.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md6.5 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Google Cloud Well-Architected Framework skill for the Cost Optimization pillar

Overview

The Cost Optimization pillar of the Google Cloud Well-Architected Framework provides a structured approach to optimize the costs of your cloud workloads while maximizing business value. Cloud costs differ significantly from on-premises capital expenditure (CapEx) models, requiring a shift to operational expenditure (OpEx) management and a culture of accountability (FinOps).

Core principles

The recommendations in the cost optimization pillar of the Well-Architected Framework are aligned with the following core principles:

Relevant Google Cloud products

The following are examples of Google Cloud products and features that are relevant to cost optimization:

  • Visibility and monitoring:

    • Cloud Billing reports: Native dashboards for visualizing spending and trends.
    • BigQuery billing export: Enables granular, custom analysis of billing data using SQL and BI tools.
    • Looker Studio: Used for creating detailed, shared cost dashboards and reports.
    • Billing alerts and budgets: Automated notifications when spending reaches predefined thresholds.
  • Automation and optimization tools:

    • Recommender / Active Assist: Automatically identifies idle resources, rightsizing opportunities, and unused commitments.
    • Cloud Hub Optimization: Integrates billing and resource utilization data to help developers and application owners quickly identify their most expensive, fluctuating, or underutilized cloud resources.
    • FinOps hub: Presents active savings and optimization opportunities in one dashboard.
    • Billing quotas: Limits on resource consumption to prevent unexpected cost spikes.
  • Efficient infrastructure:

    • Managed services and serverless services: Services like Cloud Run, Cloud Run functions, and GKE Autopilot reduce operational overhead and pay-per-use scaling.
    • Compute Engine: Use of Spot VMs for fault-tolerant workloads and Committed Use Discounts (CUDs) for stable workloads.
    • Cloud Storage Lifecycle Policies: Automatically moves data to lower-cost storage classes (Nearline, Coldline, Archive) based on age or access.
  • Organization and governance:

    • Resource Manager: Logical structure (Organizations, Folders, Projects) for cost attribution.
    • Labels: Metadata tags for categorizing and filtering costs by environment, team, or application.
    • Organization Policy Service: Enforces constraints (e.g., restricted regions or machine types) to control costs.

Workload assessment questions

Ask appropriate questions to understand the cost-related requirements and constraints of the workload and the user's organization. Choose questions from the following list:

  • How do you incorporate cost considerations into your cloud architecture design process?
  • How do you foster a culture of cost awareness among your development teams?
  • How do you monitor and manage cloud costs across different projects or departments?
  • What strategies do you use to optimize the cost of your compute resources?
  • How do you balance cost optimization with the need for agility and innovation?
  • How do you ensure that you are not over-provisioning cloud resources?
  • How do you use data and analytics to drive cost optimization decisions?
  • How do you optimize costs in different environments (e.g., development, testing, production)?
  • How do you ensure that your cost optimization efforts are sustainable and ongoing?
  • How do you measure the success of your cloud cost optimization initiatives?

Validation checklist

Use the following checklist to evaluate the architecture's alignment with cost-optimization recommendations:

  • Cost Attribution: 100% of resources are labeled with key metadata (e.g., env, team, app).
  • Granular Visibility: BigQuery billing export is enabled and used for regular cost reviews.
  • Budgets and Alerts: Every project or business unit has defined budgets and active alerts.
  • Rightsizing: Resources are regularly adjusted based on rightsizing suggestions provided by Active Assist Recommender.
  • Commitment Strategy: Spend is reviewed monthly to optimize Committed Use Discount coverage.
  • Idle Resource Management: Unused disks, IP addresses, and idle VMs are identified and removed monthly.
  • Managed Services: Serverless options are preferred for new workloads unless specific technical constraints exist.
  • Storage Tiers: Lifecycle policies are active for all major storage buckets to minimize archival costs.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Design, implement, and audit inclusive digital products using WCAG 2.2 Level AA standards. Use this skill to generate semantic ARIA for Web and accessibility traits for Web and Native platforms (iOS/Android).

日本語の概要は準備中です。原文の説明を表示しています。

tensology/decisionsai172026年10月10日 更新

Whole site or product — a full web accessibility (a11y) audit against WCAG 2.2, following the WCAG-EM methodology. Defines scope, samples representative pages and flows, runs the automated tier (`accessibility-scan`) and the hands-on manual tier (`accessibility-inspect`), and produces one conformance report. Grades each finding by severity and evidence basis, and states per-criterion conformance as pass, fail, or undetermined (needs a human). Use it for 'audit my site for accessibility', 'is this product accessible', 'a11y audit', 'WCAG or Section 508 conformance report', or any multi-page assessment. Assesses; does not fix (use `accessibility-fix`) or diff (use `accessibility-diff`). For a single page use `accessibility-scan`; for hands-on keyboard and screen-reader checks use `accessibility-inspect`.

日本語の概要は準備中です。原文の説明を表示しています。

tensology/decisionsai172026年10月10日 更新

Regression check — diff a live page's web accessibility (a11y) violations against a baseline. By default it compares your uncommitted changes (stash-based); pass `--branch [<name>]` to compare against a branch. Reports the new WCAG violations introduced, the ones fixed, and the count of pre-existing ones. Use it for 'did my change break accessibility', 'what a11y issues did this PR add', or as a CI gate. For a full scan of one page use `accessibility-scan`; for a whole site use `accessibility-audit`.

日本語の概要は準備中です。原文の説明を表示しています。

tensology/decisionsai172026年10月10日 更新

Remediation only — repair web accessibility (a11y) violations against WCAG 2.2 with a baseline, edit, and verify loop. Takes a target (URL, files, directory) or a findings worklist from `accessibility-scan`/`accessibility-inspect`/`accessibility-audit`, applies mechanical fixes as given, leaves TODOs for visual or contextual judgment, and verifies by re-running the baseline check. It only fixes. To find issues use `accessibility-scan` (one page, automated), `accessibility-inspect` (one page, manual), or `accessibility-audit` (whole site, WCAG-EM); to check for regressions use `accessibility-diff`. Use it for 'fix the a11y issues in X', 'make this accessible', 'add missing alt text and labels', 'apply these accessibility fixes', 'remediate these violations'.

日本語の概要は準備中です。原文の説明を表示しています。

tensology/decisionsai172026年10月10日 更新

One page, hands-on manual tier — drive a live page through the web accessibility (a11y) checks a rule engine can't decide: keyboard operation and focus order, screen-reader names, roles and states from the accessibility tree, reflow and zoom, reduced motion, form errors, and target size. Grades each finding by evidence basis (verified / confirm-with-a-human / human-required) and severity, and closes every criterion in a ledger: verified, flagged, not exercised, or N/A. Locates and assesses; does not fix (use `accessibility-fix`). Use it for keyboard testing, focus-order checks, screen-reader or a11y-tree review, reflow and zoom at 200%, or 'is this operable, not just lint-clean'. The automated tier is `accessibility-scan`; `accessibility-audit` runs both across a sampled site.

日本語の概要は準備中です。原文の説明を表示しています。

tensology/decisionsai172026年10月10日 更新

One page, automated tier — run the web accessibility (a11y) rule engine against a live page and locate every violation it can detect mechanically. Pass a URL, a config target name (e.g. `accesslint:accessibility-scan dev`), or nothing to use the default target from `accesslint.config.json`. Ensures a debuggable Chrome, runs the @accesslint/core engine over CDP, and returns a worklist of live-DOM WCAG 2.2 violations, each grounded to its DOM selector and source `file:line`. Locates; doesn't edit. Use it for 'is this page accessible', 'check a11y on this URL', 'find contrast and alt-text issues', or to verify a UI change. For hands-on keyboard and screen-reader checks use `accessibility-inspect`; for a whole site or product use `accessibility-audit`; to diff against uncommitted changes or a branch use `accessibility-diff`.

日本語の概要は準備中です。原文の説明を表示しています。

tensology/decisionsai172026年10月10日 更新

tensology のスキルをすべて見る

このスキルの問題を報告する