Token导航 LogoToken导航

Agent Skill · 研究检索

memory-file-manager-teman(内存文件管理器)

memory-file-manager-teman 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

memory-file-manager-teman 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为需要联网;许可证为 MIT-0,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 9,302。

总安装 14,517周安装 593GitHub Stars 公开资料未说明下载 4,697核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
0.2.2

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:memory-file-manager-teman(内存文件管理器)
来源仓库:https://github.com/teman2050/memory-file-manager-teman
安装命令:
openclaw skills install memory-file-manager-teman
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install memory-file-manager-teman

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

memory-file-manager-teman 主动蒸馏 MEMORY.md 内容,每日定时提取关键信息并优化结构。适用于 OpenClaw 中需要持续维护高质量记忆文件的自动化运维场景。支持空闲时段运行,推迟至低负载时间执行以防影响主流程性能。

安装命令为 openclaw skills install memory-file-manager-teman,需配置定时任务权限。使用前应验证蒸馏逻辑是否保留核心语义,避免过度精简导致信息失真。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install memory-file-manager-teman;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

memory-file-manager-teman 怎么安装?

在终端执行 openclaw skills install memory-file-manager-teman。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

memory-file-manager-teman 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

memory-file-manager-teman 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

memory-file-manager-teman 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

memory-file-manager-teman 用的人多吗?

公开数据是累计安装 14,517 次,近一周安装 593 次,下载 4,697 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

memory-file-manager-teman 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。

先想清楚的地方

  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
memory-file-manager-teman

内存文件管理器 · 本页

14,517—需要联网MIT-0有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
dream
description
>-
version
0.2.2
metadata
openclaw
emoji
🌙
homepage
https://github.com/teman2050/dream-skill
requires
bins
config
install
formula
jq
bins
[jq]

Dream — Proactive Memory Distillation v5

Core Purpose

OpenClaw natively solves capture and search:

  • Capture: compaction flush automatically writes important content to memory/YYYY-MM-DD.md
  • Search: openclaw memory search provides hybrid vector + BM25 search

The gaps Dream fills:

  • The native system never proactively maintains MEMORY.md (relying on occasional manual AI writes means content only grows, never shrinks)
  • The native system has no active handling for MEMORY.md's 20,000-character limit: when exceeded, content is silently truncated — the AI receives no warning and quietly loses the latter half of context, which users rarely notice.

Dream triggers compression at 18,000 characters, moving stale content into the ledger, ensuring MEMORY.md stays within effective bounds and always contains the most current, relevant content

  • No permanent archive (ledger) in the native system
  • No Re-emergence detection mechanism in the native system

Dream's role is distiller, not capturer — and it does not reinvent the search wheel.


File Responsibilities

OpenClaw native (Dream read-only)
└── memory/YYYY-MM-DD.md     ← auto-written by compaction flush; Dream reads as source material

Dream actively maintains
├── MEMORY.md                ← updated each distillation, fully injected into context each conversation; brevity is paramount
│                               Hard limit: 18,000 chars (native truncation at 20,000, keeping 2,000 buffer)
│
{DREAM_VAULT_PATH}/
├── ledger.md                ← permanent archive, append-only, never deleted
├── ledger-index.json        ← structured index for ledger retrieval
├── meta/
│   ├── removed-entries.json ← summaries of entries removed from MEMORY.md (for Re-emergence)
│   ├── last-review.txt      ← timestamp of last completed distillation
│   └── dream-state.txt      ← active | hibernating | pending
└── obsidian-index/
    ├── _index.md            ← main content index (reverse chronological)
    └── topics/<topic>.md    ← topic-based classification

Files intentionally omitted:

  • ~~cache.md~~ → handled natively by memory/YYYY-MM-DD.md
  • ~~custom search index~~ → handled natively by openclaw memory search

MEMORY.md Structure Spec

Dream maintains MEMORY.md in three sections, with total character count strictly capped at 15,000:

## Current State
<!-- Active projects, unresolved decisions, recent important changes -->
<!-- Changes fastest — check for updates on every distillation -->

## Stable Knowledge
<!-- Tech stack, work environment, decision style, core preferences, repeatedly validated judgments -->
<!-- Changes slowly — only update when new evidence warrants it -->

## Relationships & Context
<!-- Important people, ongoing collaborations, key external context -->
<!-- Update as needed -->

## Dream
<!-- Auto-maintained by Dream skill — do not edit manually -->
<!-- Last 5 ledger entries as one-line summaries, so AI knows what was recently archived permanently -->

