Clawwork

This skill largely does what it says (wraps a ClawWork project), but there are important inconsistencies and risks you should consider before installing: - Secrets: The skill expects OPENAI_API_KEY / OPENAI_API_BASE and an E2B_API_KEY stored in ~/.openclaw/workspace/ClawWork/.env, but the registry metadata does not declare these. Do not place high-privilege keys there until you trust the code. Prefer scoped/test keys. - Hardcoded paths: Files use absolute paths under /home/freedom and expect a venv at CLAWWORK_DIR/venv. If your environment differs the code may fail or read unexpected files. Review and adapt paths before running. - Unreviewed imports: The CLI imports agent.live_agent from the ClawWork project directory (not included in these files). That code will run when you execute tasks — inspect the ClawWork project (the referenced GitHub repo) before executing to ensure it doesn't perform unwanted network, filesystem, or credential operations. - Run in isolation first: If you want to try it, run it in a disposable VM or container and use limited-scope API keys. Verify what network endpoints are contacted (OpenRouter/E2B and any other endpoints the ClawWork project contacts). - Metadata fix: Ask the skill author/maintainer to update the registry metadata to declare required env vars (OPENAI_API_KEY, OPENAI_API_BASE, E2B_API_KEY) and to avoid hardcoded user paths. Given the mismatches (undeclared secrets + code that will import external project modules and use them), treat this skill as suspicious until you can review the full ClawWork project and confirm the exact runtime behavior.