Cloud Cost Optimization
wshobson/agents
Cuts cloud spend across AWS, Azure, GCP and OCI with cost tagging, rightsizing, commitment and spot pricing models, and architecture changes.
AWS CloudWatch monitoring — metrics, alarms, log queries, VPC flow log analysis, network performance.
Install AWS Cloud Monitoring
$ npx skills add automateyournetwork/netclaw --skill aws-cloud-monitoring -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install automateyournetwork/netclaw aws-cloud-monitoring --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/workspace/skills/aws-cloud-monitoring .claude/skills/aws-cloud-monitoring && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "aws-cloud-monitoring" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/aws-cloud-monitoring into .claude/skills/aws-cloud-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aws-cloud-monitoring", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/aws-cloud-monitoringType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add automateyournetwork/netclaw --skill aws-cloud-monitoring -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install automateyournetwork/netclaw aws-cloud-monitoring --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/workspace/skills/aws-cloud-monitoring .agents/skills/aws-cloud-monitoring && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "aws-cloud-monitoring" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/aws-cloud-monitoring into .agents/skills/aws-cloud-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aws-cloud-monitoring", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add automateyournetwork/netclaw --skill aws-cloud-monitoring -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install automateyournetwork/netclaw aws-cloud-monitoring --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/workspace/skills/aws-cloud-monitoring .cursor/skills/aws-cloud-monitoring && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "aws-cloud-monitoring" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/aws-cloud-monitoring into .cursor/skills/aws-cloud-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aws-cloud-monitoring", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/automateyournetwork/netclaw.git --path workspace/skills/aws-cloud-monitoring--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add automateyournetwork/netclaw --skill aws-cloud-monitoring -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install automateyournetwork/netclaw aws-cloud-monitoring --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/workspace/skills/aws-cloud-monitoring .gemini/skills/aws-cloud-monitoring && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "aws-cloud-monitoring" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/aws-cloud-monitoring into .gemini/skills/aws-cloud-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aws-cloud-monitoring", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install automateyournetwork/netclaw aws-cloud-monitoringInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add automateyournetwork/netclaw --skill aws-cloud-monitoring -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/workspace/skills/aws-cloud-monitoring .github/skills/aws-cloud-monitoring && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "aws-cloud-monitoring" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/aws-cloud-monitoring into .github/skills/aws-cloud-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aws-cloud-monitoring", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add automateyournetwork/netclaw --skill aws-cloud-monitoring -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install automateyournetwork/netclaw aws-cloud-monitoring --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/workspace/skills/aws-cloud-monitoring .opencode/skills/aws-cloud-monitoring && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "aws-cloud-monitoring" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/aws-cloud-monitoring into .opencode/skills/aws-cloud-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aws-cloud-monitoring", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
aws-cloud-monitoring- GitHub stars
- 677
- Token cost
- ~1k tokens
- SKILL.md length
- 402 words
- Files
- 1
- Skills in repo
- 120
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
AWS CloudWatch monitoring — metrics, alarms, log queries, VPC flow log analysis, network performance.
- Works in 6 steps: Check alarms: List CloudWatch alarms in… → VPN metrics: Tunnel state, bytes in/out… → NAT Gateway metrics: Active connections,… → …
- Checking AWS alarms
- SKILL.md covers MCP Server, Key Capabilities, Workflow: Network Monitoring… and Workflow: Flow Log Analysis, plus 5 more sections
- Calls uvx; needs AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY
What it does
AWS Cloud Monitoring is an agent skill from automateyournetwork/netclaw. AWS CloudWatch monitoring — metrics, alarms, log queries, VPC flow log analysis, network performance. Use when checking AWS alarms, analyzing VPC flow logs, investigating network latency, or monitoring VPN and NAT Gateway metrics.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud. It works with Amazon Web Services. The repository describes itself as: An AI agent that claws through your network. The licence is Apache-2.0.
When your agent uses it
- Checking AWS alarms
- Analyzing VPC flow logs
- Investigating network latency
- Monitoring VPN and NAT Gateway metrics
Example prompts
- “/aws-cloud-monitoring”
Requirements
- A credential in AWS_SECRET_ACCESS_KEY
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Check alarms: List CloudWatch alarms in ALARM state
- VPN metrics: Tunnel state, bytes in/out for site-to-site VPNs
- NAT Gateway metrics: Active connections, packets dropped, bytes processed
- Transit Gateway metrics: Bytes in/out, packets dropped per attachment
- ELB metrics: Healthy/unhealthy targets, latency, 5xx errors
- Report: Network health dashboard with any issues flagged
What it can do on your machine
Read from SKILL.md and the folder at commit f943637. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
uvx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use uvx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
AWS_ACCESS_KEY_IDAWS_SECRET_ACCESS_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
AWS Cloud Monitoring loads about 1k tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 402 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from automateyournetwork/netclaw at commit f943637, republished under its Apache-2.0 licence (© automateyournetwork). 402 words, ~1,036 tokens.
Download SKILL.mdSave it as
.claude/skills/aws-cloud-monitoring/SKILL.md (or your agent's skills folder).- name
- aws-cloud-monitoring
- description
- AWS CloudWatch monitoring — metrics, alarms, log queries, VPC flow log analysis, network performance. Use when checking AWS alarms, analyzing VPC flow logs, investigating network latency, or monitoring VPN and NAT Gateway metrics.
- version
- 1.0.0
- license
- Apache-2.0
- tags
- aws, cloudwatch, monitoring, metrics, alarms, logs, flow-logs
AWS Cloud Monitoring
MCP Server
- Command:
uvx awslabs.cloudwatch-mcp-server@latest(stdio transport) - Requires:
AWS_ACCESS_KEY_ID,AWS_SECRET_ACCESS_KEY,AWS_REGION(orAWS_PROFILE)
Key Capabilities
- Metrics: Query CloudWatch metrics for any AWS service (EC2, ELB, TGW, NAT GW, VPN)
- Alarms: List and inspect CloudWatch alarms and their states
- Logs: Run CloudWatch Logs Insights queries across any log group
- Flow Logs: Analyze VPC and TGW flow logs for traffic patterns and dropped connections
Workflow: Network Monitoring Dashboard
When a user asks "how is our AWS network performing?":
- Check alarms: List CloudWatch alarms in ALARM state
- VPN metrics: Tunnel state, bytes in/out for site-to-site VPNs
- NAT Gateway metrics: Active connections, packets dropped, bytes processed
- Transit Gateway metrics: Bytes in/out, packets dropped per attachment
- ELB metrics: Healthy/unhealthy targets, latency, 5xx errors
- Report: Network health dashboard with any issues flagged
Workflow: Flow Log Analysis
When investigating traffic patterns or security events:
- Query VPC flow logs: Filter by source IP, destination IP, port, action (ACCEPT/REJECT)
- Identify rejected traffic: Find REJECT entries to see blocked connections
- Top talkers: Aggregate by source/destination to find heaviest traffic flows
- Time correlation: Narrow to specific time windows around incidents
- Report: Traffic analysis with recommendations
Common CloudWatch Network Metrics
| Service | Metric | What It Tells You |
|---|---|---|
| VPN | TunnelState | 0=down, 1=up for each tunnel |
| VPN | TunnelDataIn/Out | Bytes through each VPN tunnel |
| NAT GW | ActiveConnectionCount | Active NAT connections |
| NAT GW | PacketsDropCount | Packets dropped (capacity issue) |
| NAT GW | BytesProcessed | Traffic volume through NAT |
| TGW | BytesIn/BytesOut | Traffic per TGW attachment |
| TGW | PacketDropCountBlackhole | Blackhole route drops |
| ELB | HealthyHostCount | Healthy targets behind ALB/NLB |
| ELB | TargetResponseTime | Backend latency |
| EC2 | NetworkIn/NetworkOut | Instance network throughput |
| EC2 | NetworkPacketsIn/Out | Instance packet rate |
Show full SKILL.md (129 more words)Show less
Flow Log Query Examples
# Top rejected connections in last hour
fields @timestamp, srcAddr, dstAddr, dstPort, action
| filter action = "REJECT"
| stats count() as rejections by srcAddr, dstAddr, dstPort
| sort rejections desc
| limit 20
# Traffic from specific source
fields @timestamp, srcAddr, dstAddr, dstPort, bytes, action
| filter srcAddr = "10.0.1.50"
| sort @timestamp desc
# Top talkers by bytes
fields srcAddr, dstAddr, bytes
| stats sum(bytes) as totalBytes by srcAddr, dstAddr
| sort totalBytes desc
| limit 10Important Rules
- CloudWatch Logs Insights queries have a cost — be mindful of time range and data volume
- Region-specific — metrics and logs are scoped to the configured region
- Record in GAIT — log monitoring investigations for audit trail
Environment Variables
AWS_ACCESS_KEY_ID,AWS_SECRET_ACCESS_KEY,AWS_REGION(orAWS_PROFILE)
Failure Behavior
- On a tool error (timeout, unreachable host, malformed response), report the failure and its error message directly to the user rather than fabricating or guessing at results.
- For a confirmed read-only call, check connectivity and retry once if appropriate. For any call that changes state or sends a message, a timeout does not prove the action failed: inspect current state or delivery status before retrying, preserve the required approval/change gates, and do not repeat an action whose outcome is unknown.
© automateyournetwork, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in workspace/skills/aws-cloud-monitoring of automateyournetwork/netclaw.
Open the folder on GitHubat commit f943637
Compare with similar skills
AWS Cloud Monitoring next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| AWS Cloud Monitoring this skillautomateyournetwork/netclaw | 677 | — | ~1k | Automated safety check: Pass | Apache-2.0 | |
| Cloud Cost Optimizationwshobson/agents | 40k | 14 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Review Docshashicorp/terraform-provider-aws | 11k | — | ~1.3k | Automated safety check: Pass | MPL-2.0 | |
| AWS Cdk Developmentzxkane/aws-skills | 367 | 2 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit | 260 | 6 repos | ~1.1k | Automated safety check: Notes | Custom licence | |
| Terravision Cloud Diagramspatrickchugh/terravision | 1.6k | — | ~5.6k | Automated safety check: Notes | AGPL-3.0-only |
Similar skills
- Official
Review Docs
hashicorp/terraform-provider-aws
Review a Terraform AWS Provider PR's end-user documentation (website/docs//.markdown): whether docs are needed, description openings, argument/attribute style, section structure, tags wording, code…
AWS Cdk Development
zxkane/aws-skills
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.
Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
Terravision Cloud Diagrams
patrickchugh/terravision
Draw cloud architecture diagrams for AWS, Azure or GCP with the official provider icon sets, using TerraVision.
Thesvg
glincker/thesvg
Fetch brand SVG logos and cloud architecture icons (AWS, Azure, GCP) from theSVG.
More from automateyournetwork/netclaw
All 120 skills in this repoEVE-NG Lab Topology Design
automateyournetwork/netclaw
Entry point for designing EVE-NG network labs: classifies the request, gathers missing requirements, proposes options and validates the resulting topology.
ACI Policy Change Deployment
automateyournetwork/netclaw
Deploys Cisco ACI policy changes only behind an approved ServiceNow Change Request, capturing pre and post-change fault baselines and rolling back automatically on a fault delta.
Cisco ACI Fabric Health Audit
automateyournetwork/netclaw
Runs a phased health audit of a Cisco ACI fabric through MCP tools: node status, links, tenant and policy review, faults and endpoint learning.
Anta Validation
automateyournetwork/netclaw
Validate Arista EOS network state against ANTA's pre-built 208-test catalogue, with structured pass/fail verdicts.
Arista Cvp
automateyournetwork/netclaw
Arista CloudVision Portal (CVP) automation via REST API — device inventory, events, connectivity monitoring, tag management (4 tools).
Batfish Config Analysis
automateyournetwork/netclaw
Batfish network configuration analysis -- pre-deployment validation, reachability testing, ACL/firewall tracing, differential analysis, compliance checking.
Related
Works with
Categories
Questions about AWS Cloud Monitoring
What does AWS Cloud Monitoring do?
AWS CloudWatch monitoring — metrics, alarms, log queries, VPC flow log analysis, network performance. AWS Cloud Monitoring is an agent skill from automateyournetwork/netclaw. AWS CloudWatch monitoring — metrics, alarms, log queries, VPC flow log analysis, network performance.
When should I use AWS Cloud Monitoring?
AWS Cloud Monitoring fits situations like: checking AWS alarms; analyzing VPC flow logs; investigating network latency; monitoring VPN and NAT Gateway metrics.
How do I install AWS Cloud Monitoring in Claude Code?
Run `npx skills add automateyournetwork/netclaw --skill aws-cloud-monitoring -a claude-code`. Or copy the skill folder (workspace/skills/aws-cloud-monitoring in automateyournetwork/netclaw) into .claude/skills/aws-cloud-monitoring in your project. Claude Code loads it when a task matches its description.
How do I install AWS Cloud Monitoring in Codex?
Run `npx skills add automateyournetwork/netclaw --skill aws-cloud-monitoring -a codex`. Or copy the skill folder (workspace/skills/aws-cloud-monitoring in automateyournetwork/netclaw) into .agents/skills/aws-cloud-monitoring in your project. Codex loads it when a task matches its description.
Can I use AWS Cloud Monitoring in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add automateyournetwork/netclaw --skill aws-cloud-monitoring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/aws-cloud-monitoring, .gemini/skills/aws-cloud-monitoring, .github/skills/aws-cloud-monitoring and .opencode/skills/aws-cloud-monitoring in your project.
What does AWS Cloud Monitoring need to run?
Going by SKILL.md and its folder, AWS Cloud Monitoring needs the command-line tools its instructions call (uvx) and credentials named AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY. Our summary lists: A credential in AWS_SECRET_ACCESS_KEY.
Does AWS Cloud Monitoring access the network?
SKILL.md contains no URLs. Its commands use uvx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is AWS Cloud Monitoring safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does AWS Cloud Monitoring use?
AWS Cloud Monitoring is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does AWS Cloud Monitoring use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to AWS Cloud Monitoring?
Skills that share tags, products or a category with AWS Cloud Monitoring: Cloud Cost Optimization (wshobson/agents, 40k stars), Review Docs (hashicorp/terraform-provider-aws, 11k stars), AWS Cdk Development (zxkane/aws-skills, 367 stars) and Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 260 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains AWS Cloud Monitoring?
automateyournetwork (a GitHub user) maintains it in automateyournetwork/netclaw, which has 677 GitHub stars. The repository holds 120 skills in this directory. The repository was last updated on October 11, 2026.
Source: automateyournetwork/netclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.