菜单
Memory history and change tracking — view evolution of memories over time, audit modifications, and track knowledge changes. This skill should be used when the user asks to see memory changes, audit modifications, or track how information evolved.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Agents-Store/claude-plugins --skill history-tracking命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
This skill should be used when the user reports a problem with macstack-dev or the MACSTACK standard — "this skill did the wrong thing", "the schema is missing a field", "the passport for X is wrong", "send macstack feedback", "improve the schema based on my edit", "fix the macstack plugin" — and the fix must land in the right source (plugin, schema repo, or registry repo).
This skill should be used when the user asks to "set up Infisical for this project", "create .infisical.json", "pull the env keys", "wire the env", "sync secrets", or scaffold-project reaches the env step. Creates .infisical.json, pulls .env.prod/.env.dev, ensures every key from macstack.json resources.accesses exists, and installs the mandatory secrets scripts and commands.
This skill should be used when the user asks to "scaffold the project from macstack.json", "create the project working files", "generate project files from the spec", "build the project from macstack.json", or after a macstack.json is validated and the working tree must be built. Creates project files strictly in the prototype → stack plugins → dev plugins order.
基于 SOC 职业分类
正在显示 SKILL.md
| name | history-tracking |
| description | Memory history and change tracking — view evolution of memories over time, audit modifications, and track knowledge changes. This skill should be used when the user asks to see memory changes, audit modifications, or track how information evolved. |
Track how memories evolve over time — view changes, audit modifications, and investigate knowledge evolution.
| Tool | Purpose | Required Params |
|---|---|---|
| get_memory_history | View change history | memory_id |
| get_memory | Get current state | memory_id |
Tool: get_memory_history
get_memory_history({ memory_id: "abc-123" })
Returns a timeline of all changes made to the memory, including timestamps and old/new values.
1. get_memory(memory_id) -> show current state
2. get_memory_history(memory_id) -> show all changes
3. Present as timeline: date, action, old value -> new value
1. update_memory(memory_id, new_data)
2. get_memory_history(memory_id) -> confirm change recorded
3. Show before/after comparison
1. get_memory(memory_id) -> see current (unexpected) content
2. get_memory_history(memory_id) -> find when it changed
3. Identify the problematic update
4. update_memory(memory_id, correct_data) -> fix if needed
1. get_all_memories(user_id) -> list all memories
2. For key memories: get_memory_history(memory_id)
3. Report on frequently changed memories
4. Flag memories with many revisions for review
1. get_memory_history(memory_id) -> find previous correct value
2. update_memory(memory_id, previous_value) -> restore
3. get_memory(memory_id) -> verify restoration