skills.rest
Simplified-Reasoning
Simplified-ReasoningOFFICIAL
Explore all skills by this author →
WebsiteGitHub

memory

Separate persistent facts from event history and search HISTORY.md with grep.

58|1|Updated May 13, 2026
Search Tags:#memory#personal assistant#workspace context#event log#grep recall#long-term facts
One-click install
npx skills add https://github.com/Simplified-Reasoning/Pi-Bench --skill memory-simplified-reasoning
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: memory
Source: https://github.com/Simplified-Reasoning/Pi-Bench/tree/main/third_party/nanobot/nanobot/skills/memory
Command: npx skills add https://github.com/Simplified-Reasoning/Pi-Bench --skill memory-simplified-reasoning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you organize long-term facts and quickly search past events so you can act with context instead of starting from scratch.

Core Features & Use Cases

  • Two-layer memory system: Long-term facts live in MEMORY.md while an append-only event log lives in HISTORY.md.
  • Greppable event recall: Search HISTORY.md by keyword(s) using grep-style matching to quickly find relevant prior actions, decisions, or events.
  • Automatic consolidation: Older conversations get summarized into HISTORY.md, and stable long-term facts are extracted into MEMORY.md without manual management.

Quick Start

Use grep to search the event log by typing a case-insensitive keyword query against memory/HISTORY.md (optionally combining patterns with an extended regex query) to surface relevant past events.

Frequently Asked Questions about memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I recall past context and search event logs with grep?▼

You can recall past context by running case-insensitive grep keyword queries against memory/HISTORY.md, optionally combining patterns with extended regex, to surface relevant prior actions and decisions.

What is the best way to persist user preferences and project context across sessions?▼

To persist project context, maintain memory/MEMORY.md for stable long-term facts and memory/HISTORY.md for chronological events, ensuring consistent entry formatting for reliable retrieval.

Does this approach require manual management of long-term facts and event history?▼

No, older conversations get summarized into HISTORY.md automatically, and stable long-term facts are extracted into MEMORY.md without manual management, reducing maintenance overhead.

Can I use combined pattern queries to find specific deadlines in the event log?▼

Yes, you can search for deadlines or meetings in HISTORY.md using extended regex queries to combine multiple keyword patterns, enabling precise and rapid retrieval of past events.

What are the limitations of using grep for workspace context retrieval?▼

Grep-based retrieval depends on consistent entry formatting within HISTORY.md and MEMORY.md; without standardized keywords or formatting, matching accuracy for past events may degrade.

Related Skills

Explore More Software Engineering Skills→
yangkun19921001yangkun19921001
37

memory

Maintain persistent context with MEMORY.md for long-term facts and HISTORY.md for event logs.

Community
Intermediate
chenguojun06-starchenguojun06-star
1

lark-workflow-meeting-summary

Collect meeting notes and generate structured summary reports.

Community
Advanced
designnotdrumdesignnotdrum
3

managing-memory

Store structured memories with facts, reasons, sentiment, and implications.

Community
Basic
mindmorassmindmorass
2

qdrant-patterns

Store and retrieve documents in Qdrant for semantic search.

Community
Advanced