Is openclaw-config safe to install?

SaferSkills independently audited openclaw-config (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

.claude/skills/openclaw-config/SKILL.md · 1 file

.claude/skills/openclaw-config/SKILL.md1.0 KB · Markdown

/openclaw-config

Generate or update an openclaw.json config for a deployed stack.

Steps

Read the OpenClaw version from spec/openclaw-versions.yaml to check compatibility quirks.

Generate `openclaw.json` using the provider adapter's config template:

Model provider section (Bedrock, Anthropic API, etc.)
Channel configuration
Gateway auth mode

Bedrock / AWS compatibility note:

OpenClaw 2026.4.5+ requires AWS_PROFILE in the systemd EnvironmentFile=, NOT auth: "aws-sdk" in openclaw.json. The AWS adapter must emit BOTH for backwards compatibility. See spec/openclaw-versions.yaml.

Secrets are always references (env var names, ARNs), never inline values. Per R6.

Apply the config via clawops config set <key> <value> or during clawops up.

Output format

{
  "version": "2026.4",
  "gateway": {
    "port": 18789,
    "auth": { "mode": "token" }
  },
  "models": {},
  "channels": {}
}

openclaw-config— agent skill

Is openclaw-config safe to install?

/openclaw-config

Steps

Output format

Audit the pieces. Scan the whole. Decide.