AugmentClaude

Memory

Manage persistent knowledge files and search conversation history.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/memory-hkuds/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Two-layer memory system with Dream-managed knowledge files.

What this skill does

Memory

Structure

  • SOUL.md — Bot personality and communication style. Managed by Dream. Do NOT edit.
  • USER.md — User profile and preferences. Managed by Dream. Do NOT edit.
  • memory/MEMORY.md — Long-term facts (project context, important events). Managed by Dream. Do NOT edit.
  • memory/history.jsonl — append-only JSONL, not loaded into context. Prefer the built-in grep tool to search it.

Search Past Events

memory/history.jsonl is JSONL format — each line is a JSON object with cursor, timestamp, content.

  • For broad searches, start with grep(..., path="memory", glob="*.jsonl", output_mode="count") or the default files_with_matches mode before expanding to full content
  • Use output_mode="content" plus context_before / context_after when you need the exact matching lines
  • Use fixed_strings=true for literal timestamps or JSON fragments
  • Use head_limit / offset to page through long histories
  • Use exec only as a last-resort fallback when the built-in search cannot express what you need

Examples (replace keyword):

  • grep(pattern="keyword", path="memory/history.jsonl", case_insensitive=true)
  • grep(pattern="2026-04-02 10:00", path="memory/history.jsonl", fixed_strings=true)
  • grep(pattern="keyword", path="memory", glob="*.jsonl", output_mode="count", case_insensitive=true)
  • grep(pattern="oauth|token", path="memory", glob="*.jsonl", output_mode="content", case_insensitive=true)

Important

  • Do NOT edit SOUL.md, USER.md, or MEMORY.md. They are automatically managed by Dream.
  • If you notice outdated information, it will be corrected when Dream runs next.
  • Users can view Dream's activity with the /dream-log command.

Related skills