Well architected

Skill jpantsjoha/googlecloud-plugin/skills/well-architected

Google Cloud Well-Architected Framework reference. Six pillars: operational excellence, security, reliability, cost optimization, performance, and sustainability. Referenced by gcp-architect and gcp-security for every design review. Use when the user mentions: GCP framework, architecture pillars, reliability GCP, cost optimization GCP, performance GCP, sustainability GCP, WAF review.From its SKILL.md

Install

npx -y skills add jpantsjoha/googlecloud-plugin --skill well-architected

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.2 KB, as published. Nobody here has run it

GCP Well-Architected Framework

Six pillars that every GCP workload should be evaluated against. Referenced in every HLD, security review, and operational readiness check.

The Six Pillars

Pillar	Core Question	Key Practices
Operational Excellence	Can we build, run, and evolve the system reliably?	IaC, CI/CD, runbooks, monitoring-as-code
Security	Is the system protected against threats?	Least-privilege IAM, encryption, no public exposure by default
Reliability	Will the system recover from failures?	Multi-region, health checks, SLOs, chaos testing
Cost Optimization	Are we spending efficiently?	Right-sizing, committed use, lifecycle policies, budget alerts
Performance	Can the system handle load and scale?	Autoscaling, CDN, caching, regional proximity
Sustainability	Are we minimizing environmental impact?	Carbon-aware regions, efficient resource use

Quick Review Checklist (per design)

Operational Excellence

Infrastructure as Code (Terraform or Config Connector)
CI/CD pipeline with automated tests
Runbook for each primary failure mode
Alerting tied to SLOs

Security

Least-privilege IAM throughout
No public exposure without intent
Secrets in Secret Manager
Network deny-by-default

Reliability

SLO defined (availability + latency)
Health checks configured
Multi-zone or multi-region for production
Backup and recovery tested

Cost Optimization

Right-sized instances (use GCP recommender)
Committed use discounts evaluated
Budget alerts configured
Lifecycle policies on storage

Performance

Load tested at target traffic
Caching layer evaluated
CDN for static assets
Autoscaling configured

Sustainability

Low-carbon region selected where latency allows
Idle resources scheduled for shutdown

References

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.