Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
deploy-docker-auto
v1.0.0用于在需要将 TPAIP 项目新版本自动化部署到 Linux 服务器时使用。例如：完成功能开发并合并到主分支后；需要将修复的补丁快速推送到生产环境时；或定期执行 CI/CD 流水线中的部署环节时。
⭐ 0· 0·0 current·0 all-time
by@lky115
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (automatic Docker deployment for the TPAIP project) align with the instructions: building images, pushing to a registry, SSHing to a remote server, pulling and running containers, and performing health checks are expected for this purpose.
Instruction Scope
SKILL.md explicitly instructs the agent to ask for and use sensitive inputs (project path, Dockerfile path, registry address, image tag, SSH connection info including key path, server deploy directory, .env path). Those are appropriate for deployment but are sensitive; the instructions also assume the agent (or operator) will run local shell commands (docker build/push, curl) and SSH to the server. The skill does not attempt to access unrelated system paths or undeclared external endpoints.
Install Mechanism
Instruction-only skill with no install spec and no code to drop to disk. This is the lowest install risk — the skill will rely on existing docker/ssh tooling on the host.
Credentials
The skill does not declare required environment variables but reasonably requires credentials/inputs at runtime (SSH key, registry credentials, .env file). These are proportionate to a deploy workflow, but they are sensitive and the skill does not prescribe safe handling (e.g., using short-lived tokens or least-privilege deploy user).
Persistence & Privilege
Skill is not always-enabled and does not request persistent system privileges. Autonomous invocation is allowed by platform default (not a separate concern here) and the skill does not claim to modify other skills or global agent settings.
Assessment
This skill is coherent for its stated purpose, but it will need sensitive inputs to operate (SSH private key or credentials, registry login, and .env files). Before using it: (1) only provide a least-privilege deploy user and consider a dedicated deploy key or short-lived token; (2) avoid giving permanent access to your main account keys—use throwaway/rotated keys and rotate them after use; (3) run the process first in a staging environment and verify the exact commands the agent will execute; (4) keep backups and a rollback plan in case the new container fails; (5) if you are uncomfortable letting an agent access private keys directly, perform the SSH and key handling manually following the skill’s steps. If you want higher assurance, ask the skill author to document exactly how credentials are handled or to accept ephemeral tokens instead of raw key paths.Like a lobster shell, security has layers — review code before you run it.
latestvk9749a7gwb3xte4vqxazb6hdes84szsq
License
MIT-0
Free to use, modify, and redistribute. No attribution required.