Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Policy-based compliance assessment for OpenClaw skills. Define security policies, assess skills against them, track violations, and generate compliance repor...
Policy-based compliance assessment for OpenClaw skills. Define security policies, assess skills against them, track violations, and generate compliance repor...
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. 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. Summarize what changed and any follow-up checks I should run.
Assess OpenClaw skills against defined security policies. Track compliance posture across your skill inventory with framework-mapped findings and remediation tracking.
Security scanners find vulnerabilities. Trust verifiers check provenance. But neither answers: "Does this skill meet our security policy?" Compliance Checker bridges the gap โ define what "compliant" means for your environment, then assess every skill against those rules.
python3 {baseDir}/scripts/checker.py policy create --name "production" --description "Production deployment requirements"
python3 {baseDir}/scripts/checker.py policy add-rule --policy "production" \ --rule "no-critical-findings" \ --description "No CRITICAL findings from skill scanner" \ --severity critical python3 {baseDir}/scripts/checker.py policy add-rule --policy "production" \ --rule "trust-verified" \ --description "Must have VERIFIED or TRUSTED trust level" \ --severity high python3 {baseDir}/scripts/checker.py policy add-rule --policy "production" \ --rule "no-network-calls" \ --description "No unauthorized network calls in scripts" \ --severity high python3 {baseDir}/scripts/checker.py policy add-rule --policy "production" \ --rule "no-shell-exec" \ --description "No shell=True or subprocess calls" \ --severity medium python3 {baseDir}/scripts/checker.py policy add-rule --policy "production" \ --rule "has-checksum" \ --description "Must have SHA-256 checksums for all scripts" \ --severity medium
python3 {baseDir}/scripts/checker.py assess --skill "arc-budget-tracker" --policy "production"
python3 {baseDir}/scripts/checker.py assess-all --policy "production"
python3 {baseDir}/scripts/checker.py status --policy "production"
python3 {baseDir}/scripts/checker.py report --policy "production" --format json python3 {baseDir}/scripts/checker.py report --policy "production" --format text
The following rules are available out of the box: RuleWhat it checksFramework mappingno-critical-findingsNo CRITICAL findings from scannerCIS Control 16, OWASP A06no-high-findingsNo HIGH findings from scannerCIS Control 16, OWASP A06trust-verifiedTrust level is VERIFIED or TRUSTEDCIS Control 2no-network-callsNo unauthorized network requestsCIS Control 9, OWASP A10no-shell-execNo shell execution patternsCIS Control 2, OWASP A03no-eval-execNo eval/exec patternsOWASP A03has-checksumSHA-256 checksums for all filesCIS Control 2no-env-accessNo environment variable accessCIS Control 3no-data-exfilNo data exfiltration patternsCIS Control 3, CIS Control 13version-pinnedAll dependencies version-pinnedCIS Control 2
Each skill-policy assessment produces one of: COMPLIANT โ Passes all rules in the policy NON-COMPLIANT โ Fails one or more rules EXEMPTED โ Has approved exemptions for all failures UNKNOWN โ Not yet assessed
Sometimes a skill legitimately needs to violate a rule (e.g., a network monitoring skill needs network access). Record exemptions with justification: python3 {baseDir}/scripts/checker.py exempt --skill "arc-skill-scanner" \ --rule "no-network-calls" \ --reason "Scanner needs network access to check URLs against blocklists" \ --approved-by "arc"
When a skill fails compliance, track the fix: python3 {baseDir}/scripts/checker.py remediate --skill "some-skill" \ --rule "no-shell-exec" \ --action "Replaced subprocess.call with safer alternative" \ --status fixed
Compliance data is stored in ~/.openclaw/compliance/: policies/ โ Policy definitions (JSON) assessments/ โ Assessment results per skill (JSON) exemptions/ โ Approved exemptions (JSON) remediations/ โ Remediation tracking (JSON)
Compliance Checker reads output from: arc-skill-scanner โ vulnerability findings arc-trust-verifier โ trust levels and attestations Run a full pipeline: # Scan โ verify trust โ assess compliance python3 {baseDir}/scripts/checker.py pipeline --skill "some-skill" --policy "production"
Identity, auth, scanning, governance, audit, and operational guardrails.
Largest current source with strong distribution and engagement signals.