agentleFS
jpantsjohajpantsjoha/googlecloud-plugin/skills/networking/SKILL.md

networking

Skill4 starsChanged 4 months agoMITView on GitHub

Design and manage GCP networking: VPC, subnets, firewall rules, Cloud Load Balancing, Cloud Armor, Private Google Access, and Shared VPC. Deny-by-default firewall posture. Warns before creating external load balancers (billable). Use when the user mentions: networking GCP, cloud load balancer, VPN GCP, cloud NAT, network design GCP.

10 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Never use 0.0.0.0/0 as a source range for SSH or RDP — use IAP tunnels instead

    line 71

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Networking

Design and manage GCP VPC networks, connectivity, and traffic management. Deny-by-default; open only what is necessary.

Core Patterns

Create a VPC with a subnet

gcloud compute networks create VPC_NAME \
  --subnet-mode=custom \
  --project=PROJECT_ID

gcloud compute networks subnets create SUBNET_NAME \
  --network=VPC_NAME \
  --region=REGION \
  --range=10.0.0.0/24 \
  --enable-private-ip-google-access \
  --project=PROJECT_ID

Deny-by-default firewall (then open minimally)

# Deny all ingress (GCP default is deny-all for custom VPCs)
# Add targeted allow rules only:
gcloud compute firewall-rules create allow-internal \
  --network=VPC_NAME \
  --direction=INGRESS \
  --action=ALLOW \
  --rules=tcp:0-65535,udp:0-65535,icmp \
  --source-ranges=10.0.0.0/8 \
  --project=PROJECT_ID

Enable Private Google Access

gcloud compute networks subnets update SUBNET_NAME \
  --region=REGION \
  --enable-private-ip-google-access \
  --project=PROJECT_ID

Cloud NAT (outbound internet without public IPs)

gcloud compute routers create ROUTER_NAME \
  --network=VPC_NAME \
  --region=REGION

gcloud compute routers nats create NAT_NAME \
  --router=ROUTER_NAME \
  --region=REGION \
  --auto-allocate-nat-external-ips \
  --nat-all-subnet-ip-ranges

Safety Rules

  • Never use 0.0.0.0/0 as a source range for SSH or RDP — use IAP tunnels instead
  • Enable Private Google Access on all subnets to avoid routing through internet
  • Cost warning: external load balancers and Cloud Armor bill per rule and per GB

References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.