Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Security agent that inventories installed OpenClaw skills, analyzes them for threats, and syncs results to your Clawned dashboard.
Security agent that inventories installed OpenClaw skills, analyzes them for threats, and syncs results to your Clawned dashboard.
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.
Automatically discovers all installed skills, analyzes them for security threats, and syncs results to your Clawned dashboard.
Configure your API key in openclaw.json: { "skills": { "entries": { "clawned": { "enabled": true, "env": { "CLAWNED_API_KEY": "cg_your_api_key_here", "CLAWNED_SERVER": "https://api.clawned.io" } } } } }
python3 {baseDir}/scripts/agent.py sync
python3 {baseDir}/scripts/agent.py scan --path <skill-directory>
python3 {baseDir}/scripts/agent.py inventory
python3 {baseDir}/scripts/agent.py status
During sync (default operation): Sends only skill metadata: name, owner, slug, version No file contents are uploaded No .env files or secrets are ever read During scan --path (explicit user action only): Reads source files (.md, .py, .js, etc.) from the specified skill directory for analysis .env files are excluded from scanning File contents are sent to the Clawned server for security analysis Local config access: Reads ~/.openclaw/openclaw.json only to locate skill directories (extraDirs paths) No credentials or secrets are read from config files
Schedule every 6 hours via OpenClaw cron: { "jobs": [ { "schedule": "0 */6 * * *", "command": "Run clawned sync to check all installed skills", "description": "Security scan every 6 hours" } ] }
Identity, auth, scanning, governance, audit, and operational guardrails.
Largest current source with strong distribution and engagement signals.