agentleFS
Mohamed-Sherif-AliMohamed-Sherif-Ali/botter/.claude/skills/deploy-to-cloud/SKILL.md

deploy-to-cloud

Skill0 starsChanged 5 months agoMITView on GitHub

Put a finished bot live 24/7 on a managed cloud host the user owns and pays for, with its secret kept in the host's secret store, never in the code. Use this when the user runs /deploy-to-cloud, or asks to host a bot online, run it 24/7, deploy it to the cloud, or take it off their own PC. Unlike deploy-to-host, which writes a guide for someone else's server, this deploys the user's own bot to a managed platform for them.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If no bot was named above, look in the bots/ folder, list the bots by name, and ask which one to deploy.

    line 24
  2. Distinctive:

    Make sure the bot runs as a long-running worker, not a web server: it just runs its start script and stays connected, with no open port.

    line 34
  3. Distinctive:

    Create the project on the host from inside the bot's folder and deploy the code to it (for Railway, link a new project and run its deploy …

    line 41
  4. Distinctive:

    Keep it minimal and beginner-friendly.

    line 61

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

deploy-to-cloud

Get a bot the user already made running around the clock on a managed cloud host that the user owns, so it no longer depends on their PC being on. The host is theirs and they pay for it; Botter runs no servers. Read the bot-style base and the bot's platform style skill first so you know its layout and its secret.

Talk to the user as if they are not a programmer. Use plain language. Be honest that the host is the user's own paid account, and that running a bot there costs money (usually a small monthly or usage-based amount); say so before they commit. Never enter the user's payment details or passwords; have the user sign in to their own account themselves.

The bot the user wants to put online:

$ARGUMENTS

Work through these in order.

  1. If no bot was named above, look in the bots/ folder, list the bots by name, and ask which one to deploy. Wait. Make sure it runs locally first: its dependencies install and it starts cleanly. If it does not, stop and point the user to check-bot. Only deploy a working bot.
  2. Pick the host. Default to Railway: it has the simplest path for a beginner, a command-line tool that deploys the local folder directly, a built-in place to store secrets, and no need for a web server or Docker. If the user wants a free always-on option, note Fly.io (free small VMs, but it needs a Dockerfile and is more technical). If they want a fixed low monthly cost, note Render as a background worker (its free tier sleeps, so a bot needs the paid tier). Confirm the host first.
  3. Make sure the bot runs as a long-running worker, not a web server: it just runs its start script and stays connected, with no open port. Confirm the start script is correct for the host.
  4. Get the host's command-line tool ready and have the user sign in to their own account with it (for Railway, install the Railway CLI and run its login, which opens the browser for them to approve). The account and any payment details are the user's; do not enter them.
  5. Create the project on the host from inside the bot's folder and deploy the code to it (for Railway, link a new project and run its deploy command, which uploads the current folder). Do not send the .env file or node_modules; the host installs dependencies itself, and the secret is set in the next step.
  6. Set the secret safely. The secret never goes into the deployed code or any committed file. Put it in the host's own environment-variable store instead (for Railway, set it as a variable on the service). Set every value the bot reads from .env: the token, and for Telegram the chat ID. The host injects these at runtime, exactly as .env does locally.
  7. Confirm it is live. Read the host's logs and check the bot starts cleanly and connects, the same healthy startup test-bot looks for. Tell the user the bot now runs 24/7 on the host, independently of their PC.
  8. Finish in plain language with no emoji: confirm the bot is live, say where to see its logs and restart it on the host, restate that the secret lives only in the host's secret store, and give a realistic note on cost so there are no billing surprises. If the bot saves data to a file, warn that a plain redeploy can wipe that file, and that keeping data across deploys needs the host's persistent storage; flag this rather than guessing the setup.

Keep it minimal and beginner-friendly. Never enter the user's payment details, and never put the secret anywhere but the host's secret store.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.