remember

Capture behavioral friction as structured observations in JSON files.

226|55|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/Miosa-osa/canopy --skill remember-miosa-osa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: remember
Source: https://github.com/Miosa-osa/canopy/tree/main/library/skills/learning/remember
Command: npx skills add https://github.com/Miosa-osa/canopy --skill remember-miosa-osa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture behavioral friction as structured observations to support continuous improvement of AI systems. When users correct behavior, when patterns emerge, or when conversations reveal gaps, store actionable lessons for later synthesis.

Core Features & Use Cases

  • Explicit mode: capture user-stated lessons directly.
  • Contextual mode: detect and extract corrections from ongoing conversations.
  • Mining mode: scan transcripts to surface recurring frictions and shortcuts.

Quick Start

Tell /remember a lesson learned to capture the observation for system improvement.

Frequently Asked Questions about remember

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

FAQPage Schema
How do I capture behavioral friction from user feedback to improve AI systems?

Capture behavioral friction by logging structured observations from explicit user feedback, contextual corrections, or mined transcripts. These observations are stored as JSON files with category, severity, and confidence metadata to drive system improvements.

What is the best way to extract recurring lessons from conversation transcripts?

Extracting lessons from transcripts uses mining mode to scan for recurring frictions and shortcuts. The system surfaces these patterns and stores them as structured observations for later synthesis, ensuring no behavioral feedback is lost.

How do I deduplicate observations when logging multiple user corrections?

Deduplication is handled automatically within the formal observation model. When logging corrections, the system checks existing stored observations to prevent redundant entries, ensuring your feedback logs remain clean and actionable.

Can I store contextual corrections from ongoing conversations automatically?

Yes, contextual mode detects and extracts corrections directly from ongoing conversations. It automatically captures behavioral friction as structured observations without requiring explicit user commands to log the feedback.

What format are structured observations stored in for later synthesis?

Structured observations are stored as JSON files at ops/observations/{category}/{timestamp}-{slug}.json. This format includes formal metadata like category, severity, confidence, and deduplication status to support later analysis.

How do I synthesize stored observations into actionable system improvements?

Stored observations are synthesized into actionable improvements via the /rethink command. This later synthesis step aggregates the captured feedback, analyzing the structured JSON files to identify and resolve systemic behavioral friction.