Claude Skill

memory

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

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download navinspire-ia-navin-navin_skills_memory-e9c73a3.zip · 0 KB

navinspire-ia/navin 31 4 forks AGPL-3.0 Updated 4d ago

Part of navinspire-ia/navin — 182 skills

Install

skills CLI npx skills add https://github.com/Navinspire-ia/navin/tree/main/navin/skills/memory

Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install navinspire-ia-navin@llmmart

Git git clone https://github.com/Navinspire-ia/navin.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole navinspire-ia/navin collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Memory

Structure

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

Search Past Events

.navin/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=".navin/memory/history.jsonl", case_insensitive=true)
grep(pattern="2026-04-02 10:00", path=".navin/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.

Files (navin)

SKILL.md 1.8 KB

---
name: memory
description: Two-layer memory system with Dream-managed knowledge files.
always: true
---

# Memory

## Structure

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

## Search Past Events

`.navin/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=".navin/memory/history.jsonl", case_insensitive=true)`
- `grep(pattern="2026-04-02 10:00", path=".navin/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.