Agent Skills › vectorize-io/hindsight › routine-memory

routine-memory

GitHub

指导Agent在定时任务中利用Hindsight记忆保持状态连续性。通过在指令中嵌入recall和retain步骤，实现跨运行读取历史、跳过已处理项并记录变更，避免重复工作。

hindsight-integrations/grok-bot/skills/routine-memory/SKILL.md vectorize-io/hindsight

Trigger Scenarios

创建或编辑定时任务执行定时任务前执行定时任务后

Install

npx skills add vectorize-io/hindsight --skill routine-memory -g -y

More Options

Non-standard path

npx skills add https://github.com/vectorize-io/hindsight/tree/main/hindsight-integrations/grok-bot/skills/routine-memory -g -y

Use without installing

npx skills use vectorize-io/hindsight@routine-memory

指定 Agent (Claude Code)

npx skills add vectorize-io/hindsight --skill routine-memory -a claude-code -g -y

安装 repo 全部 skill

npx skills add vectorize-io/hindsight --all -g -y

预览 repo 内 skill

npx skills add vectorize-io/hindsight --list

SKILL.md

Frontmatter

{
    "name": "routine-memory",
    "description": "Carry state between runs of a scheduled routine using Hindsight memory. Use when creating or editing a routine, to write the recall and retain steps into the routine's own instructions, and at the start and end of every scheduled or event-triggered routine run."
}

Remember between routine runs

A routine runs again and again. Without memory each run starts from zero, repeats work and misses what changed. Read the last run before starting, and record this run before finishing.

When creating or editing a routine

Write the memory steps into the routine's own instructions, so every run carries them even when nobody is in the chat:

First: "Recall the last run of from Hindsight and use it."
Last: "Retain a run note to Hindsight: what this run found, what changed, and what the next run should check first."

Tell the user you added them.

At the start of the run

Call recall on this Bot's bank with the query "last run of ".
Use it: skip what was already handled, pick up what was left open, and compare against what the last run found.

At the end of the run

Call retain on this Bot's bank with a note covering: the routine name, the date, what this run found, what changed since the last run, and what the next run should check first. Retain a note even when nothing changed, so the next run knows when this one looked.
Use the tags source:grok-bot, bot:<bot-name> and routine:<routine name>.
If the run found something other Bots should act on, also retain it to grok-bot::shared (see the bot-handoff skill).