[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7715X5E22JS2MKK3W2DAGVQ":3,"skill-same:01M7715X5E22JS2MKK3W2DAGVQ":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":41,"updatedAt":42,"install":43,"resources":55},"01M7715X5E22JS2MKK3W2DAGVQ","compliance-checker",null,"Policy-based compliance assessment for OpenClaw skills. Define security policies, assess skills against them, track violations, and generate compliance reports. Maps findings to frameworks like CIS Controls and OWASP. Integrates with arc-skill-scanner and arc-trust-verifier.","javimosch\u002Fopen-claw-skills","javimosch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12900508?v=4","01M6D3F2AS6PV75ET9PZ1QGP8J","Javier Leandro Arancibia","01M75B8NCTAJG9WH5YNZH7C3D8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftrypto1019\u002Farc-compliance-checker\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: compliance-checker\ndescription: Policy-based compliance assessment for OpenClaw skills. Define security policies, assess skills against them, track violations, and generate compliance reports. Maps findings to frameworks like CIS Controls and OWASP. Integrates with arc-skill-scanner and arc-trust-verifier.\nuser-invocable: true\nmetadata: {\"openclaw\": {\"emoji\": \"🛡️\", \"os\": [\"darwin\", \"linux\"], \"requires\": {\"bins\": [\"python3\"]}}}\n---\n\n# Compliance Checker\n\nAssess OpenClaw skills against defined security policies. Track compliance posture across your skill inventory with framework-mapped findings and remediation tracking.\n\n## Why This Exists\n\nSecurity 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.\n\n## Quick Start\n\n### Define a policy\n```bash\npython3 {baseDir}\u002Fscripts\u002Fchecker.py policy create --name \"production\" --description \"Production deployment requirements\"\n```\n\n### Add rules to the policy\n```bash\npython3 {baseDir}\u002Fscripts\u002Fchecker.py policy add-rule --policy \"production\" \\\n  --rule \"no-critical-findings\" \\\n  --description \"No CRITICAL findings from skill scanner\" \\\n  --severity critical\n\npython3 {baseDir}\u002Fscripts\u002Fchecker.py policy add-rule --policy \"production\" \\\n  --rule \"trust-verified\" \\\n  --description \"Must have VERIFIED or TRUSTED trust level\" \\\n  --severity high\n\npython3 {baseDir}\u002Fscripts\u002Fchecker.py policy add-rule --policy \"production\" \\\n  --rule \"no-network-calls\" \\\n  --description \"No unauthorized network calls in scripts\" \\\n  --severity high\n\npython3 {baseDir}\u002Fscripts\u002Fchecker.py policy add-rule --policy \"production\" \\\n  --rule \"no-shell-exec\" \\\n  --description \"No shell=True or subprocess calls\" \\\n  --severity medium\n\npython3 {baseDir}\u002Fscripts\u002Fchecker.py policy add-rule --policy \"production\" \\\n  --rule \"has-checksum\" \\\n  --description \"Must have SHA-256 checksums for all scripts\" \\\n  --severity medium\n```\n\n### Assess a skill against a policy\n```bash\npython3 {baseDir}\u002Fscripts\u002Fchecker.py assess --skill \"arc-budget-tracker\" --policy \"production\"\n```\n\n### Assess all installed skills\n```bash\npython3 {baseDir}\u002Fscripts\u002Fchecker.py assess-all --policy \"production\"\n```\n\n### View compliance status\n```bash\npython3 {baseDir}\u002Fscripts\u002Fchecker.py status --policy \"production\"\n```\n\n### Generate compliance report\n```bash\npython3 {baseDir}\u002Fscripts\u002Fchecker.py report --policy \"production\" --format json\npython3 {baseDir}\u002Fscripts\u002Fchecker.py report --policy \"production\" --format text\n```\n\n## Built-in Rules\n\nThe following rules are available out of the box:\n\n| Rule | What it checks | Framework mapping |\n|------|---------------|-------------------|\n| `no-critical-findings` | No CRITICAL findings from scanner | CIS Control 16, OWASP A06 |\n| `no-high-findings` | No HIGH findings from scanner | CIS Control 16, OWASP A06 |\n| `trust-verified` | Trust level is VERIFIED or TRUSTED | CIS Control 2 |\n| `no-network-calls` | No unauthorized network requests | CIS Control 9, OWASP A10 |\n| `no-shell-exec` | No shell execution patterns | CIS Control 2, OWASP A03 |\n| `no-eval-exec` | No eval\u002Fexec patterns | OWASP A03 |\n| `has-checksum` | SHA-256 checksums for all files | CIS Control 2 |\n| `no-env-access` | No environment variable access | CIS Control 3 |\n| `no-data-exfil` | No data exfiltration patterns | CIS Control 3, CIS Control 13 |\n| `version-pinned` | All dependencies version-pinned | CIS Control 2 |\n\n## Compliance Status\n\nEach skill-policy assessment produces one of:\n\n- **COMPLIANT** — Passes all rules in the policy\n- **NON-COMPLIANT** — Fails one or more rules\n- **EXEMPTED** — Has approved exemptions for all failures\n- **UNKNOWN** — Not yet assessed\n\n## Exemptions\n\nSometimes a skill legitimately needs to violate a rule (e.g., a network monitoring skill needs network access). Record exemptions with justification:\n\n```bash\npython3 {baseDir}\u002Fscripts\u002Fchecker.py exempt --skill \"arc-skill-scanner\" \\\n  --rule \"no-network-calls\" \\\n  --reason \"Scanner needs network access to check URLs against blocklists\" \\\n  --approved-by \"arc\"\n```\n\n## Remediation Tracking\n\nWhen a skill fails compliance, track the fix:\n\n```bash\npython3 {baseDir}\u002Fscripts\u002Fchecker.py remediate --skill \"some-skill\" \\\n  --rule \"no-shell-exec\" \\\n  --action \"Replaced subprocess.call with safer alternative\" \\\n  --status fixed\n```\n\n## Storage\n\nCompliance data is stored in `~\u002F.openclaw\u002Fcompliance\u002F`:\n- `policies\u002F` — Policy definitions (JSON)\n- `assessments\u002F` — Assessment results per skill (JSON)\n- `exemptions\u002F` — Approved exemptions (JSON)\n- `remediations\u002F` — Remediation tracking (JSON)\n\n## Integration\n\nCompliance Checker reads output from:\n- **arc-skill-scanner** — vulnerability findings\n- **arc-trust-verifier** — trust levels and attestations\n\nRun a full pipeline:\n```bash\n# Scan → verify trust → assess compliance\npython3 {baseDir}\u002Fscripts\u002Fchecker.py pipeline --skill \"some-skill\" --policy \"production\"\n```\n","# Compliance Checker\n\nAssess OpenClaw skills against defined security policies. Track compliance posture across your skill inventory with framework-mapped findings and remediation tracking.\n\n## Why This Exists\n\nSecurity 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.\n\n## Quick Start\n\n### Define a policy\n```bash\npython3 {baseDir}\u002Fscripts\u002Fchecker.py policy create --name \"production\" --description \"Production deployment requirements\"\n```\n\n### Add rules to the policy\n```bash\npython3 {baseDir}\u002Fscripts\u002Fchecker.py policy add-rule --policy \"production\" \\\n  --rule \"no-critical-findings\" \\\n  --description \"No CRITICAL findings from skill scanner\" \\\n  --severity critical\n\npython3 {baseDir}\u002Fscripts\u002Fchecker.py policy add-rule --policy \"production\" \\\n  --rule \"trust-verified\" \\\n  --description \"Must have VERIFIED or TRUSTED trust level\" \\\n  --severity high\n\npython3 {baseDir}\u002Fscripts\u002Fchecker.py policy add-rule --policy \"production\" \\\n  --rule \"no-network-calls\" \\\n  --description \"No unauthorized network calls in scripts\" \\\n  --severity high\n\npython3 {baseDir}\u002Fscripts\u002Fchecker.py policy add-rule --policy \"production\" \\\n  --rule \"no-shell-exec\" \\\n  --description \"No shell=True or subprocess calls\" \\\n  --severity medium\n\npython3 {baseDir}\u002Fscripts\u002Fchecker.py policy add-rule --policy \"production\" \\\n  --rule \"has-checksum\" \\\n  --description \"Must have SHA-256 checksums for all scripts\" \\\n  --severity medium\n```\n\n### Assess a skill against a policy\n```bash\npython3 {baseDir}\u002Fscripts\u002Fchecker.py assess --skill \"arc-budget-tracker\" --policy \"production\"\n```\n\n### Assess all installed skills\n```bash\npython3 {baseDir}\u002Fscripts\u002Fchecker.py assess-all --policy \"production\"\n```\n\n### View compliance status\n```bash\npython3 {baseDir}\u002Fscripts\u002Fchecker.py status --policy \"production\"\n```\n\n### Generate compliance report\n```bash\npython3 {baseDir}\u002Fscripts\u002Fchecker.py report --policy \"production\" --format json\npython3 {baseDir}\u002Fscripts\u002Fchecker.py report --policy \"production\" --format text\n```\n\n## Built-in Rules\n\nThe following rules are available out of the box:\n\n| Rule | What it checks | Framework mapping |\n|------|---------------|-------------------|\n| `no-critical-findings` | No CRITICAL findings from scanner | CIS Control 16, OWASP A06 |\n| `no-high-findings` | No HIGH findings from scanner | CIS Control 16, OWASP A06 |\n| `trust-verified` | Trust level is VERIFIED or TRUSTED | CIS Control 2 |\n| `no-network-calls` | No unauthorized network requests | CIS Control 9, OWASP A10 |\n| `no-shell-exec` | No shell execution patterns | CIS Control 2, OWASP A03 |\n| `no-eval-exec` | No eval\u002Fexec patterns | OWASP A03 |\n| `has-checksum` | SHA-256 checksums for all files | CIS Control 2 |\n| `no-env-access` | No environment variable access | CIS Control 3 |\n| `no-data-exfil` | No data exfiltration patterns | CIS Control 3, CIS Control 13 |\n| `version-pinned` | All dependencies version-pinned | CIS Control 2 |\n\n## Compliance Status\n\nEach skill-policy assessment produces one of:\n\n- **COMPLIANT** — Passes all rules in the policy\n- **NON-COMPLIANT** — Fails one or more rules\n- **EXEMPTED** — Has approved exemptions for all failures\n- **UNKNOWN** — Not yet assessed\n\n## Exemptions\n\nSometimes a skill legitimately needs to violate a rule (e.g., a network monitoring skill needs network access). Record exemptions with justification:\n\n```bash\npython3 {baseDir}\u002Fscripts\u002Fchecker.py exempt --skill \"arc-skill-scanner\" \\\n  --rule \"no-network-calls\" \\\n  --reason \"Scanner needs network access to check URLs against blocklists\" \\\n  --approved-by \"arc\"\n```\n\n## Remediation Tracking\n\nWhen a skill fails compliance, track the fix:\n\n```bash\npython3 {baseDir}\u002Fscripts\u002Fchecker.py remediate --skill \"some-skill\" \\\n  --rule \"no-shell-exec\" \\\n  --action \"Replaced subprocess.call with safer alternative\" \\\n  --status fixed\n```\n\n## Storage\n\nCompliance data is stored in `~\u002F.openclaw\u002Fcompliance\u002F`:\n- `policies\u002F` — Policy definitions (JSON)\n- `assessments\u002F` — Assessment results per skill (JSON)\n- `exemptions\u002F` — Approved exemptions (JSON)\n- `remediations\u002F` — Remediation tracking (JSON)\n\n## Integration\n\nCompliance Checker reads output from:\n- **arc-skill-scanner** — vulnerability findings\n- **arc-trust-verifier** — trust levels and attestations\n\nRun a full pipeline:\n```bash\n# Scan → verify trust → assess compliance\npython3 {baseDir}\u002Fscripts\u002Fchecker.py pipeline --skill \"some-skill\" --policy \"production\"\n```\n",{"name":5,"metadata":24,"description":7,"user-invocable":33},{"openclaw":25},{"os":26,"emoji":29,"requires":30},[27,28],"darwin","linux","🛡️",{"bins":31},[32],"python3",true,"main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Ftrypto1019\u002Farc-compliance-checker",1,"https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills","https:\u002F\u002Fgithub.com\u002Fjavimosch","intrane.fr","Building robust, open-source infrastructure for the commons. AI-leveraged, self-hosted, built to last.","2026-06-07 03:34:58",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":33},[45,48,51],{"tool":46,"command":47},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill compliance-checker",{"tool":49,"command":50},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill compliance-checker",{"tool":52,"command":53},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill compliance-checker","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftrypto1019\u002Farc-compliance-checker\u002FSKILL.md",[],[57,65,72,79,86,93],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":64},"01M778GGXG2VQ0YF31W2MKGMQZ","crowd-prompting","A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":64},"01M778G7BH8SBJ9FJ6C3G7CB1K","ceaser","Interact with the Ceaser privacy protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- shield, unshield, note management, and protocol queries. All ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir\u002FUltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":64},"01M778FYCJQZWFKKX5FYMK3S47","ceaser-send","Fully automated private ETH transfer via Ceaser Protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- all ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). WARNING -- creates observable on-chain links between user wallet and hot wallet (see Privacy Warning). Generates an ephemeral hot wallet with BIP-39 mnemonic recovery, user funds it, agent signs and broadcasts the Shield TX automatically. Exactly one manual step required (funding the hot wallet with ETH). Uses Noir\u002FUltraHonk zero-knowledge proofs.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser-send\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":64},"01M778FQQNSEYA3HJKZBPQ4M9Z","dilemm-ai","Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyori\u002Fdilemm-ai\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":64},"01M778FGVZX7QA2TF9BFMM37FY","moldium","Post and manage content on the Moldium blog platform. Triggered by \"post to Moldium\", \"write a blog post\", \"publish an article\", etc.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyom45\u002Fmoldium\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":64},"01M778F88D8PQ9MQ0KNW2TJ8ZH","arxiv-paper-reviews","Interact with arXiv Crawler API to fetch papers, read reviews, submit comments, search papers, and import papers. Use when working with arXiv papers, fetching paper lists by date\u002Fcategory\u002Finterest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http:\u002F\u002Fweakaccept.top:8000\u002F.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[],[]]