Noise Maker

Aggregates and filters webhook alerts from multiple sources, correlates incidents by host, and escalates critical events via Telegram with rate limiting and...

This SKILL.md is a detailed design/plan, not an implemented skill. Before installing or running anything labeled 'noise-maker': - Ask the publisher for the implementation artifacts: a public code repository or packaged release, an explicit install script, and a list of exact env vars the implementation will require (DB_HOST/USER/PASS, TELEGRAM_TOKEN, HMAC secrets, etc.). - Do not provide credentials (DB, Telegram, HMAC secrets) until you can review the code and confirm secure secret handling (no plaintext storage, proper permissions, encryption at rest). - Confirm what files the skill will write and where (skill dir vs /opt). Prefer running the gateway on an isolated host/container rather than on your OpenClaw controller to limit blast radius. - Review any startup hook injection: get the exact hook content and rationale. Reject any opaque or remote-fetched code executed at agent startup. - Require least privilege: the gateway should only have access to the DB and tokens it needs; prefer scoped tokens and DB users with minimal rights. - If you must test, run it in an isolated environment (separate VM/container) with no production DB/credentials and with network access restricted. Because metadata currently lists no credentials or install steps while the design calls for many sensitive resources, treat this package as incomplete and verify the missing details before proceeding.

Type: OpenClaw Skill Name: noise-maker Version: 1.0.0 The bundle contains a comprehensive design specification (SKILL.md) and metadata (_meta.json) for an alert management gateway and its corresponding OpenClaw skill. The documentation details a legitimate architecture for processing system alerts from sources like Zabbix and Graylog, including database schemas, Telegram escalation logic, and a plan for agent-based management via scripts. No evidence of malicious intent, data exfiltration, or harmful prompt injection was identified; the content is entirely focused on the technical planning of a monitoring tool.