What does this skill do, and when should you use it?
This skill provides performance-focused guidance for Google Cloud workloads using the Performance Optimization pillar of the Well-Architected Framework. It covers resource allocation, elasticity, modular design, and continuous performance monitoring and improvement. It asks workload-assessment questions and applies a checklist covering caching, storage, autoscaling, fault isolation, observability, and performance testing. It fits teams that need a structured architecture review with actionable performance recommendations.
Generates Google Cloud WAF performance guidance from workload context supplied by the user; asks about capacity planning, caching, storage, architectural patterns, fault isolation, monitoring, performance testing, cost management, and traffic spikes; relates recommendations to example products including Compute Engine MIGs, GKE, Cloud Run, Cloud CDN, Memorystore, Bigtable, Spanner, Cloud Trace, Cloud Profiler, and Cloud Monitoring; and evaluates architectures against checklist items for resource allocation, modular design, continuous improvement, and elasticity.
- A cloud architect designing a new Google Cloud application needs to plan compute, storage, and networking capacity for expected peak load.
- A platform engineering team handling variable traffic needs to review autoscaling, serverless, and managed-service choices.
- An application team experiencing latency or throughput problems needs a structured review of tracing, profiling, and monitoring practices.
- A technical lead conducting an architecture review needs to check caching, storage selection, modularity, fault isolation, and performance testing.
How do you install this skill?
- This is primarily a generic review questionnaire and checklist, not a tested performance diagnosis or optimization plan.
- Before implementing autoscaling, caching, storage, or monitoring changes, confirm workload constraints, cost impact, permission scope, and rollback procedures.
- The grounding links depend on reachability of Google Cloud documentation; the skill does not state mainland-China availability or a Chinese-language delivery strategy.
Install the repository's skill collection with: npx skills add google/skills. The installer allows you to select specific skills from the repository. The source does not document the installation directory or a separate command for installing only this skill.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/google/skills.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/skills/cloud/google-cloud-waf-performance-optimization" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Provide the skill to an Agent Skills-compatible client along with workload context. Example trigger: "Assess this Google Cloud workload for performance optimization: it runs on GKE and latency has recently increased. Ask the relevant assessment questions, identify likely bottlenecks, and recommend improvements using the Performance Optimization pillar." The source does not define a specific trigger command, script, or argument format.
What are this skill's strengths and limitations?
- Defines four clear Google Cloud WAF performance principles with corresponding checklist items.
- Covers capacity planning, caching, elasticity, modularity, observability, and performance testing.
- Names relevant Google Cloud product examples to connect principles with architecture choices.
- It does not run load tests, query monitoring systems, analyze traces, or change infrastructure.
- Recommendation quality depends on the workload context and performance data supplied by the user.
- The source provides no test suite, runtime scripts, or detailed incident-remediation procedures.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Google Cloud Performance Advisor this page ✓ Google · Official | 50 · Use with care | ★ 21k | 12d ago | Apache-2.0 |
| Google Cloud Reliability Architect ✓ Google · Official | 57 · Use with care | ★ 21k | 12d ago | Apache-2.0 |
| Google Cloud Operational Excellence Advisor ✓ Google · Official | 53 · Use with care | ★ 21k | 12d ago | Apache-2.0 |
| Google Cloud Sustainability Advisor ✓ Google · Official | 48 · Use with care | ★ 21k | 12d ago | Apache-2.0 |
| Google Cloud Cost Optimization Advisor ✓ Google · Official | 47 · Use with care | ★ 21k | 12d ago | Apache-2.0 |
How did FollowSkills review this skill?
The skill is advisory only: it performs no code execution, credential access, external writes, or destructive actions, and it links the Google Cloud framework documents supporting its principles. It does not specify sensitive-data handling, user confirmation, isolation, rollback, or external-impact controls for implementation advice, so points are deducted.
The overview, principles, questions, and checklist are internally coherent and the intended behavior is understandable from a static read. There are no scripts, tests, input boundaries, exception paths, or failure-feedback guidance; under static calibration reliability cannot exceed 10, so points are deducted.
The target scenario is clear: performance optimization assessment for Google Cloud workloads, covering resource allocation, modularity, monitoring, and elasticity. Non-fit boundaries, exclusion triggers, input/output formats, Chinese support, and mainland-China reachability are unspecified, so points are deducted.
The skill has metadata, an overview, topical structure, assessment questions, and a validation checklist; the repository README supplies installation guidance and an Apache-2.0 license is present. It lacks skill-level versioning, changelog, explicit maintenance ownership, update path, example outputs, and troubleshooting guidance, so points are deducted.
The questions and checklist can support a usable first-pass performance architecture review. The content is generic and lacks a concrete output schema, quantitative criteria, prioritization, implementation steps, and alternative comparisons; under static calibration effectiveness cannot exceed 7, so points are deducted.
The four core principles include links to Google Cloud WAF grounding documents, providing limited claim traceability. No committed tests, CI coverage, representative outputs, or independent reproduction evidence are supplied; under static calibration verifiability cannot exceed 5, so points are deducted.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →