Prompts & use cases
Eleven Hermes workflows: routing, inbox, leads, demos, posts, research, a morning brief, price watches, a vault, cheaper model routing, and coding jobs. Swap the bracketed parts for your own setup.
11 paste-ready prompts
Hermes AgentGeneral purposeMornings start with scattered tabs just to answer what is happening today. Hermes runs before you are up, pulls the calendar, checks the weather, scans your news sources, and drops a short brief into Telegram so the first coffee comes with context.
Save this as a skill named morning-briefing. Run every day at [6:45] [TIMEZONE] and send one Telegram message.
Daily cron · calendar, weather, RSS, Telegram
Read the promptHermes AgentSpecific purposePrices and plan tables change when you are not looking. Hermes fetches the pages you care about on a schedule, compares them to the last snapshot, and messages you only when a tracked field actually changed.
Save this as a skill named price-watch. Run every [12] hours.
Every 12 or 24 hours · fetch + Telegram
Read the promptHermes AgentSpecific purposeSaved links do not become a knowledge base. On a schedule, Hermes takes the next question from a topic list, reads a handful of sources, and writes a linked markdown note into a vault you can open in Obsidian or any folder. You review the newest notes once a week, starting with the synthesis note.
Save this as a skill named vault-researcher. Run every day at [8:00] [TIMEZONE]. When you finish, send one Telegram line: topic name and how many sources you used.
Daily cron · web + markdown vault
Read the promptHermes AgentSpecific purposeOne premium model on every Hermes turn gets expensive fast. This workflow checks that cheap jobs stay on cheaper models and that only the hard jobs use a paid one, with a hard monthly cap so a loop cannot run all night.
Read my Hermes model config at [CONFIG PATH, e.g. /opt/data/config.yaml]. Do not change it until I say yes.
On demand, then weekly · model config
Read the promptHermes AgentAny taskSmall coding tasks still land on you. You send Hermes the task, the folder, and the file name. It runs Codex CLI on the machine where Hermes already lives, checks the result, commits, and reports back on Telegram. You stay in chat.
When I send a coding job, run it through Codex CLI in [REPO PATH]. Do not start until the message has all three: the task, the folder inside the repo, and the output filename.
On demand · Codex CLI + Telegram
Read the promptShowing 7–11 of 11
Open a prompt for the full message, then replace the bracketed names, repos, and times before you send it.