Content NOT written to MEMORY.md:

  • Observable real-time facts (uses Mac, prefers dark theme)
  • Granular log entries (these live in memory/YYYY-MM-DD.md, searchable anytime)
  • Completed/expired state (moved to ledger, then removed from MEMORY.md)

Real-time Capture (During Conversation, Without Waiting for Review)

When the following content is discovered mid-conversation, write directly to the appropriate MEMORY.md section (do not wait for 03:30), and also record in the current day's memory/YYYY-MM-DD.md:

Write to MEMORY.md immediately:

  • User explicitly corrects the AI's judgment ("No, actually...") → update Stable Knowledge
  • User announces an important decision outcome ("I've decided...") → update Current State
  • User describes a newly started project → update Current State

Write to memory/YYYY-MM-DD.md only, await the 03:30 distillation:

  • Emotional events, preference discussions, opinion expressions
  • Single-occurrence information whose importance is not yet certain

Before writing, check MEMORY.md size (dream-tools.sh --check-size). If over 16,000 characters, first compress the oldest completed entries in Current State, then write.


Operations

dream review — Daily Distillation (Core)

Fully automatic, runs silently (no messages pushed when triggered at 03:30).

Steps:

Step 1 — Pre-flight Checks

dream-tools.sh --check-idle   → busy? write "pending", retry in 15 min, max until 06:00
dream-tools.sh --check-size   → read current MEMORY.md character count

Step 2 — Read Source Material

Read memory/YYYY-MM-DD.md files added since the last distillation (incremental, no reprocessing). If no new files exist, skip distillation and only update last-review.txt.

Step 3 — AI Distillation Judgment

For each journal entry, apply the following rules:

DecisionConditionAction
Update MEMORY.mdNew progress or correction over existing entryReplace the corresponding line
Add to MEMORY.mdAppears across 2+ dates, or single occurrence but clearly importantAppend to appropriate section
Ledger onlyImportant but completed/expired; no need to stay in contextRemove from MEMORY.md, archive to ledger
IgnoreFiller content, single low-value occurrence, near-duplicate already existsDiscard

Re-emergence Check (required on every distillation): Compare against meta/removed-entries.json. If journal content is semantically similar (>70%) to a previously removed entry, rewrite that entry to MEMORY.md with a [re-emerged] tag; elevate its priority so it won't be easily removed in the next distillation. Also append a re-emergence event record to the ledger.

Step 4 — Character Limit Protection (Run Before Writing)

Projected post-write size > 15,000 chars?
  → Compress oldest completed entries in "Current State": move to ledger, remove from MEMORY.md
  → Compress highest-redundancy entries in "Stable Knowledge": merge similar entries
  → Repeat until projected post-write size ≤ 18,000 chars

Step 5 — Atomic Write to MEMORY.md

dream-tools.sh --atomic-write MEMORY.md <tmpfile>
# Write to .tmp first, validate format and char count (≤ 18,000), then mv to replace

Step 6 — Archive Operations

For entries judged "ledger only" during this distillation:

dream-tools.sh --ledger-append <id> <category> <content>
# Append block to ledger.md, update ledger-index.json

Ledger entry format:

---
ID: a3f8c201
Archived: 2026-02-27 03:31
Category: [decision]
Content: Decided to use Obsidian instead of Notion for local data ownership and Git sync
Source: memory/2026-02-27.md, first occurrence
---

Step 7 — Update Meta

  • Append today to active-days.json (deduplicated)
  • Update last-review.txt
  • Update ## Dream section: one-line summaries of the last 5 ledger entries (overwrite)

Step 8 — Review Log (Archived Monthly)

# Append to meta/review-YYYY-MM.md
### YYYY-MM-DD 03:30
Updated: N | Added: N | Archived: N | Re-emerged: N | Ignored: N
MEMORY.md chars: N → N

When triggered manually, also output a summary:

🌙 Distillation complete
MEMORY.md: N chars (limit 15,000)
This run: updated N | added N | archived N
Permanent archive total: N records

Search: Fully Delegated to Native — No Custom Index

# Everyday search (memory/ directory + MEMORY.md, hybrid vector+BM25)
openclaw memory search "<keyword>"

# Deep retrieval (including permanent archive)
# Step 1: Use native search for memory portion
openclaw memory search "<keyword>"
# Step 2: Search the ledger
dream-tools.sh --ledger-search "<keyword>"
# Step 3: Merge output with source labels

dream search <keyword> wraps both steps and clearly distinguishes sources in output:

🔍 Results for "Obsidian":

── OpenClaw Memory ──
· memory/2026-02-27.md: Decided to use Obsidian instead of Notion...
· MEMORY.md [Stable Knowledge]: Primary note tool: Obsidian...

── Permanent Archive ──
· [a3f8c201] 2026-02-27 [decision] Decided to use Obsidian instead of Notion (archive score 22)

── Obsidian Content Index ──
· OpenClaw + Obsidian Integration Notes (2026-02-15)

dream index <content> — Add to Obsidian Index

  1. Hash-based dedup on URL/title — skip if already exists
  2. Extract metadata: title, source, date, topic tags (≤5), one-line summary
  3. Append to obsidian-index/_index.md and the relevant topics/<topic>.md
  4. If content clearly reflects user preferences, also write one record to the current day's memory/YYYY-MM-DD.md for the next distillation

dream status — Status Overview (Read-only Meta, Low IO)

🌙 Dream Status — YYYY-MM-DD HH:MM
MEMORY.md: N chars / 18,000 limit (N%)
Permanent archive: N records
Last distillation: YYYY-MM-DD HH:MM (N hours ago)
System state: active / hibernating (dormant N days) / pending (deferred, waiting N min)
Obsidian index: N entries
Pending journals: N files (added since last distillation)

dream forget <description> — Remove from Memory

Semantic search in memory/YYYY-MM-DD.md and MEMORY.md for matching entries and remove them. No confirmation required — executes immediately.

Re-emergence mechanism: On removal, write the entry summary to meta/removed-entries.json along with removal timestamp and content hash. If the content reappears in a later conversation, automatically trigger re-emergence: rewrite to MEMORY.md and elevate priority. Content that was forgotten and then reappears is more worth keeping than content that was never forgotten.

Ledger records are not affected by dream forget — they are permanently preserved. On execution, inform the user: "Removed from memory. The permanent archive is unaffected."


dream init — Cold-Start Setup

  1. Create {DREAM_VAULT_PATH} directory structure
  2. If MEMORY.md is empty or missing, ask 5 seed questions:

tool preferences, work environment, the most important current project, core value judgments, the most important relationships

  1. Write answers directly into the appropriate MEMORY.md sections (no waiting for distillation)
  2. Write dream-state.txt = active

dream wakeup — Wake from Hibernation

Automatically triggered on the first new conversation after 7 consecutive inactive calendar days:

  1. Output last 3 ledger entries + current MEMORY.md snapshot summary
  2. Restore active state — no content is deleted

Utility Script dream-tools.sh

dream-tools.sh --check-idle
# Query openclaw agent status, return idle / busy

dream-tools.sh --check-size
# Return current MEMORY.md character count (using wc -c)

dream-tools.sh --hash "<content>"
# Return 8-char MD5 short hash for ID generation and dedup

dream-tools.sh --atomic-write <target-file> <tmp-file>
# Validate tmp-file format and char count, then mv to replace target-file

dream-tools.sh --ledger-append <id> <category> <content> [<note>]
# Append a block to ledger.md, update ledger-index.json

dream-tools.sh --ledger-search "<keyword>"
# Search ledger-index.json, return matching entries

dream-tools.sh --dedup-index "<url-or-hash>"
# Check if obsidian-index already has this entry, return exists / new

Dependencies: jq (JSON), wc (character count), md5sum (hashing). No Python or Node required.


Scheduled Trigger (Add to SOUL.md)

Run dream review --scheduled every day at 03:30

Deferral logic:

  • 03:30: check idle → busy → write "pending" → retry in 15 minutes
  • Retry window: 03:45 / 04:00 / ... / 06:00
  • 06:00: force execute, no further deferral
  • Fully silent — no messages pushed; results written to meta/review-YYYY-MM.md

Hibernation Protection

ConditionBehavior
7 consecutive inactive calendar daysWrite "hibernating"; 03:30 heartbeat skips entirely, zero IO
First new conversationTrigger dream wakeup; no content deleted

IO Principles

  • All writes go to .tmp first, then atomically replaced — crash-safe
  • ledger / obsidian-index are append-only, never rewritten
  • status reads only small meta files — never touches ledger or MEMORY.md body
  • In hibernation state, 03:30 heartbeat is skipped entirely — zero file operations
  • Character count is forcibly checked before any MEMORY.md write; exceeding 18,000 is not permitted

平台分布

OpenClaw

92.36%
按下载量换算4,338

安全审计

VirusTotal

可疑

ClawScan

通过

Static analysis

未展示

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills