← Back to Skills Marketplace
Noise Maker
by
Morten Bojer
· GitHub ↗
· v1.0.0
· MIT-0
86
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install noise-maker
Description
Aggregates and filters webhook alerts from multiple sources, correlates incidents by host, and escalates critical events via Telegram with rate limiting and...
Usage Guidance
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.
Capability Analysis
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.
Capability Assessment
Purpose & Capability
The name/description and SKILL.md consistently describe an alert gateway that requires database credentials, Telegram credentials, HMAC secrets, and ability to bind a network endpoint (port 8090). However the registry metadata declares no required env vars, no binaries, and no install steps. That mismatch (describing heavy external integrations but requesting nothing) is incoherent and should be clarified.
Instruction Scope
Although this is an instruction-only skill (planning doc), the runtime design specifies reading/writing system paths (/opt/alert-gateway/buffer/, /opt/alert-gateway/cache/targets.json), storing raw alerts to a DB, writing startup-check.json into ~/.openclaw/skills/noise-maker/, and injecting a before_agent_start one-liner into agent context. Those are broad actions that go beyond simple in-skill operations and could change agent startup behavior and system state.
Install Mechanism
No install spec is included (low install surface). However the SKILL.md plans a Python/FastAPI service, Caddy route, and on-host buffers — implementation will require installation and elevated deployment steps on MB-OPENCLAW. The lack of an explicit install mechanism or verified release/source is a missing piece that increases risk because the actual code/install process is undefined.
Credentials
The architecture clearly requires secrets: DB credentials for MB-PGDB, Telegram API token(s), HMAC secrets per source, and potentially SSH/OS privileges to write /opt and ~/.openclaw paths. Yet the published metadata lists no required environment variables or primary credential. That discrepancy means the skill as published is incomplete and would later request sensitive credentials without prior disclosure.
Persistence & Privilege
always:false (good). But the design explicitly writes files under the skill directory and installs a before_agent_start hook that can inject context at agent startup. Writing self-owned files is normal, but injecting startup behavior and writing to /opt are persistence/privilege actions that should be reviewed and limited to least privilege.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install noise-maker - After installation, invoke the skill by name or use
/noise-maker - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release: Alert Gateway architecture with incident correlation, rule engine, LLM filter groundwork
Metadata
Frequently Asked Questions
What is Noise Maker?
Aggregates and filters webhook alerts from multiple sources, correlates incidents by host, and escalates critical events via Telegram with rate limiting and... It is an AI Agent Skill for Claude Code / OpenClaw, with 86 downloads so far.
How do I install Noise Maker?
Run "/install noise-maker" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Noise Maker free?
Yes, Noise Maker is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Noise Maker support?
Noise Maker is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Noise Maker?
It is built and maintained by Morten Bojer (@mbojer); the current version is v1.0.0.
More Skills