agentleFS
Sign inStart free
clovericcloveric/tarocub/skills/tarocub-service-ops/SKILL.md

tarocub-service-ops

Skill20 starsChanged 6 months agoMITView on GitHub

Operate the TaroCub Lark bot fleet — restart, status, stop, start, logs, doctor — via its service manager. Use when asked to restart the fleet/bots, check whether the service is running or healthy, stop or start the bots, view bot logs, or diagnose the Lark service. Triggers: 重启车队 / 重启bot / restart the fleet, 服务状态 / 健康 / service status, 看日志 / logs, doctor / 诊断 / 排查.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. cloveric/cc-telegram-bridge★ 20100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Add --force to also restart busy instances — this interrupts their in-flight turn.

    line 17
  2. Very specific:

    If you only need to confirm a bot is alive, lark service status (current instance) or checking the process is enough — don't restart unless …

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

TaroCub service ops (Lark fleet)

Manage the TaroCub Lark bot fleet through its own service manager. The commands take an absolute path (via ~), so they run from any directory.

Restart the fleet (most common)

node ~/projects/cc-telegram-bridge/dist/src/index.js lark service restart --all
  • Restarts every configured Lark instance. Idle bots restart immediately; the current instance (the one whose bot is running this command) auto-defers its own restart until its turn queue is idle — it can't kill itself mid-turn; a busy instance is skipped (not interrupted).
  • Add --force to also restart busy instances — this interrupts their in-flight turn. Use it only when you mean to (the current instance is still deferred, never force-killed).
  • Do NOT hand-roll a per-instance restart loop (stopping/starting each bot by hand). Always use the manager command above.

Other service commands

node ~/projects/cc-telegram-bridge/dist/src/index.js lark service status              # status of the current instance
node ~/projects/cc-telegram-bridge/dist/src/index.js lark service stop  [--all] [--force]
node ~/projects/cc-telegram-bridge/dist/src/index.js lark service start [--all]
node ~/projects/cc-telegram-bridge/dist/src/index.js lark service logs                # recent service logs
node ~/projects/cc-telegram-bridge/dist/src/index.js lark service doctor              # diagnose config / connectivity

Notes

  • A full TaroCub release ends with restart --all (step 3 of the release ritual: commit → GitHub Release → restart & verify). This is that command.
  • The fleet is the configured Lark instances (e.g. ccfcc1/2/3, ccfgg1/2). One bot per instance, one instance per process; state lives under ~/.cctb/<instance>/.
  • If you only need to confirm a bot is alive, lark service status (current instance) or checking the process is enough — don't restart unless asked.

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.

Check your setup, free