OpenClaw ClaudeCode Controller

Control Claude Code (cc) via tmux to execute development tasks. Use for: starting CC development sessions, sending development commands, monitoring progress,...

This skill appears to do what it says, but it contains several risky or under-documented actions. Before installing or running it: - Do not blindly run curl | sh; inspect the remote install script or prefer npm install from a trusted package. - Avoid using --dangerously-skip-permissions and automated 'y' confirmations unless you fully trust the commands Claude will run. These flags can cause destructive or network-exfiltrating actions to proceed without human review. - The SKILL.md references ANTHROPIC_API_KEY and 'claude /login' but the registry metadata doesn't declare required env vars; ensure you provide and protect the correct API credentials and never paste secrets into commands or public logs. - Creating system users and setting passwords via chpasswd is a privileged action; run these steps in a controlled environment (VM or container), not on production hosts. - If you plan to allow autonomous invocation, restrict it until you confirm the install source and remove the auto-confirm behaviors. If you want a lower-risk setup, ask the author for: a trustworthy source/release for Claude Code, explicit required environment variables, safer defaults (no --dangerously flags), and a mode that requires manual confirmation for privileged operations.

Type: OpenClaw Skill Name: openclaw-claudecode Version: 1.1.0 The skill automates Claude Code via tmux, requiring high-privilege actions like package installation (apt/dnf), user creation (useradd), and the use of the '--dangerously-skip-permissions' flag which bypasses all safety confirmations within the Claude Code CLI. While these actions align with the stated goal of automated development, the combination of root-level setup and unconstrained sub-agent execution presents a significant security risk. (File: SKILL.md)