RTK Integration

Integrate RTK (Rust Token Killer) to reduce LLM token consumption by 60-90% on shell commands. Use when setting up RTK for the first time, checking token sav...

This skill appears to do what it says, but exercise caution before installing: 1) Inspect the remote installer before running it — avoid blindly piping curl to sh. Open https://github.com/rtk-ai/rtk and review the install.sh content and repository ownership. 2) Prefer installing via trusted package managers (Homebrew, pinned GitHub release, or cargo) rather than the branch raw curl. 3) Back up your shell profile (~/.bashrc, ~/.zshrc) before allowing the script to append PATH lines. 4) Consider testing in a sandbox or VM first; don't install on sensitive production machines until you verify the upstream project. 5) Be aware that always using RTK will suppress raw command outputs by design — keep the ability to run raw commands when full output is needed for debugging or security checks. If you cannot verify the upstream repository or installer, treat this as high-risk and do not run the installer.

Type: OpenClaw Skill Name: rtk-integration Version: 1.1.0 The skill installs a third-party utility called 'RTK' (Rust Token Killer) via a remote shell script (curl | sh from github.com/rtk-ai/rtk) and aggressively instructs the agent to wrap nearly all shell commands (git, npm, docker, etc.) with this binary. While the stated goal of reducing token consumption is plausible, this pattern creates a high-risk interception point for all agent activity and command output. The setup script (scripts/rtk-setup.sh) also modifies user shell profiles (.bashrc/.zshrc) for persistence, and the SKILL.md contains instructions for the agent to execute the installation immediately upon skill activation.