v1.0.1

Config Guardian

BenignClawScan verdict for this skill. Analyzed May 1, 2026, 5:12 AM.

Analysis

Config Guardian is purpose-aligned for safer OpenClaw config changes, but users should review approved config edits and be aware it creates persistent local backups.

GuidanceInstall only if you want agents to help modify OpenClaw configuration. Approve each config change deliberately, check the path and value before running it, and manage the backup directory because it keeps historical copies of your OpenClaw config.

Findings (3)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

Abnormal behavior control

Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.

Tool Misuse and Exploitation

SeverityMediumConfidenceHighStatusNote

SKILL.md

Applies change via `openclaw config set <path> <value>`

The skill intentionally exposes a wrapper for changing OpenClaw configuration. This is aligned with the stated purpose and includes backup/rollback guidance, but a wrong path or value could still alter persistent agent behavior.

User impactIf approved with the wrong config path or value, the skill can change how OpenClaw agents or gateway settings behave.

RecommendationBefore approving use, verify the exact config path and new value, and keep the generated backup until the change is confirmed safe.

Agentic Supply Chain Vulnerabilities

SeverityLowConfidenceHighStatusNote

.clawhub/origin.json

"requires": {
        "bins": ["openclaw", "python3"]
      }

The included origin metadata shows required binaries, while the registry metadata says no required binaries. This appears to be an under-declared dependency rather than hidden behavior because the scripts visibly call openclaw and python3.

User impactThe skill may fail or behave unexpectedly if OpenClaw or Python 3 is missing, despite the registry requirements saying no binaries are needed.

RecommendationConfirm openclaw and python3 are installed before use, and treat the registry requirement mismatch as a packaging issue to fix.

Sensitive data protection

Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.

Memory and Context Poisoning

SeverityLowConfidenceHighStatusNote

scripts/atomic_apply.sh

BACKUP_DIR="${BACKUP_DIR:-$HOME/.openclaw/config-guardian-backups}"
CONFIG_FILE="$HOME/.openclaw/openclaw.json"
...
cp "$CONFIG_FILE" "$BACKUP_PATH"

The script creates persistent local copies of the OpenClaw config. This is disclosed and supports rollback, but it retains configuration history outside the primary config file.

User impactOld config values may remain in the backup directory after changes, including any sensitive settings that may be present in the config file.

RecommendationProtect the backup directory and periodically remove old backups that are no longer needed.