Claude Code Wingman

Things to check before installing or running this skill: - Review the code yourself (especially auto-approver.sh, interactive-approver.sh, master-monitor.sh, and lib/send-notification.sh). The auto-approver will automatically approve 'Do you want' prompts and folder trust prompts, which may allow Claude Code to execute tools, write files, or run shell commands without further human confirmation. - Confirm where notifications go and who controls the webhook: lib/send-notification.sh will use CLAWDBOT_WEBHOOK_TOKEN, CLAWDBOT_PHONE or ~/.clawdbot/clawdbot.json and by default posts to http://127.0.0.1:18789/hooks/agent unless overridden. Make sure the webhook URL/token are under your control and not pointed at a remote endpoint you don't trust. - Be aware of undeclared requirements: scripts use jq, curl and expect access to ~/.clawdbot/clawdbot.json and /tmp state files. The registry metadata lists only 'claude' and 'tmux' — verify you have or want to grant these additional accesses. - Prefer interactive mode: avoid running with --auto unless you fully trust the environment and understand that prompts (including ones that could allow running arbitrary tool calls) will be auto-approved. - If you want to test safely: run the scripts in an isolated VM/container or sandbox, do not point webhook env vars to production endpoints, and do not run master-monitor as a daemon until you verify behavior. - Fix/inspect minor issues: some scripts reference variables that are not set (e.g., lib/approval-respond.sh echoes $NORMALIZED which is never defined) — expect small bugs. Overall: this skill is plausible for its stated goal, but it requires careful review and explicit configuration of webhook tokens and approval modes before use; treat it as untrusted code until you inspect and control its configuration and runtime environment.