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

deploy-to-host

Skill0 starsChanged 5 months agoMITView on GitHub

Produce a clear deploy guide for putting a bot on an always-on computer (a server) so it runs around the clock. Use this when the user runs /deploy-to-host, or asks how to deploy, host, or run a bot on a server or VPS, or to make it run 24/7. Writes step-by-step instructions tailored to the bot, meant to be handed to whoever runs the server.

  • 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 (older bots may sit at the project root.

    line 24
  2. Distinctive:

    Read the bot so the guide is accurate for it: its platform (Discord or Telegram) and shape (poster or full bot), what secret it needs, what …

    line 27
  3. Distinctive:

    Write the guide as a "Deploying to an always-on host" section in the bot's README.md, so it travels inside the package-bot zip.

    line 32
  4. Distinctive:

    Keep your explanation to the user plain and beginner-friendly.

    line 58

≈ “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-host

Produce a clear set of deploy instructions for running a bot on an always-on computer (a server), so it keeps working even when the user's own PC is off. The instructions are meant to be handed to whoever runs that server (often the server's owner), together with the zip that package-bot makes. The bot may be a Discord or a Telegram bot; read the matching style skill (discord-style for Discord, telegram-style for Telegram) so you know the bot's layout, shape, and whether it saves data.

Talk to the user as if they are not a programmer; explain plainly what you produced and why. The deploy guide itself is for the person running the server, who knows their way around one, so it can use normal server steps and commands.

The bot the user wants to deploy:

$ARGUMENTS

Work through these in order.

  1. If no bot was named above, look in the bots/ folder (older bots may sit at the project root; check there too), list the bots by name, and ask which one to deploy. Wait.
  2. Read the bot so the guide is accurate for it: its platform (Discord or Telegram) and shape (poster or full bot), what secret it needs, what it must reach (for Discord, the target channel and, for a full bot, which intents; for Telegram, the target chat and whether privacy mode matters), and whether it saves data to a file.
  3. Write the guide as a "Deploying to an always-on host" section in the bot's README.md, so it travels inside the package-bot zip. The guide should walk the server's owner through, on a Linux server they reach over SSH:
    • getting the bot's files onto the server (unzip the package, or clone it),
    • installing Node.js if it is not there, then running npm install,
    • creating the .env from .env.example and filling in its values: the secret (a bot token or a webhook URL) and, for Telegram, the target chat ID,
    • the one-time platform setup, the same as anywhere else: for a Discord full bot, the bot must be invited to the server and any privileged intent enabled; for a Telegram bot, the bot must be added to its target chat (an admin if it is a channel), and if it must read all group messages, privacy mode must be off in BotFather,
    • starting it and keeping it running with PM2: start it, save the list, and use PM2's own start-on-boot setup (pm2 startup), which works properly on Linux, so it survives reboots and restarts itself on a crash,
    • a note that the bot uses an explicit timezone (Africa/Cairo) in its schedule, so the server's own clock setting does not change when it fires,
    • and, if the bot saves data, that its data file lives in the bot's folder and should be kept in place across restarts and updates.
  4. Show the user the guide you wrote, and explain plainly: package the bot with package-bot, then send the owner the zip (the guide is now inside the README), and send the secret separately and safely, never inside the zip.
  5. Finish in plain language with no emoji: confirm the guide is in the bot's README, and remind the user that if they ever get their own always-on computer, the same guide works for them.

Keep your explanation to the user plain and beginner-friendly. Never put a real secret into the guide or the package.

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.