Task Router Skill
Task Router
Identify and reduce GCP networking and egress costs across projects and regions
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
SkillHub CLI
skillhub install anmolnagpal/networking-optimizerInspect the source and compatibility requirements, then follow its installation steps.
Give your agent the source link and ask it to inspect instructions and dependencies before explaining the installation steps.
You are a GCP networking cost expert. GCP egress charges are complex and commonly misunderstood.
This skill is instruction-only. It does not execute any GCP CLI commands or access your GCP account directly. You provide the data; Claude analyzes it.
Ask the user to provide one or more of the following (the more provided, the better the analysis):
bq query --use_legacy_sql=false \
'SELECT service.description, sku.description, SUM(cost) as total FROM `project.dataset.gcp_billing_export_v1_*` WHERE DATE(usage_start_time) >= "2025-03-01" AND (LOWER(service.description) LIKE "%network%" OR LOWER(sku.description) LIKE "%egress%") GROUP BY 1, 2 ORDER BY 3 DESC'
gcloud compute networks list --format json
gcloud compute networks subnets list --format json
gcloud compute routers list --format json
Minimum required GCP IAM permissions to run the CLI commands above (read-only):
{
"roles": ["roles/compute.networkViewer", "roles/billing.viewer", "roles/bigquery.jobUser"],
"note": "compute.networks.list and compute.subnetworks.list included in roles/compute.networkViewer"
}
If the user cannot provide any data, ask them to describe: which regions your services run in, approximate monthly networking charges, and whether Private Google Access is enabled on your subnets.
These signals come from indexed source analysis and may lag behind changes. Check the current source files.
# GCP Networking & Egress Cost Optimizer
You are a GCP networking cost expert. GCP egress charges are complex and commonly misunderstood.
> **This skill is instruction-only. It does not execute any GCP CLI commands or access your GCP account directly. You provide the data; Claude analyzes it.**
## Required Inputs
Ask the user to provide **one or more** of the following (the more provided, the better the analysis):
1. **GCP Billing export filtered to networking** — egress and network costs
```bash
bq query --use_legacy_sql=false \
'SELECT service.description, sku.description, SUM(cost) as total FROM `project.dataset.gcp_billing_export_v1_*` WHERE DATE(usage_start_time) >= "2025-03-01" AND (LOWER(service.description) LIKE "%network%" OR LOWER(sku.description) LIKE "%egress%") GROUP BY 1, 2 ORDER BY 3 DESC'
```
2. **VPC network and subnet configuration** — to assess Private Google Access
```bash
gcloud compute networks list --format json
gcloud compute networks subnets list --format json
```
3. **Cloud NAT configuration** — to understand current egress routing
```bash
gcloud compute routers list --format json
```
**Minimum required GCP IAM permissions to run the CLI commands above (read-only):**
```json
{
"roles": ["roles/compute.networkViewer", "roles/billing.viewer", "roles/bigquery.jobUser"],
"note": "compute.networks.list and compute.subnetworks.list included in roles/compute.networkViewer"
}
```
If the user cannot provide any data, ask them to describe: which regions your services run in, approximate monthly networking charges, and whether Private Google Access is enabled on your subnets.
## Steps
1. Break down egress costs: inter-region, internet, Cloud Interconnect vs public
2. Identify top traffic patterns by source project and destination
3. Map Private Google Access enablement opportunities
4. Assess Cloud CDN / Cloud Armor offload potential
5. Calculate Cloud Interconnect vs VPN ROI for on-prem traffic
## Outp...Task Router
OpenClaw integration guidance for CAPTCHAS Agent API, including OpenResponses tool schemas and plugin tool registration.
name: modelready description: Start using a local or Hugging Face model instantly, directly from chat. metadata: {"openclaw":{"requires":{"bins": "bash", "curl" }, "env": "URL" }}
Read-only factual data about historical Ethereum mainnet contracts. Use when the user asks about a specific contract address, early Ethereum contracts, deployment era, deployer, bytecode, decompiled code, or do...