القائمة
Snapshot of the BTD6 data pipeline — what the bot knows, what it doesn't, and what's broken. Useful after a live testing session where you hit wrong answers.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Turn a spoken idea or a diagnosed fix into a structured Claude Code work order and dispatch it to a Claude Code **Routine** (`/fire` API), closing the "nearly autonomous from anywhere" loop. Hermes decides and dispatches **read-only** — it sends text; Claude Code does the mutation under CI gates.
One consolidated start-of-day digest — repo health, open PRs, recent CI, what the autonomous routines did overnight, and any decisions waiting on the owner — so the day starts from a single message instead of several separate pings.
Scan recent PRs for Codex/bot review flags, apply the "real bug" bar, and **open a GitHub issue** for each verified-real defect — so a real bug Codex caught never sits unactioned, and a false positive never burns a routine fire. **Issue-only: no merge, no dispatch authority.**
Turn a recurring Hermes workflow into a new, well-formed, version-controlled SuperBot skill — design it, write it in the repo's skill format, regenerate the installable artifact, and open a docs-only PR so it is reviewed and committed (not left as a VPS-only scratch file).
Surface **one** active idea from the backlog each day with the thinking already started — a short summary plus **pros, cons/risks, and options/expansions** — so the owner can mull it over during the day and report a decision back at the end of it.
Surface all unanswered Q- blocks from the maintainer question router, grouped by area and urgency. Useful for thinking through decisions without needing to navigate the router doc directly.
| name | superbot-btd6-status |
| description | Snapshot of the BTD6 data pipeline — what the bot knows, what it doesn't, and what's broken. Useful after a live testing session where you hit wrong answers. |
| version | 1.0.0 |
| author | SuperBot agents |
| license | MIT |
| platforms | ["linux","macos"] |
| metadata | {"hermes":{"tags":["Monitoring","SuperBot","BTD6"]}} |
You are Hermes, working with the SuperBot repository at /home/hermes/repos/superbot. Do not modify any files. Read-only only.
Produce a BTD6 STATUS REPORT. Keep the output under 500 words.
Do the following in order:
Read: /home/hermes/repos/superbot/docs/btd6/btd6-gamedata-decode-status.md Extract:
Read: /home/hermes/repos/superbot/docs/health/bug-book.md Find any open bugs (not marked FIXED) that mention BTD6, round cash, grounding, resolver, or BTD6-related commands. List each: BUG-NNNN — short description — status.
Run: cd /home/hermes/repos/superbot && git log --oneline --all -- disbot/data/btd6/ | head -5 Show the 5 most recent commits that touched the BTD6 data files. This tells you how recently the data was updated.
Run: cd /home/hermes/repos/superbot && git log --oneline --all -- disbot/services/btd6_*.py | head -5 Show the 5 most recent commits that touched BTD6 service files.
Check if the probe script exists: ls /home/hermes/repos/superbot/scripts/btd6_probe.py If it exists, run: cd /home/hermes/repos/superbot && python3 scripts/btd6_probe.py --help (read-only — just check what options exist, do not run a full probe)
Format the output as:
[from step 1 — what's grounded vs. missing, compact table or list]
[from step 2 — or "none open"]
[from steps 3+4 — last 5 commits for data files, last 5 for services]
[from step 5 — available options, or "probe script not found"]
