← Back to Skills Marketplace
ordiy

Watadot Aws Cloudwatch

by ordiy · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
290
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install watadot-aws-cloudwatch
Description
Observability and monitoring by Watadot Studio. Log tailing and metric extraction.
README (SKILL.md)

AWS CloudWatch Skills

Observability and automated monitoring patterns.

🚀 Core Commands

Log Insights

# Live tail of a Log Group
aws logs tail /aws/lambda/\x3Cfunction-name> --follow

# Query logs for errors (last 1h)
aws logs filter-log-events --log-group-name \x3Cname> --filter-pattern "ERROR" --start-time $(date -d '1 hour ago' +%s000) --query "events[].message"

Metrics & Alarms

# List active alarms with state
aws cloudwatch describe-alarms --query "MetricAlarms[?StateValue==\`ALARM\`].{Name:AlarmName,Reason:StateReason}" --output table

# Get CPU utilization metric for EC2
aws cloudwatch get-metric-statistics --namespace AWS/EC2 --metric-name CPUUtilization --dimensions Name=InstanceId,Value=\x3Cid> --period 3600 --statistics Average --start-time 2026-03-15T00:00:00 --end-time 2026-03-16T00:00:00

Dashboard Orchestration

# List dashboard names
aws cloudwatch list-dashboards --query "DashboardEntries[].DashboardName"

🧠 Best Practices

  1. Retention Policies: Don't keep logs forever. Set retention (e.g., 14 days) to save storage costs.
  2. Log Streams: Use unique log stream names for different agent instances to avoid interleaving.
  3. Structured Logging: Log in JSON format to make filtering and automated analysis via OpenClaw easier.
  4. Alarms: Set up billing alarms to catch sudden spikes in AWS usage early.
Usage Guidance
This skill is instruction-only and simply provides aws CLI examples for CloudWatch. Before enabling it: ensure the agent environment has the aws CLI installed and that any AWS credentials available to the agent follow least-privilege (read-only for logging/metrics if possible). Remember the skill will run commands using whatever AWS identity is configured (even though it doesn't declare creds explicitly). If you run agents autonomously, be cautious about granting them wide AWS permissions. Also note small portability issues (e.g., date -d usage may not work on macOS) but these are operational, not security-related.
Capability Analysis
Type: OpenClaw Skill Name: watadot-aws-cloudwatch Version: 1.0.0 The skill bundle provides standard AWS CLI commands for CloudWatch observability, including log tailing, metric extraction, and alarm management. All commands in SKILL.md are legitimate administrative actions, and there is no evidence of malicious intent, data exfiltration, or prompt injection.
Capability Assessment
Purpose & Capability
Name/description (CloudWatch observability, log tailing, metrics) match the SKILL.md commands (aws logs, aws cloudwatch). Requesting the aws CLI is appropriate for this purpose.
Instruction Scope
SKILL.md is narrowly scoped to specific aws CLI commands for tailing logs, filtering events, listing alarms/dashboards, and fetching metrics. It does not instruct the agent to read arbitrary local files or send data to external endpoints. Note: the skill does not declare credentials but will use whatever AWS credentials the environment provides when running the aws CLI.
Install Mechanism
No install spec and no code files — lowest-risk instruction-only skill. It relies on an existing aws binary and does not download or execute external code.
Credentials
The skill declares no required env vars or credentials, which is reasonable for an instruction-only AWS helper. However, the aws CLI uses AWS credentials from environment or config (~/.aws). Users should be aware the agent will run aws commands under whatever AWS identity is available.
Persistence & Privilege
always:false and default model invocation settings — no elevated persistence. The skill does not request system-wide changes or modify other skills.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install watadot-aws-cloudwatch
  3. After installation, invoke the skill by name or use /watadot-aws-cloudwatch
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release: Observability and monitoring tools for AWS CloudWatch - Provides core CLI commands for live log tailing, log filtering, and error searches. - Includes metric extraction examples, such as querying EC2 CPU utilization. - Lists active CloudWatch alarms and dashboard orchestration commands. - Shares best practices for log retention, structuring, and alarm setup. - Designed for easy integration with Watadot Studio and OpenClaw workflows.
Metadata
Slug watadot-aws-cloudwatch
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Watadot Aws Cloudwatch?

Observability and monitoring by Watadot Studio. Log tailing and metric extraction. It is an AI Agent Skill for Claude Code / OpenClaw, with 290 downloads so far.

How do I install Watadot Aws Cloudwatch?

Run "/install watadot-aws-cloudwatch" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Watadot Aws Cloudwatch free?

Yes, Watadot Aws Cloudwatch is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Watadot Aws Cloudwatch support?

Watadot Aws Cloudwatch is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Watadot Aws Cloudwatch?

It is built and maintained by ordiy (@ordiy); the current version is v1.0.0.

💬 Comments