Source profileQuality 91/100Review permissions

aAAaqwq/AGI-Super-Team/skills/ai-shield-audit/SKILL.md

openclaw-shield

Security audit engine for OpenClaw configurations. Detects vulnerabilities, misconfigurations, secret leaks, and over-privileged agents. Use when the user asks about security, hardening, config review, or audit of their OpenClaw setup.

Source repository stars
89
Declared platforms
0
Static risk flags
1
Last source update
2026-08-26
Source checked
2026-08-28

Decision brief

What it does: where it fits

Audit any OpenClaw config for security vulnerabilities, misconfigurations, and best-practice violations. Produces a structured JSON report with risk scores, findings, and remediation steps.

Best for

  • User asks to check/audit/review their OpenClaw security
  • User wants to harden their config before deploying
  • User is setting up a new OpenClaw instance

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/aAAaqwq/AGI-Super-Team --skill "skills/ai-shield-audit"
Safe inspection promptEditorial

Inspect the Agent Skill "openclaw-shield" from https://github.com/aAAaqwq/AGI-Super-Team/blob/bfcfb64081f94e5869ff420aaaed63b6da716bc6/skills/ai-shield-audit/SKILL.md at commit bfcfb64081f94e5869ff420aaaed63b6da716bc6. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Usage

    Review the “Usage” section in the pinned source before continuing.

    Review and apply the “Usage” source section.
  2. 02

    Workflow for Agent

    1. Load the user's config: cat /.openclaw/openclaw.json 2. Run: node SKILLDIR/bin/shield.js audit /.openclaw/openclaw.json --summary 3. Present findings to user with prioritized recommendations 4. Offer to sanitize before sharing: node SKILLDIR/bin/shield.js sanitize

    Load the user's config: cat /.openclaw/openclaw.jsonRun: node SKILLDIR/bin/shield.js audit /.openclaw/openclaw.json --summaryPresent findings to user with prioritized recommendations
  3. 03

    When to Use

    User asks to check/audit/review their OpenClaw security

    User asks to check/audit/review their OpenClaw securityUser wants to harden their config before deployingUser is setting up a new OpenClaw instance
  4. 04

    Quick Audit (live config)

    Review the “Quick Audit (live config)” section in the pinned source before continuing.

    Review and apply the “Quick Audit (live config)” source section.

Permission review

Static risk signals and limitations

Runs scripts

medium · line 17

The documentation asks the agent to run terminal commands or scripts.

node scripts/shield-audit.sh

Runs scripts

medium · line 23

The documentation asks the agent to run terminal commands or scripts.

node SKILL_DIR/bin/shield.js audit ~/.openclaw/openclaw.json --summary

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score91/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars89SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
aAAaqwq/AGI-Super-Team
Skill path
skills/ai-shield-audit/SKILL.md
Commit
bfcfb64081f94e5869ff420aaaed63b6da716bc6
License
MIT
Collected
2026-08-28
Default branch
main
View the original SKILL.md

OpenClaw Shield — Security Audit

Audit any OpenClaw config for security vulnerabilities, misconfigurations, and best-practice violations. Produces a structured JSON report with risk scores, findings, and remediation steps.

When to Use

  • User asks to check/audit/review their OpenClaw security
  • User wants to harden their config before deploying
  • User is setting up a new OpenClaw instance
  • User asks about secret leakage or API key exposure in their config
  • Before publishing or sharing any config file

Quick Audit (live config)

node scripts/shield-audit.sh

Or directly:

node SKILL_DIR/bin/shield.js audit ~/.openclaw/openclaw.json --summary

What It Checks (11 categories)

  1. Gateway Auth — missing/weak auth, insecure UI settings
  2. Network Exposure — bind address, Tailscale funnel, wildcard proxies
  3. Channel Security — wildcard allowFrom, missing allowlists
  4. DM Policy — open DM policy without pairing
  5. Subagent Permissions — wildcard allowAgents, circular delegation chains, self-delegation
  6. Tool Permissions — over-privileged agents with tools.profile: "full"
  7. Secret Leakage — API keys, tokens, private keys in plaintext config
  8. Sandbox/Execution — missing workspace isolation, no execution policies
  9. Plugin Config — enabled plugins without channel config
  10. Heartbeat Exposure — sensitive data in heartbeat prompts
  11. Remote Config — unencrypted WebSocket, exposed remote URLs/tokens

Usage

Audit a config file

node SKILL_DIR/bin/shield.js audit <config.json>
node SKILL_DIR/bin/shield.js audit <config.json> --summary   # human-readable

Audit from stdin

cat config.json | node SKILL_DIR/bin/shield.js audit --stdin

Sanitize a config (strip secrets)

node SKILL_DIR/bin/shield.js sanitize <config.json>

Programmatic use

const { auditConfig } = require('SKILL_DIR/src/audit');
const config = require('./openclaw.json');
const report = auditConfig(config);
console.log(report.risk_level);      // "CRITICAL" | "HIGH" | "MEDIUM" | "LOW"
console.log(report.overall_score);   // 0-100
console.log(report.vulnerabilities); // detailed findings

Output

Returns JSON with: risk_level, overall_score (0-100), vulnerabilities[], vulnerability_count, best_practices_compliance, action_recommended, safe_to_deploy, audit_timestamp.

Workflow for Agent

  1. Load the user's config: cat ~/.openclaw/openclaw.json
  2. Run: node SKILL_DIR/bin/shield.js audit ~/.openclaw/openclaw.json --summary
  3. Present findings to user with prioritized recommendations
  4. Offer to sanitize before sharing: node SKILL_DIR/bin/shield.js sanitize <file>

Frequently asked questions

What to verify before installation and use

What does the openclaw-shield source document cover?

Audit any OpenClaw config for security vulnerabilities, misconfigurations, and best-practice violations. Produces a structured JSON report with risk scores, findings, and remediation steps.

How do I install openclaw-shield?

The source record exposes this install command: npx skills add https://github.com/aAAaqwq/AGI-Super-Team --skill "skills/ai-shield-audit". Inspect the command and pinned source before running it.

Which permission-related actions were detected?

Static rules flagged exec-script in the source; the page lists the matching lines and excerpts.

Alternatives

Compare before choosing

Computed 10029,236

garrytan/gbrain

bulk-ingestion

End-to-end discipline for turning any large data source (audio libraries, email takeouts, document corpora, chat exports, API dumps) into brain pages at scale. The lifecycle spine: SCHEMA → ACCESS → TRIAL → EVALUATE → IMPROVE → CODIFY → TEST → SKILLIFY → BULK → MONITOR. State is tracked in a durable JSON manifest (see MANIFEST-PATTERN.md) so any crash, session boundary, or subagent fan-out resumes from ground truth instead of memory.

Computed 10025,136

alirezarezvani/claude-skills

app-store-optimization

App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist

Computed 10015,385

wanshuiyin/Auto-claude-code-research-in-sleep

citation-audit

Use it for operations and research tasks; the detail page covers purpose, installation, and practical steps.

Computed 10014,706

prowler-cloud/prowler

postgresql-indexing

PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing index usage statistics, reindexing, dropping indexes, or working with partitioned table indexes. Also trigger when discussing index strategies, partial indexes, or index maintenance