How do I install the Cloud Ready skill?

Run npx skillmds add majiayu000/cloud-ready in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Cloud Ready safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cloud Ready?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cloud Ready free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cloud Ready?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cloud Ready by majiayu000 — Agent Skill

Name: Cloud Ready
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

☁️ Cloud Ready (Sovereign Deploy)

This skill forces the project into a professional, deployable state compatible with Hetzner VPS and Coolify.

🎯 Objective

Transform a "Local" project into a "Production" engine.

Strict Topology: Enforces src/, ops/, assets/, docs/.
Eco Mode: Generates docker-compose.yml with strict RAM/CPU limits to prevent OOM kills on cheap VPS.
Deployment Guide: Adds docs/COOLIFY_DEPLOY.md.

🛠️ Usage

Trigger this skill when the user wants to "deploy", "go to cloud", or "standardize" the project.

# Verify structure
python -c "import os; print('✅ Ready' if os.path.exists('src') else '❌ Missing src/')"

📜 The "Golden Standard" (The Truths)

Code lives in src/: No exceptions. apps/ goes inside src/.
Resources live in assets/: Not rsc/.
Infrastructure lives in ops/: Firewall, Audits, Backups.
Data Persistence: Only /app/data inside Docker.
Limits are Mandatory: Every service MUST have deploy.resources.limits.

🔒 The Application of "Proof" (Verification Protocol)

Before considering a module "Cloud Ready", it must be Inhaled (Verified).

Create Temporary Provers: Generate prove_module.py scripts at root.
Check Importability: from src.module import App.
Check Integrity: hasattr(App, 'app') or hasattr(Bot, 'run').
Run Tests: Fix sys.path in runners (run_tests.py) to include src/.

🧹 The "Sanitization" (Exhale Protocol)

We never ship the crowbar with the crate.

Delete Provers: del prove_*.py run_tests.py.
Ignore Tests: Add tests/ and */tests/ to .dockerignore.
Sanitize Git: Add prove_*.py and *.tmp to .gitignore.

Rule: Production Containers contain ONLY what is needed to run. No tests, no audit tools.

📦 Output Artifacts

docker-compose.yml (Optimized)
Dockerfile (Python Slim with source mapping)
docs/COOLIFY_DEPLOY.md
docs/SWAP_GUIDE.md

---name: cloud-readydescription: Standardizes project for Cloud Sovereignty (Coolify + VPS) with Eco Mode resource limits and Professional Folder Hierarchy.--- # ☁️ Cloud Ready (Sovereign Deploy) This skill forces the project into a professional, deployable state compatible with **Hetzner VPS** and **Coolify**. ## 🎯 Objective Transform a "Local" project into a "Production" engine. 1. **Strict Topology**: Enforces `src/`, `ops/`, `assets/`, `docs/`. 2. **Eco Mode**: Generates `docker-compose.yml` with strict RAM/CPU limits to prevent OOM kills on cheap VPS. 3. **Deployment Guide**: Adds `docs/COOLIFY_DEPLOY.md`. ## 🛠️ Usage Trigger this skill when the user wants to "deploy", "go to cloud", or "standardize" the project. ```bash # Verify structure python -c "import os; print('✅ Ready' if os.path.exists('src') else '❌ Missing src/')" ``` ## 📜 The "Golden Standard" (The Truths) 1. **Code lives in `src/`**: No exceptions. `apps/` goes inside `src/`. 2. **Resources live in `assets/`**: Not `rsc/`. 3. **Infrastructure lives in `ops/`**: Firewall, Audits, Backups. 4. **Data Persistence**: Only `/app/data` inside Docker. 5. **Limits are Mandatory**: Every service MUST have `deploy.resources.limits`. ## 🔒 The Application of "Proof" (Verification Protocol) Before considering a module "Cloud Ready", it must be **Inhaled** (Verified). 1. **Create Temporary Provers**: Generate `prove_module.py` scripts at root. 2. **Check Importability**: `from src.module import App`. 3. **Check Integrity**: `hasattr(App, 'app')` or `hasattr(Bot, 'run')`. 4. **Run Tests**: Fix `sys.path` in runners (`run_tests.py`) to include `src/`. ## 🧹 The "Sanitization" (Exhale Protocol) We **never** ship the crowbar with the crate. 1. **Delete Provers**: `del prove_*.py run_tests.py`. 2. **Ignore Tests**: Add `tests/` and `*/tests/` to `.dockerignore`. 3. **Sanitize Git**: Add `prove_*.py` and `*.tmp` to `.gitignore`. > **Rule**: Production Containers contain ONLY what is needed to run. No tests, no audit tools. ## 📦 Output Artifacts - `docker-compose.yml` (Optimized) - `Dockerfile` (Python Slim with source mapping) - `docs/COOLIFY_DEPLOY.md` - `docs/SWAP_GUIDE.md`

Frequently asked questions