Tonic System Deploy

Software deployment workflow for systems with separate UAT and PROD environments. Use when: planning a bug fix deployment, choosing between Flow 1 (UAT-first...

This appears to be a deployment playbook rather than executable automation, but it mentions sending Telegram notifications and performing deploy/merge operations without listing any required credentials, endpoints, or tools. Before installing or enabling this skill for autonomous use: 1) Confirm whether it is intended as a human-facing checklist only — if so, treat it as documentation and keep autonomous invocation disabled. 2) If you plan to let the agent perform deploys or send Telegram messages, require explicit, minimal credentials (scoped CI/CD service token, Telegram bot token + chat id, deploy keys) and restrict them to least privilege. 3) Ask the publisher for concrete integration details (what CI/CD, how deploys are executed, where 'records' are stored, rollback commands). 4) Avoid pasting high-privilege secrets into the agent without reviewing and limiting their scope; prefer manual gates for PROD actions. If you cannot obtain those clarifications, do not grant this skill network or credential access and use it only as a manual runbook.

Type: OpenClaw Skill Name: tonic-system-deploy Version: 1.0.0 The skill bundle describes a complex software deployment workflow, which inherently requires powerful system interactions. Specifically, the `SKILL.md` file includes explicit shell commands for rollback procedures (`docker compose down && git checkout <prev_tag> && docker compose up`). While these commands are plausible for the stated purpose, they represent a significant shell injection vulnerability if the `<prev_tag>` input is not properly sanitized, potentially leading to Remote Code Execution (RCE). Additionally, the skill instructs the AI agent to perform 'AI analysis' and 'AI assist' in fixing bugs, implying powerful code generation/modification capabilities which, without strict sandboxing, could be risky. There is no evidence of intentional malicious behavior like data exfiltration or backdoor installation, but the presence of high-risk, potentially vulnerable commands makes it suspicious.