skill-security_skill

This skill performs automated security audits on new OpenClaw skills, detecting credential harvesting, code injection, network exfiltration, and obfuscation
  • Python

2.5k

GitHub Stars

7

Bundled Files

3 weeks ago

Catalog Refreshed

1 month ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstart where the catalogue uses aiagentskills.

npx veilstart add skill openclaw/skills --skill skill-security

  • _meta.json289 B
  • allowlist.txt495 B
  • audit-all.sh2.6 KB
  • audit.sh3.9 KB
  • blocklist.txt61 B
  • preinstall-check.sh1.4 KB
  • SKILL.md3.1 KB

Overview

This skill is a security audit tool for OpenClaw skills that scans code for credential harvesting, code injection, network exfiltration, obfuscation, and other risky patterns. It is designed to run before installing or loading any external skill to prevent malicious activity. The scanner categorizes findings by severity and can automatically block or flag problematic skills.

How this skill works

The scanner searches skill source code for risky patterns such as network libraries, credential file paths, dynamic code execution, obfuscated payloads, environment dumping, and subprocess usage. It assigns severity levels (CRITICAL, HIGH, MEDIUM, LOW) and produces a report; CRITICAL findings are added to a blocklist and prevent installation. Manual override and allowlist entries are supported for verified exceptions.

When to use it

  • Before installing any new skill from external or untrusted sources
  • During routine security audits of installed skills
  • As part of a CI pipeline that validates skills before deployment
  • When reviewing skill updates or new versions
  • Before enabling skills from archived or community repositories

Best practices

  • Always audit new or updated skills before loading them into the agent
  • Treat CRITICAL and HIGH findings as blockers until reviewed and explained
  • Verify any network or credential access by checking documentation and scoped file paths
  • Keep the blocklist and allowlist under version control and document overrides
  • Combine static scanning with a manual code review for MEDIUM severity items

Example use cases

  • Scan a downloaded skill directory to detect remote exfiltration attempts
  • Run batch audits across all installed skills before a system upgrade
  • Integrate the scanner in CI to fail builds when CRITICAL patterns are detected
  • Create an allowlist entry after manual verification of a flagged skill
  • Use the report to instruct authors on required security fixes before acceptance

FAQ

CRITICAL findings block installation and the skill is added to the blocklist until the issue is resolved or explicitly allowed by a verified override.

Can I trust the scanner to catch every malicious pattern?

No scanner is perfect. This tool finds common risky patterns and automates initial triage, but should be paired with manual review and runtime monitoring for full protection.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational