根据代理工作记录和词元数量,整理每项已完成成果及返工的费用,区分估算金额与实测支出,并生成附有依据的 HTML、JSON 和 CSV 报告。
- 核对每周支出与完成成果
- 比较每项已完成成果的费用
- 调查重复工作与返工费用
为 claude-mem 数据库设置定期本地快照,查看最近的保存时间、快照数量和错误,也可从已保存的文件恢复数据库。
Set up, check, or restore local claude-mem database snapshots. Use when the user says "set up backups", "back up my memories", "backup status", or "restore my database".
实测评分 未实测
查看安装方法为 claude-mem 数据库设置定期本地快照,并选择保存间隔和保留的文件数量。可以查看最近一次保存时间、快照数量及近期错误。恢复时,从已保存文件列表中选择一个快照;工作进程会切换数据库并重启,同时把恢复前的数据库保存在同一文件夹中。
需要在本机保存 claude-mem 记忆数据副本,或确认备份是否正常运行时,可以使用此技能。发生误操作或故障后,也可以将数据库恢复到较早的快照。
设置时会使用 npx claude-mem。设置文件包含认证信息,因此不会显示文件内容,并会将文件访问权限保持为 0600。如果启用了云同步,恢复后会从快照记录的位置继续同步,也可能取回云端的后续更改。
本介绍由 AI(OpenAI Codex)根据公开的 SKILL.md 撰写。准确的规格请查看下方原文。
AI 根据 SKILL.md 的内容检查了需要注意的操作和使用前提。评分只依据实际运行的结果(实测对比)。
不计入评分。 由 AI(OpenAI Codex)于 2026年10月27日 评估。仅供参考,安装前请同时查看原文。
安装前可以查看交给 AI 代理的指令内容。
The installed worker snapshots ~/.claude-mem/claude-mem.db on a schedule
(VACUUM INTO, consistent while sessions run) and keeps the newest N under
~/.claude-mem/backups/auto/. Each snapshot is one standalone SQLite file.
Snapshots stay on this machine.
Preserve every unrelated setting and keep ~/.claude-mem/settings.json mode
0600. Never print the file's contents: it holds credentials.
Based on $ARGUMENTS:
setup or empty: 1. Check status, then 2. Enable snapshotsrestore: 3. Restorestatus: 1. Check status onlynpx claude-mem backup status
npx claude-mem start and retry.npx claude-mem update brings them once a release
includes them. Do not write the settings in step 2, and never say backups
are on.Ask (or default): interval in hours (default 24, range 1 to 168) and how many snapshots to keep (default 7, range 1 to 100). Then write the settings without echoing anything else in the file:
node - <<'EOF'
const fs = require('fs'), os = require('os'), path = require('path');
const intervalHours = 'PASTE_INTERVAL_HOURS_HERE'; // e.g. '24'
const retainCount = 'PASTE_RETAIN_COUNT_HERE'; // e.g. '7'
const dir = path.join(os.homedir(), '.claude-mem');
const file = path.join(dir, 'settings.json');
fs.mkdirSync(dir, { recursive: true });
const settings = fs.existsSync(file) ? JSON.parse(fs.readFileSync(file, 'utf8')) : {};
const target = settings.env && typeof settings.env === 'object' ? settings.env : settings;
target.CLAUDE_MEM_BACKUP_ENABLED = 'true';
target.CLAUDE_MEM_BACKUP_INTERVAL_HOURS = intervalHours;
target.CLAUDE_MEM_BACKUP_RETAIN_COUNT = retainCount;
fs.writeFileSync(file, JSON.stringify(settings, null, 2) + '\n', { mode: 0o600 });
fs.chmodSync(file, 0o600);
console.log('backups enabled: every ' + intervalHours + 'h, keeping ' + retainCount);
EOF
Restart the worker so the schedule starts, then confirm with step 1. Tell the user backups are on only when that status reports them enabled:
npx claude-mem restart
npx claude-mem backup status
The first automatic snapshot lands about five minutes after the worker starts. To take one now:
npx claude-mem backup run
npx claude-mem backup list
npx claude-mem restore <file>
npx claude-mem backup status
restore stages the snapshot and restarts the worker (it also starts a
worker that is not running). The new worker swaps the database in before it
opens it, saves the database it replaced in the same folder as
claude-mem-<timestamp>-pre-restore.db (restore that file to undo; it counts
toward the retain count), and records the outcome. With cloud sync on, the
restored database resumes syncing from the snapshot's position and can pull
back changes that reached the cloud after it. backup status then prints a "Last restore" line: on success it
names the saved copy; on failure it gives the reason, and the worker kept
the database it had.
Report the snapshot count, the last snapshot time, any error, and the last restore outcome if there was one.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
根据代理工作记录和词元数量,整理每项已完成成果及返工的费用,区分估算金额与实测支出,并生成附有依据的 HTML、JSON 和 CSV 报告。
持续跟踪拉取请求的评审和自动检查,核实反馈是否适用于实际代码,反复修复、测试并推送,直到待处理问题与未解决讨论清零,达到可合并状态。
将编码任务交给子代理,依次执行build、合并已准备好的拉取请求,再从更新后的main进入release,把实现与发布工作连接起来。
检查本地claude-mem运行状态,更新各用户的重要记录缓存,支持排除和恢复记录,并报告不同层级的规则冲突,适合定期运维。
发布后核查公开软件包、线上服务和已安装插件,持续跟踪延迟到达的持续集成结果及故障报告,确认问题是否由此次发布引起,并在授权范围内修复。
指导在Cursor中安装claude-mem,选择本地或远程worker,并配置使用本机登录的host观察处理方式或cmem.ai远程推理。