jimmy
2.1 KiB
2.1 KiB
20260916-002447 session 20260915_111917_cc2921ae
user: What should we name him?
assistant: Name suggestion: watchdog
Why “watchdog”?
- It conveys the idea of a vigilant guardian that scans nightly for broken workflows, missing instructions, or polluted context.
- The term is short, memorable, and aligns well with existing Hermes terminology (
watchdog→ daily monitor).
You can create the skill as ~/.hermes/profiles/jimmy/skills/watchdog.md if you want.
20260916-003521 session 20260915_111917_cc2921ae
user: Perfect. Let’s talk about how we use him.
assistant: ### How to use watchdog
| Step | What it does | How to set it up |
|---|---|---|
| 1 | Create the skill – a script that pulls all chat logs and runs an LLM prompt. | hermes skill_manage (see example code below). |
| 2 | Schedule it nightly – either via cronjob_manage or hermes --profile watchdog cron. |
hermes cronjob_manage action=connect cron=0 3 * * * --profile watchdog |
| 3 | Collect log data – the skill reads every chat_history.log under profiles/*/. |
Internally done by a find command. |
| 4 | Analyze – the skill sends the combined text to your default model with a prompt that looks for instruction violations, context pollution, and failures. | LLM prompt defined in the script. |
| 5 | Output – a JSON file reports/watchdog-YYYY-MM-DD.json that lists • time • user • profile • issue • recommendation |
hermes --profile boss chat -q or expose the file to a Telegram channel via hermes --profile telegram chat -q "Watchdog report for $(date +%F)". |
| 6 | Act on the report – review the file, then use hermes --profile <p> chat -q to give the agent corrective instructions or patch context. |
Example: hermes --profile leonard chat -q "Please avoid using the old avatar.png link in the footer." |
| 7 | Iterate – the next run will automatically refresh the analysis, picking up any new or fixed issues. | No manual trigger needed. |