Keep the AutoRAG index fresh and watch for duplicate files on their own, using Hermes cron. Use when the user wants indexing to run automatically ("re-index every night", "only while charging", "only between 10pm and 7am") or wants to be told when duplicate documents appear ("check my Documents for duplicates every morning"), or wants to list or remove such schedules. Not for one-off searches (use the search skill), not for first-time setup (use the setup skill), and not for reacting to a file the moment it appears (use the automate skill).
95%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Two kinds of Hermes cron job, both no-agent: the script is the job, no model runs, and a script that prints nothing delivers nothing. They cost no tokens and say nothing unless there is something to say.
| Kind | What it does | Speaks when |
|---|---|---|
index | Runs autorag watch --once so the index stays current. Power, time window and weekday rules are AutoRAG's own. | A refresh fails. A closed window or a battery skip is recorded, not delivered. |
duplicates | Runs autorag duplicates --json and compares with what it reported last time. | A duplicate group is new or has grown. Never twice for the same group. |
The scan only reads files. It never moves, edits or deletes anything, and the message says so.
Ask for what is missing, then run the helper. Do not guess a schedule the user did not give; offer the default.
# keep the index fresh, only while plugged in and overnight
python3 "${HERMES_SKILL_DIR}/scripts/autorag_schedule.py" index \
--id nightly --schedule "every 1h" --power ac --window 22:00-07:00
# tell me about new duplicates every morning at 9
python3 "${HERMES_SKILL_DIR}/scripts/autorag_schedule.py" duplicates \
--id docs --schedule "0 9 * * *" --path ~/Documents --deliver telegram--id is letters, digits, _ and -. The cron job is named autorag-index-<id> or autorag-duplicates-<id>.--schedule is Hermes' own grammar: 30m, every 2h, or a cron expression. Defaults: every 1h (index) and
0 9 * * * (duplicates). For the index job it is how often the gate is checked; --window, --days and
--power decide whether a check actually indexes.--window HH:MM-HH:MM is local time and repeatable; 22:00-07:00 wraps midnight. --days mon,tue,....--deliver is where a message goes: local (default, visible in hermes cron list and the job's output),
telegram, discord, and so on. Pick it from what the user says ("message me" is their messaging app).--path for duplicates is a folder to scan (repeatable). Without it the configured AutoRAG search paths are scanned.--id updates the job instead of adding a second one.The helper prints JSON. If it exits non-zero, show the user its error and stop; do not retry with guessed flags.
If it says no AutoRAG CLI was found, run the plugin's search pane once (it installs a resident copy) or pass
--autorag-cli npx -y -p @autorag/librarian@2.13.12 autorag.
python3 "${HERMES_SKILL_DIR}/scripts/autorag_schedule.py" list
python3 "${HERMES_SKILL_DIR}/scripts/autorag_schedule.py" remove --kind index --id nightlylist shows each job, its schedule and the last result the script recorded (refreshed, skipped with the reason,
failed, or scanned with the group counts). remove deletes the cron job, the script and its state, and leaves other
jobs alone. To run one now: hermes cron run <job id>, then hermes cron tick.
--power ac pauses indexing on battery. If the power state cannot be read, AutoRAG lets the run
proceed rather than stopping indexing silently.hermes cron tick) is running. hermes cron status shows whether one is.| Symptom | Check |
|---|---|
| Nothing ever happens | hermes cron status: no gateway serving the profile means no job fires. |
| Index job never indexes | list: last.outcome is skipped with battery, outside-window or outside-day. Loosen the rule. |
| A message says "AutoRAG index refresh failed" | Its text is the CLI's own error. A first refresh downloads models and can be slow; the job gives up after 55 minutes. |
| A message says "AutoRAG duplicate scan failed" | The scan's own error. The previous report is remembered, so the next good run does not repeat it. |
| Same duplicates reported again | They changed (a group gained a file, or went away and returned). Unchanged groups are never repeated. |
Marker-Inc-Korea/AutoRAG
399c591
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.