xCloud Docker Deploy

Deploy any project to xCloud hosting — auto-detects stack (WordPress, Laravel, PHP, Node.js, Next.js, NestJS, Python, Go, Rust), routes to native or Docker d...

This skill appears coherent and focused on adapting docker-compose and producing GitHub Actions for xCloud. Before you use it: 1) Review any generated GitHub Actions workflow before committing — it will push images to GHCR and optionally call an xCloud webhook; ensure the webhook URL and any secrets are trustworthy. 2) Do not commit real secrets (.env) to the repo; the skill correctly advises generating .env.example and storing secrets in GitHub secrets or xCloud UI. 3) If you make GHCR packages public (required by xCloud), confirm you are comfortable with public images. 4) Verify the optional curl trigger to XCLOUD_DEPLOY_WEBHOOK is only present when you add that secret. 5) Because the agent will read your repository files to detect stack and extract env var names, ensure you are comfortable granting the agent access to the repo contents and review outputs before pushing the changes. Overall the files and instructions are consistent with the described deployment workflow.

Type: OpenClaw Skill Name: xcloud-docker-deploy Version: 1.2.1 The skill's primary function is to guide an AI agent in transforming Docker configurations and generating CI/CD workflows for deployment. This involves instructing the agent to read project files, and to generate/modify configuration files (e.g., `docker-compose.yml`, `.github/workflows/docker-build.yml`, `.env.example`). While these file system write operations are central to the skill's stated purpose, the `SECURITY.md` file explicitly states 'No file system modifications' and 'No subprocess calls', which directly contradicts the instructions in `SKILL.md` and other reference files. This misrepresentation of the skill's capabilities in its security documentation (SECURITY.md) is a significant vulnerability, making the skill's self-declared safety unreliable. Additionally, the 'Audited by' date in `SECURITY.md` is in the future (2026-03-03), which is a minor but suspicious metadata anomaly.