AWS Health Monitor
v1.0.0Monitor AWS Health Dashboard for active incidents and notify via configurable channels (Feishu, Telegram, Slack, Discord, etc.). Activate when user wants to...
⭐ 0· 246·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill claims to send notifications to Feishu/Telegram/Slack/Discord, and the Python script implements polling and message construction. However, the script invokes an external CLI 'openclaw' to deliver messages but the skill metadata did not declare any required binaries. That missing dependency is a meaningful mismatch: the notifier will silently fail or call an unexpected tool unless 'openclaw' is present and trusted.
Instruction Scope
SKILL.md instructions align with the script: place files under workspace/scripts, configure via environment variables, optionally run from Cron, and the script reads/writes only the ignore file, a local .aws-health-state.json, and writes logs. The runtime behavior stays within the stated monitoring/notification scope and only fetches the public AWS Health URL.
Install Mechanism
There is no installer or external download; this is instruction + Python script only. No remote code is fetched or extracted at install time. That lowers supply-chain risk, but users must still ensure the script file came from a trusted source.
Credentials
The SKILL.md and script rely on several environment variables (AWS_HEALTH_NOTIFY_CHANNEL, AWS_HEALTH_NOTIFY_TARGET, HTTP(S)_PROXY, AWS_HEALTH_WATCH_REGIONS, AWS_HEALTH_WATCH_SERVICES) but the registry metadata lists no required env vars or primary credential. Also, the notifier uses the external 'openclaw' CLI which likely needs its own credentials or configuration that are not declared. The skill does not request AWS credentials (none are needed because it uses the public status feed).
Persistence & Privilege
The skill does not request always:true and does not modify other skills or system-wide configs. It creates/updates a local state file (.aws-health-state.json) and writes logs under workspace; this is normal for a polling/notify tool.
What to consider before installing
This script does what it says (polls the public AWS Health feed and builds messages), but verify two things before using: (1) The script calls an external CLI named 'openclaw' to send notifications — the registry did not declare that dependency. Ensure 'openclaw' exists on your system, understand what endpoints and credentials it uses, and confirm it is from a trusted source. (2) The SKILL.md expects several environment variables (notify channel/target, optional proxy, watch filters) though the registry declared none — you must set AWS_HEALTH_NOTIFY_TARGET at minimum. Also review and control the workspace paths where the script will write state and logs. If you cannot verify the origin and behavior of the 'openclaw' binary, do not install or run this skill. If you want a cleaner deployment, ask the author to update metadata to declare the 'openclaw' dependency and the required env vars (or change the notifier to use direct API calls with documented credentials).Like a lobster shell, security has layers — review code before you run it.
awsvk9732vxh3y2xgs84hs4p0a9jg58258zqinfraopsvk9732vxh3y2xgs84hs4p0a9jg58258zqlatestvk9732vxh3y2xgs84hs4p0a9jg58258zqmonitoringvk9732vxh3y2xgs84hs4p0a9jg58258zqopsvk9732vxh3y2xgs84hs4p0a9jg58258zq
License
MIT-0
Free to use, modify, and redistribute. No attribution required.