keep-running
Skill0 starsChanged 5 months agoMITView on GitHub
Keep a finished bot running on this Windows PC, so it survives closing the terminal, keeps going after a crash, and starts again when the computer reboots. Use this when the user runs /keep-running, or asks to keep a bot running, run it in the background, make it always on, restart on crash, or start on boot. Sets it up with PM2 and a Windows logon task.
- Reads credentials
- Installs packages
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- bot-styleSkill
- check-botSkill
- deploy-to-cloudSkill
- deploy-to-hostSkill
- discord-styleSkill
- edit-botSkill
- list-botsSkill
- make-botSkill
- package-botSkill
- remove-botSkill
- rotate-secretSkill
- security-checkSkill
- skillsSkill
- telegram-styleSkill
- test-botSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Read the bot-style skill first so you know the bot's layout.
- Distinctive: line 22
If no bot was named above, look in the bots/ folder (older bots may sit at the project root.
- Distinctive: line 25
Make sure the bot is ready: its dependencies are installed and its .env has the real secret in it.
- Distinctive: line 29
Make sure PM2 is available.
- Very specific: line 32
Start the bot under PM2 from inside the bot's folder, using its existing start script, and give the PM2 process the bot's name so it is …
- Distinctive: line 42
Check it worked: confirm PM2 shows the bot as online.
- Distinctive: line 48
If the bot must run even when the PC is off, point to the always-on host route as the next step.
≈ “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.
Files
keep-running
Set up a bot the user already made so it runs in the background on this Windows PC: it keeps going after the terminal is closed, restarts itself if it crashes, and comes back when the PC reboots. Read the bot-style skill first so you know the bot's layout.
Talk to the user as if they are not a programmer. Use plain language. Be honest about the one limit: this only runs while the PC is on and awake. For a bot that must fire on a schedule even when the PC is off, the user needs an always-on host instead, which is a separate step.
The bot the user wants to keep running:
$ARGUMENTS
Work through these in order.
- 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 keep running. Wait.
- Make sure the bot is ready: its dependencies are installed and its .env has the real secret in it. If the secret is still missing, stop and tell the user to add it first. This skill keeps an existing, working bot running; it does not set one up from scratch (make-bot does that).
- Make sure PM2 is available. PM2 is a small tool that keeps Node programs running. If it is not installed, install it once for the whole machine with npm install -g pm2.
- Start the bot under PM2 from inside the bot's folder, using its existing start script, and give
the PM2 process the bot's name so it is easy to find later (for example,
pm2 start npm --name
<bot>-- start). PM2 restarts the bot automatically if it ever crashes. Then save the PM2 process list with pm2 save so it can be brought back after a reboot. - Make it start again when the PC restarts. On Windows, PM2's own boot setup is unreliable, so use Windows Task Scheduler instead: create a task that runs when the user logs in and brings the saved bots back with pm2 resurrect. Create this task for the user rather than asking them to click through Task Scheduler by hand, and keep it scoped to the current user logging in.
- Check it worked: confirm PM2 shows the bot as online. Then tell the user, in plain language, the
few commands they will actually use: see what is running (pm2 list), watch a bot's output
(pm2 logs
<name>), restart it (pm2 restart<name>), and stop and remove it (pm2 delete<name>). - Finish in plain language with no emoji: confirm the bot is now running in the background and will come back on login, and restate the one limit, that it only runs while this PC is on and awake. If the bot must run even when the PC is off, point to the always-on host route as the next step.
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
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.

