Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Legal/compliance guardrails for outbound OpenClaw actions (anti-spam, defamation, privacy, financial claims).
Legal/compliance guardrails for outbound OpenClaw actions (anti-spam, defamation, privacy, financial claims).
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Use this skill to preflight bot output before posting, messaging, or publishing anything that could create legal/compliance risk.
A generic outbound guardrail checker used by workflows before execute actions such as post/comment/message/chat/send in any app.
Before create_post, create_comment, send_message, or equivalent publish actions. Before market-related commentary, strategy claims, or price/certainty statements. Before HR-sensitive or workplace-adjacent messaging. Before anti-spam or coordination-heavy communications. Before handling or exposing personal identifiers.
Draft text. Run the checker with the matching action/profile. If result is PASS/WATCH, proceed. If REVIEW, rewrite or route for human/legal review. If BLOCK, do not execute. Use it as a shared OpenClaw outbound safety layer for any skill that publishes content. Babylon is only one current integration example, not the primary purpose of the skill.
python3 scripts/check_enterprise_guardrails.py \ --action post \ --app <app_name> \ --policies social antispam hr \ --text "Draft text here" python3 scripts/check_enterprise_guardrails.py \ --action comment \ --scope include \ --apps whatsapp,telegram \ --text "Draft text here" python3 scripts/check_enterprise_guardrails.py \ --action market-analysis \ --text "Market commentary..." \ --json
Scope applies to any app-context passed with --app and these env vars (legacy names preserved for compatibility): ENTERPRISE_LEGAL_GUARDRAILS_OUTBOUND_SCOPE (all|include|exclude) ENTERPRISE_LEGAL_GUARDRAILS_OUTBOUND_APPS (comma-separated list) BABYLON_GUARDRAILS_SCOPE BABYLON_GUARDRAILS_OUTBOUND_SCOPE BABYLON_GUARDRAILS_APPS Examples: all: check all outbound content. include + whatsapp,email: only check those apps. exclude + whatsapp,email,moltbook,babylon: everything except these apps. If scope is omitted, default is all.
social: public social text, comments, announcements. antispam: unsolicited/pumping/coordinating messaging. hr: workplace, hiring, performance, or employee conduct language. privacy: personally identifying data and private information disclosures. market: market/financial claims and outcome assertions. legal: legal conclusions/implication language. If no profile is provided, defaults are derived from --action: post|comment|message โ social,legal trade|market-analysis โ market,financial generic โ legal,social
PASS: safe to execute WATCH: low risk; optional rewrite REVIEW: human/legal review recommended BLOCK: do not execute
You can tune decision sensitivity via environment variables (or CLI flags in direct runs): ENTERPRISE_LEGAL_GUARDRAILS_REVIEW_THRESHOLD (default: 5) ENTERPRISE_LEGAL_GUARDRAILS_BLOCK_THRESHOLD (default: 9) CLI overrides: --review-threshold --block-threshold Legacy aliases are supported in legacy env names: ELG_* and BABYLON_GUARDRAILS_*.
For skills/tools without native guardrail hooks (for example: Gmail, custom website publishing, custom message bots), run outbound operations through the wrapper: python3 /path/to/enterprise-legal-guardrails/scripts/guard_and_run.py --app <app_name> --action <post|comment|message|trade|market-analysis|generic> --text "$DRAFT" -- <outbound command...> Examples: # Gmail via gog python3 /path/to/enterprise-legal-guardrails/scripts/guard_and_run.py --app gmail --action message --text "Hello, ..." -- gog gmail send --to user@domain.com --subject "Update" --body "Hello, ..." # Website/publication publish flow python3 /path/to/enterprise-legal-guardrails/scripts/guard_and_run.py --app website --action post --text "$POST_COPY" -- npm run publish-post "$POST_COPY" Use this wrapper to apply the same policy checks in non-Babylon outbound flows.
Legacy name legal-risk-checker is preserved in OpenClaw workspaces that still reference it.
See references/guardrail-policy-map.md for the full policy rule set and suggested rewrites.
A distributable bundle is available at: dist/enterprise-legal-guardrails.skill
For non-native outbound integrations, treat guard_and_run as an execution boundary. Recommended flags/env: Execution safety is allowlist-first by default. Wrapper requires explicit --allowed-command (or env alias) unless --allow-any-command is explicitly enabled. --allow-any-command / ENTERPRISE_LEGAL_GUARDRAILS_ALLOW_ANY_COMMAND Explicitly bypass allowlist enforcement (unsafe; audit-first use only). --suppress-allow-any-warning / ENTERPRISE_LEGAL_GUARDRAILS_SUPPRESS_ALLOW_ANY_WARNING Suppresses the runtime safety warning when --allow-any-command is intentionally enabled. --allow-any-command-reason / ENTERPRISE_LEGAL_GUARDRAILS_ALLOW_ANY_COMMAND_REASON Mandatory rationale for any allow-any bypass invocation. Suggested format: SEC-1234: emergency fix. --allow-any-command-approval-token / ENTERPRISE_LEGAL_GUARDRAILS_ALLOW_ANY_COMMAND_APPROVAL_TOKEN Mandatory approval token for any allow-any bypass invocation; stored as a short token fingerprint in audit logs. --allowed-command <exe...> / ENTERPRISE_LEGAL_GUARDRAILS_ALLOWED_COMMANDS Allow-list executables (supports comma/space lists and wildcards). --strict / ENTERPRISE_LEGAL_GUARDRAILS_STRICT Escalate REVIEW to hard block. --sanitize-env --keep-env <VAR...> / --keep-env-prefix <PREFIX...> --command-timeout, --checker-timeout, --max-text-bytes --audit-log <file> / ENTERPRISE_LEGAL_GUARDRAILS_AUDIT_LOG These flags provide execution safety, command scoping, and immutable trail for post-incident review without changing checker logic.
Identity, auth, scanning, governance, audit, and operational guardrails.
Largest current source with strong distribution and engagement signals.