← Back to Skills Marketplace
davida-ps

openclaw-audit-watchdog

by davida-ps · GitHub ↗ · v0.1.4 · MIT-0
cross-platform ✓ Security Clean
2378
Downloads
3
Stars
16
Active Installs
8
Versions
Install in OpenClaw
/install openclaw-audit-watchdog
Description
Automated daily security audits for OpenClaw agents with DM delivery and optional email reporting. Runs deep audits, creates or updates a recurring cron job,...
Usage Guidance
This package is internally consistent with its stated purpose, but check the following before enabling: 1) Verify you trust the openclaw CLI and the skill source (README suggests downloading a release — verify signatures/URL if you use that path). 2) Review and confirm DM and optional email recipients (PROMPTSEC_DM_CHANNEL, PROMPTSEC_DM_TO, PROMPTSEC_EMAIL_TO) to avoid sending audit output to unintended parties. 3) Inspect which environment variables will be persisted into the cron payload (setup_cron.mjs lists PERSISTED_ENV_KEYS) and avoid baking any secrets you don't want stored in a recurring job. 4) If you enable suppressions, understand that they require both the --enable-suppressions flag and a config file sentinel; review any suppression files before enabling. 5) Optionally inspect the scripts (runner.sh, setup_cron.mjs, send_smtp.mjs) locally to confirm behavior and delivery paths (send_smtp can be pointed to a remote relay if you set PROMPTSEC_SMTP_HOST). If any of these checks fail or you cannot verify the release origin, do not enable the unattended cron.
Capability Analysis
Type: OpenClaw Skill Name: openclaw-audit-watchdog Version: 0.1.4 The openclaw-audit-watchdog skill is a security monitoring tool designed to automate daily audits and report findings via DM or email. The codebase demonstrates high security maturity, featuring robust input sanitization for shell commands (setup_cron.mjs), email header cleaning to prevent injection (sendmail_report.sh, send_smtp.mjs), and a defense-in-depth suppression mechanism that requires both a CLI flag and a configuration sentinel to activate. All data delivery destinations are user-configured, and the instructions in SKILL.md are transparently aligned with the stated purpose of scheduling and executing security audits.
Capability Assessment
Purpose & Capability
Name/description align with required binaries (openclaw, node, bash) and declared env vars (PROMPTSEC_DM_CHANNEL, PROMPTSEC_DM_TO). The scripts implement cron setup, run openclaw audits, render reports, and optionally send email — all coherent with the stated goal.
Instruction Scope
SKILL.md and scripts limit activity to installing/updating a cron job, running openclaw security audits, rendering a report, and delivering it via DM or optional email. The suppression loader reads only configured suppression config files and only activates when the explicit --enable-suppressions flag is set. The runner can optionally git-pull if PROMPTSEC_GIT_PULL=1; this is documented and optional.
Install Mechanism
No install spec is included in the registry (instruction-only with bundled scripts), which is low risk. README references a standalone download from a GitHub release — that network-download path is documented but not enforced by the registry manifest; if you follow that path verify the release source and archive integrity before installing.
Credentials
Only two required env vars are declared (DM channel and recipient). The skill documents and optionally uses many additional env vars (email/S MTP, install dir, audit config, git-pull toggle). setup_cron persists a set of environment keys into the cron payload (PROMPTSEC_* and OPENCLAW_AUDIT_CONFIG). This is proportionate for an unattended cron job but operators should review which env values will be baked into the job to avoid persisting sensitive values unintentionally.
Persistence & Privilege
The skill creates/updates an unattended openclaw cron job (persistence) which is consistent with its purpose. It is not always: true and requires operator confirmation (setup_cron prints a preflight). Because the cron payload persists selected env keys, review the persisted keys and recipients before enabling.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install openclaw-audit-watchdog
  3. After installation, invoke the skill by name or use /openclaw-audit-watchdog
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.4
Release 0.1.4 via CI
v0.1.3
- Test files and end-to-end test artifacts have been removed for a lighter codebase. - Documentation updates in SKILL.md and CHANGELOG.md to reflect current operational/usage details. - No functional or interface changes for users; cron setup and suppression features remain unchanged. - Minor internal script/metadata adjustments.
v0.1.2
Release 0.1.2 via CI
v0.1.1
Release 0.1.1 via CI
v0.1.0
Release 0.1.0 via CI
v0.0.4
Release 0.0.4 via CI
v0.0.3
Release 0.0.3 via CI
v0.0.1
Release 0.0.1 via CI
Metadata
Slug openclaw-audit-watchdog
Version 0.1.4
License MIT-0
All-time Installs 16
Active Installs 16
Total Versions 8
Frequently Asked Questions

What is openclaw-audit-watchdog?

Automated daily security audits for OpenClaw agents with DM delivery and optional email reporting. Runs deep audits, creates or updates a recurring cron job,... It is an AI Agent Skill for Claude Code / OpenClaw, with 2378 downloads so far.

How do I install openclaw-audit-watchdog?

Run "/install openclaw-audit-watchdog" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is openclaw-audit-watchdog free?

Yes, openclaw-audit-watchdog is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does openclaw-audit-watchdog support?

openclaw-audit-watchdog is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created openclaw-audit-watchdog?

It is built and maintained by davida-ps (@davida-ps); the current version is v0.1.4.

💬 Comments