From gcp-cloud
Design private-by-default GCP networking: Shared VPC for multi-project, default-deny firewall targeted by tag/service-account, Private Google Access + Private Service Connect, and Cloud NAT for controlled egress.
How this skill is triggered — by the user, by Claude, or both
Slash command
/gcp-cloud:gcp-private-networkingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Centralize the network in a **host project**; service projects attach. Cleaner than per-project VPC + peering.
Centralize the network in a host project; service projects attach. Cleaner than per-project VPC + peering.
Default-deny, then allow by network tag / service account (not broad CIDRs). Never open admin ports to the internet.
Private Google Access (no external IP), Private Service Connect (private service access), Cloud NAT (controlled egress).
Plan CIDRs to avoid overlap. Route exposure verdicts to security-engineering.
npx claudepluginhub mcorbett51090/ravenclaude --plugin gcp-cloudGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.