Skill

This skill appears to do what it promises (local config patches, spend caps, caching, and an optional external 'rtk' engine for compression). Before installing: - Review the backup: /clawtk setup creates a backup of your OpenClaw config; verify that backup location in ~/.openclaw before accepting changes. - Inspect remote installers: installing the ClawTK Engine falls back to downloading and executing an installer script from GitHub (rtk). The installer file is saved locally first (scripts log the tmp path and size) — inspect that file if you want to review what will run. - Understand global effects: rtk init -g --auto-patch may modify global shell/tool hooks to compress CLI output; if you prefer no global changes, install rtk manually and adjust configuration as needed. - Data sent to cloud: license activation and optional sync call api.clawtk.co; SKILL.md states only license validation and spend summaries (timestamp, token count, estimated cost, tool name) are transmitted, not conversation or file contents — still verify network endpoints if you have strict policies. - Recovery: /clawtk restore is provided to revert changes; confirm the backup exists before proceeding. If you accept those trade-offs and trust the upstream rtk project and api.clawtk.co, the skill is coherent and reasonable for its purpose.