remember

Capture user friction as methodology notes with category, description, and provenance.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/achousal/EngramR --skill remember-achousal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: remember
Source: https://github.com/achousal/EngramR/tree/main/.claude/skills/remember
Command: npx skills add https://github.com/achousal/EngramR --skill remember-achousal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Captures user friction and converts it into actionable methodology notes that guide system behavior and learning.

Core Features & Use Cases

  • Explicit mode: create a methodology note from a direct friction description (/remember "description").
  • Contextual mode: review recent conversation corrections to surface implicit learnings.
  • Session mining: scan stored sessions for recurring patterns and unmined corrections.
  • File management: automatically file notes under ops/methodology/ and update the methodology MOC.
  • Duplication handling: deduplicate against existing notes and link when appropriate.

Quick Start

Invoke /remember with a description to capture explicit friction as a methodology note.

Frequently Asked Questions about remember

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

FAQPage Schema
How do I capture user friction as actionable methodology notes?

To capture user friction as actionable methodology notes, invoke the remember Skill with a description of the friction. It creates a note including category, description, and provenance, filing it under ops/methodology.

How do I extract implicit learnings from conversation corrections?

You can extract implicit learnings from conversation corrections using the contextual mode. This mode reviews recent conversation corrections to surface and capture implicit learnings as structured methodology notes.

Can I scan stored sessions to find recurring friction patterns?

Yes, you can scan stored sessions to find recurring friction patterns. The session mining mode scans ops/sessions to identify unmined corrections and recurring patterns for methodology updates.

How do I avoid duplicate methodology notes when capturing friction?

To avoid duplicate methodology notes, the system automatically deduplicates new notes against existing ones in ops/methodology. It flags potential duplicates or conflicts and links them when appropriate.

What is the best way to update a methodology MOC with new friction notes?

The best way to update a methodology MOC with new friction notes is to let the system handle file management automatically. It files notes under ops/methodology and updates the MOC simultaneously.

Do I need a specific format to document explicit corrections in ops/methodology?

To document explicit corrections in ops/methodology, you must include a category, a description, and the provenance of the friction. This ensures the methodology note is actionable and traceable.