Free recipes / Scheduled Jobs

A Weekly Review Every Friday

A schedule that looks back over your week every Friday afternoon and sends what got done, what is still open, a goals check and three priorities for next week.

You end most weeks unsure what you actually finished, and you want an honest look back without writing it yourself. Saves about 30 minutes

The recipe

Schedule: run the first line below, save everything from the Role line down as ~/hermes-jobs/weekly-review.txt, then run the second line in your terminal. mkdir -p ~/hermes-jobs/state hermes cron create "every friday 4pm" "$(cat ~/hermes-jobs/weekly-review.txt)" --name weekly-review --deliver [DELIVER_TO] The prompt is copied when the job is created. After editing the file, run hermes cron edit weekly-review --prompt "$(cat ~/hermes-jobs/weekly-review.txt)". Jobs fire only while the gateway is running. Role: You are my weekly review partner: factual, brief, no cheerleading. Context: This is a scheduled job in a fresh session with no memory of earlier chats. Everything you need is in this prompt, and your final reply is delivered to me automatically. The review covers the last 7 days. Steps: 1. Run TZ=[TIME_ZONE] date to get today's date, weekday and time. 2. List the files in [NOTES_FOLDER] changed in the last 7 days and read them. 3. Read [TASKS_FILE]: what was completed, what is still open, what slipped. 4. Use session_search to find what we worked on together this week. Use it only to name topics, not to quote private details. 5. Compare the week with my current goals: [CURRENT_GOALS]. Output format: plain text under 250 words: - Done this week: up to 5 bullets - Still open: up to 5, oldest first, with how long each has been open - Goals: one line per goal, saying on track, behind, or no activity - Next week: 3 suggested priorities, one line each on why - One question for me to think about over the weekend Rules: Read only. Do not edit files, send messages or create jobs. Count something as done only if the notes or task file show it. No praise and no motivational filler. If a source you need cannot be read, start the reply with [CRON_FAILURE] and name it. With no changed notes, no task changes and no sessions this week, there is nothing worth sending. If there is nothing worth sending, reply with exactly [SILENT] and nothing else. Never write [SILENT] in a reply that has content.

Fill in these brackets

`[DELIVER_TO]`	e.g. telegram (the home channel set with /sethome), telegram:<chat_id>, or local to test first
`[TIME_ZONE]`	e.g. Europe/Amsterdam
`[NOTES_FOLDER]`	e.g. ~/notes/daily
`[TASKS_FILE]`	e.g. ~/notes/tasks.md
`[CURRENT_GOALS]`	e.g. finish the course outline, two client proposals, run three times a week

Pro tip

This is one job worth keeping on a strong model, because it has to judge what matters. If you set a cheaper cron.model for routine jobs, pin this one with hermes cron edit weekly-review --model <id> --provider <id>, or use --pin to lock in your current main model. The cron.model_provider key sets the provider for cron.model itself.

Variation

Make it monthly with "30 8 1 * *" (08:30 on the first of each month), widen the window to 30 days, and ask for patterns across the month instead of a task list.

Written for Hermes Agent v0.21.x. Check commands against your version with hermes --version. This site is independent and not affiliated with Nous Research.