remember

Capture user corrections as methodology notes with deduplication and provenance metadata.

Updated Feb 3, 2026

Search Tags:#context #methodology #learning #notes #friction #remember

Ready to run

npx skills add https://github.com/LopeWale/amplLABS --skill remember-lopewale

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: remember
Source: https://github.com/LopeWale/amplLABS/tree/main/.claude/skill-sources/remember
Command: npx skills add https://github.com/LopeWale/amplLABS --skill remember-lopewale

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture friction as actionable methodology notes, turning corrections into persistent guidance.

Core Features & Use Cases

Three modes: explicit description, contextual review, and session mining to create or update notes.
Automatic filing to ops/methodology and linking to existing notes for deduplication.

Quick Start

Use /remember to capture a friction as a methodology note by providing a description.

Frequently Asked Questions about remember

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

FAQPage Schema

How do I capture contextual corrections as persistent methodology notes?▼

You can capture contextual corrections as persistent methodology notes by using explicit, contextual, or session mining modes to identify friction points. The system stores these actionable notes in ops/methodology with deduplication and provenance metadata.

What is the best way to track learning friction from user interactions across sessions?▼

Tracking learning friction across sessions is done through session mining mode, which identifies correction patterns across conversations. It automatically files these friction points as categorized methodology notes with session source provenance.

Can I automatically deduplicate methodology notes when capturing new friction points?▼

Yes, you can automatically deduplicate methodology notes when capturing new friction points. The system links new corrections to existing notes in the ops/methodology directory, preventing redundant entries while preserving original provenance metadata.

How do I document workflow friction points without interrupting my current task?▼

You can document workflow friction points without interruption by using contextual review mode, which identifies corrections during interactions. This automatically extracts friction and files it to ops/methodology without requiring explicit manual input.

Does explicit mode require a specific format to create actionable notes from corrections?▼

Explicit mode requires a simple text description of the friction point to create an actionable note. It uses this description to generate a methodology note filed in ops/methodology, complete with categorization and mode provenance metadata.

When should I use session mining instead of explicit description for capturing methodology notes?▼

Use session mining instead of explicit description when you need to identify correction patterns across past conversations rather than a single friction point. Session mining extracts methodology notes from historical interactions, while explicit mode captures immediate user-described corrections.