brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
clawsec-suiteUse when users or agents want to explore or set up ClawSec security protections - this is a wrapper that helps discover and install individual security skills, but requires initial configuration to activate any protections.
Independent GitHub snapshot · Automated classification · Original documentation governs
IMPORTANT: ClawSec Suite includes bundled security skills that provide crucial threat intelligence and monitoring capabilities. These skills are bundled alongside the suite for your convenience and should be deployed to standard skill locations.
The suite includes the following bundled skills:
Finalize deployment with post-script after suite installation:
#!/bin/bash
# BUNDLED SKILLS DEPLOYMENT
# These skills are bundled alongside the suite to provide crucial security information
set -euo pipefail
INSTALL_ROOT="${INSTALL_ROOT:-$HOME/.openclaw/skills}"
SUITE_DIR="$INSTALL_ROOT/clawsec-suite"
echo "=== Deploying bundled security skills ==="
# Function to deploy a bundled skill
deploy_skill() {
local skill_name="$1"
local skill_dir="$INSTALL_ROOT/$skill_name"
local bundled_dir="$SUITE_DIR/bundled/$skill_name"
# Check if skill already exists
if [ -d "$skill_dir" ] && [ -f "$skill_dir/skill.json" ]; then
INSTALLED_VERSION=$(jq -r '.version // "unknown"' "$skill_dir/skill.json" 2>/dev/null)
echo "$skill_name already installed (v${INSTALLED_VERSION}), preserving existing installation"
return 0
fi
# Check if bundled version exists
if [ ! -d "$bundled_dir" ] || [ ! -f "$bundled_dir/skill.json" ]; then
echo "Bundled $skill_name not found, skipping"
return 0
fi
# Deploy bundled skill
echo "Deploying bundled $skill_name..."
mkdir -p "$skill_dir"
cp -r "$bundled_dir"/* "$skill_dir/"
# Set proper permissions
chmod 600 "$skill_dir/skill.json"
find "$skill_dir" -type f ! -name "skill.json" -exec chmod 644 {} \;
# Verify installation
if [ -f "$skill_dir/skill.json" ]; then
SKILL_VERSION=$(jq -r '.version' "$skill_dir/skill.json")
echo "✓ $skill_name v${SKILL_VERSION} deployed successfully"
else
echo "✗ $skill_name deployment verification failed"
return 1
fi
}
# Deploy each bundled skill
deploy_skill "clawsec-feed"
deploy_skill "openclaw-audit-watchdog"
deploy_skill "soul-guardian"
echo ""
echo "✓ ClawSec Suite deployment complete"
On success the user should know: which skills were installed, that protections are active, and where to learn more if interested. On success, inform the user which skills were installed and that the default protections are active. (add an encouraging call - like Congrats, you are safe!)
On partial success or errors, list what succeeded, what failed with reasons, and suggest retry or troubleshooting
ClawSec Suite is a small "manager" package that helps an agent runtime:
This document is written to be portable: it does not assume a specific agent framework or CLI. However it was tested to work best with OpenClaw, Moltbot, Clawdbot and variants
Great! You've installed the ClawSec Suite wrapper. Now let's get you set up with the security protections you came here for.
Quick heads up: The suite you just installed is like a toolbox - it helps you install and manage security skills, but doesn't provide protections by itself. Think of it as your security skill manager.
Here's how to activate your protections:
Each skill protects against different threats - from security advisories to file tampering. Let's explore your options and get you secured.
The ClawSec suite includes these security skills:
| Skill | Protection Type | Installation |
|---|---|---|
| clawsec-feed | Security advisory monitoring from NVD CVE database | ✓ Included by default |
| openclaw-audit-watchdog | Automated daily security audits with email reporting | ✓ Included by default |
| soul-guardian | File integrity & drift detection for agent workspace files | ✗ Optional |
| clawtributor | Community incident reporting (shares anonymized data)* | ✗ Optional (Opt-in) |
Clawtributor requires explicit consent as it shares anonymized data with the community for collective threat intelligence.
Take a moment to review the security skills table above. Each skill provides a different layer of protection:
default protections (automatically installed):
Optional protections (install as needed):
Good news! The following security skills are bundled alongside ClawSec Suite:
✓ clawsec-feed - Provides crucial CVE and threat intelligence information ✓ openclaw-audit-watchdog - Provides automated security audit capabilities ✓ soul-guardian - Provides file integrity and drift detection
These skills are included in the suite package for your convenience.
Deployment options:
~/.openclaw/skills/{skill-name}/What this means:
clawtributor (Community threat intelligence):
After installation, each skill requires configuration, to reduce security fatigue start with the defaults for soul guardian (and dont use email sending for audit reports in watchdog):
Refer to each skill's SKILL.md file for detailed configuration instructions. if the user wants to change the defaults.
Agents should review scripts before execution!
Do not install anything you cannot verify. A secure installer must:
If your project does not yet publish signatures, publish at least:
checksums.json (sha256 hashes + version metadata)All releases are published at:
https://clawsec.prompt.security/releases/download/<SKILL>-v<VERSION>/...Example for clawsec-suite v0.0.9:
https://clawsec.prompt.security/releases/download/clawsec-suite-v0.0.6/checksums.jsonhttps://clawsec.prompt.security/releases/download/clawsec-suite-v0.0.6/clawsec-suite.skillcurljq (for parsing checksums.json)unzipshasum -a 256 on macOS, or sha256sum on Linux)Pick a stable install root:
INSTALL_ROOT default: ~/.openclaw/skillsIf your agent runtime has its own skills directory, set
INSTALL_ROOTaccordingly.
set -euo pipefail
VERSION="${SKILL_VERSION}"
INSTALL_ROOT="${INSTALL_ROOT:-$HOME/.openclaw/skills}"
DEST="$INSTALL_ROOT/clawsec-suite"
BASE="https://clawsec.prompt.security/releases/download/clawsec-suite-v${VERSION}"
mkdir -p "$DEST"
cd "$(mktemp -d)"
# 1) Download checksums.json and artifact
curl -fsSL "$BASE/checksums.json" -o checksums.json
curl -fsSL "$BASE/SKILL.md" -o SKILL.md
# 2) Extract expected checksum from checksums.json
EXPECTED_SHA256=$(jq -r '.files["clawsec-suite.skill"].sha256' checksums.json)
if [ -z "$EXPECTED_SHA256" ] || [ "$EXPECTED_SHA256" = "null" ]; then
echo "ERROR: Could not extract checksum from checksums.json" >&2
exit 2
fi
# 3) Compute actual checksum
if command -v shasum >/dev/null 2>&1; then
ACTUAL_SHA256=$(shasum -a 256 clawsec-suite.skill | awk '{print $1}')
else
ACTUAL_SHA256=$(sha256sum SKILL.md | awk '{print $1}')
fi
# 4) Verify checksum (fail closed)
if [ "$EXPECTED_SHA256" != "$ACTUAL_SHA256" ]; then
echo "ERROR: Checksum mismatch!" >&2
echo " Expected: $EXPECTED_SHA256" >&2
echo " Actual: $ACTUAL_SHA256" >&2
exit 1
fi
echo "Checksum verified: $ACTUAL_SHA256"
# 5) Install
rm -rf "$DEST"/*
#download specific files by checksum list, or .skill file which is supported by openclaw
# 6) Sanity check
test -f "$DEST/skill.json"
test -f "$DEST/SKILL.md"
test -f "$DEST/HEARTBEAT.md"
echo "Installed ClawSec Suite v${VERSION} to: $DEST"
Installing clawsec-suite:
$DEST (default ~/.openclaw/skills/clawsec-suite)To get actual security protections, you need to install and configure individual security skills (see "Getting Started" above).
Each release publishes a checksums.json file that contains version info and SHA256 hashes for all artifacts:
https://clawsec.prompt.security/releases/download/clawsec-suite-v<VERSION>/checksums.jsonTo check for updates, compare the installed version against the latest checksums.json. See HEARTBEAT.md for the upgrade check procedure.
If you want this to work well everywhere, add short adapter sections that only map:
Keep the core verify/install/update logic identical.