Security

Claw Security Self-Check

Try it

Perform a strict, evidence-based, read-only security assessment of the current OpenClaw host, review each NOT_TESTED item through targeted OpenClaw Agent inv...

What it does

Perform a strict, evidence-based, read-only security assessment of the current OpenClaw host, review each NOT_TESTED item through targeted OpenClaw Agent inv...

The skill document

Claw Security Self-Check

Assess only facts that can be verified from read-only configuration, CLI output, process information, and file metadata on the current host. First use deterministic scripts to collect routine evidence, then have the OpenClaw Agent perform targeted read-only review of NOT_TESTED observations, and finally use the report script to validate and merge the structured review evidence.

Mandatory Rules

  • Do not return PASS without the machine evidence required by references/evidence-rules.md.
  • Do not print or persist credential values, SecretRef contents, private messages, or real personal data.
  • Do not modify OpenClaw configuration, firewall rules, packages, services, users, or permissions.
  • Do not create canaries or perform unauthorized access, path traversal, high-risk test commands, or active Agent probes.
  • Do not write to the assessed host state except for report output files explicitly requested by the user.
  • Mark checks as NOT_TESTED or ERROR when required read-only evidence cannot be obtained. Never guess PASS.
  • When NOT_TESTED appears, the OpenClaw Agent must perform each manualReview.requiredAction and record sanitized facts, source, time, and conclusion in a structured manual-review file.
  • Agent inference, source-code contracts, or explanations cannot produce PASS by themselves. PASS requires reviewable machine evidence from the current target host.
  • A manual review may address only a reviewId already present in the current baseline. It must not override a check that has no pending evidence gap.
  • This Skill does not validate public network reachability, real unauthorized third-party IM accounts, or remote SIEM delivery.
  • Do not automatically remediate findings. Remediation must be a separate task with explicit user authorization.
  • Even sanitized reports contain host security-posture information. Remind the user to handle them as internal security material.

Loading Reference Material

Read references/check-matrix.md before selecting checks. Read references/evidence-rules.md before assigning statuses. Read references/manual-review-evidence.md before processing manualReview. Read references/openclaw-contracts.md whenever OpenClaw CLI output, configuration structure, or version behavior is unclear.

Modes

  • baseline: Read configuration, CLI output, and host metadata from the current OpenClaw host; have the OpenClaw Agent perform targeted read-only review of NOT_TESTED observations; generate the merged formal report. This is the default mode.
  • report-only: Read an existing baseline JSON file and optionally merge an existing manual-review JSON file. Do not run OpenClaw or host assessment commands.

There is no active-validation mode. Do not create temporary files or elevate privileges to supplement dynamic evidence.

Baseline Workflow

  1. Confirm that the target is the current OpenClaw host and state which OpenClaw profile or state directory will be assessed.

  2. Run:

    node {baseDir}/scripts/host-baseline.mjs --json --output 
    
  3. Add --openclaw-bin , --openclaw-arg , --state-dir , or --config-path only in non-default runtime environments.

  4. Generate the initial report and manual-review template:

    node {baseDir}/scripts/report-merge.mjs \
      --baseline  \
      --review-template-out  \
      --json-out  \
      --markdown-out 
    
  5. Inspect fatal, ERROR, FAIL, WARN, every NOT_TESTED observation, and manualReview. Do not hide unavailable evidence.

  6. When manualReview.required=true, read references/manual-review-evidence.md and perform each requiredAction:

    • Run only the OpenClaw CLI, source-code lookup, and read-only host commands directly related to that evidence gap.
    • Do not perform broad host enumeration or active attack probes.
    • Record sanitized evidence and the conclusion in the observation for the corresponding reviewId in ``.
    • If the result is still indeterminate, use NOT_TESTED and record the read-only checks performed and the specific blocker.
  7. If the actual log file can be located, let the baseline script collect file-permission evidence directly:

    node {baseDir}/scripts/host-baseline.mjs \
      --json \
      --log-path  \
      --output 
    

    Regenerate the manual-review template after the baseline changes. The report script must reject an old template that no longer matches the new baseline.

  8. Merge the OpenClaw Agent's structured review evidence and generate the final outputs:

    node {baseDir}/scripts/report-merge.mjs \
      --baseline  \
      --manual-review  \
      --json-out  \
      --markdown-out 
    
  9. Inspect agentReview and the remaining manualReview. Retain NOT_TESTED only for items that still lack machine evidence.

Report-Only Workflow

  1. Do not run any OpenClaw or host assessment commands.

  2. Read the baseline JSON supplied by the user. If the user also supplies a manual-review JSON file, merge only that file and do not independently perform its host-review actions.

  3. Run:

    node {baseDir}/scripts/report-merge.mjs \
      --baseline  \
      --json-out  \
      --markdown-out 
    

    Add the following when merging existing structured review evidence:

    --manual-review 
    
  4. Return ERROR for invalid report input. Do not invent missing evidence.

  5. If the report still contains manualReview, clearly tell the user to return to the target OpenClaw host and perform the listed read-only reviews. report-only must not run those commands itself.

Deliverables

Return:

  • Overall status and counts.
  • Every FAIL, ERROR, WARN, and NOT_TESTED item with concise evidence.
  • Every merged agentReview, pending manualReview, and remaining evidence blocker.
  • Exact paths to the JSON and Markdown reports.
  • The exact path to the manual-review JSON file when used.
  • The selected mode, profile, or state directory.
  • The assurance boundary: only read-only evidence from the local host is covered.
  • A report-sensitivity notice and non-executing remediation guidance for non-PASS items.

Do not automatically remediate findings. If the user requests remediation, provide a separate, staged remediation plan and wait for explicit authorization.

Related skills

Free, local security self-audit for your own OpenClaw agent. Reads your OpenClaw config, bootstrap files, log files, agent session logs, and installed skills — read-only against your OpenClaw setup, plus a bounded host-security scan; writes only its own local report/history (removable with --purge). Scores your setup (A–F) and reports the most urgent holes. It changes nothing in your OpenClaw setup except through one opt-in, confirmation-gated command (--apply-ignore-proposals, which appends only suppressions you approved to .clawseccheckignore). No API key; the scanner itself makes no network calls, and the single external command it can run is your own read-only openclaw security audit (skip it with --no-native). Use it when you want to check or audit your OpenClaw agent's security, find prompt-injection or misconfiguration risks, or see your A–F security score.

4 installs2 stars

OpenClaw cloud security guardrail that enforces pre-execution checks, source trust classification, taint tracking, metadata endpoint blocking, and output red...

27 installs

Install and configure the security-related plugins required by OpenClaw, including the `claw-sentry` plugins. Use this skill when you want to complete instal...

28 installs

Subscribe AI agents to a community-curated security advisory feed for AI-agent threats.

by davida-ps103 installs1 stars

Run a fast OpenClaw Shield scan on a folder or file, then summarize severity counts, top findings, and recommended next actions.

10 installs

Advisory-feed monitoring, signed-trust verification, and approval-gated response for OpenClaw skills, bundled in one suite.

358 installs8 stars