remember

Captures session lessons into Azoth's memory system and classifies episodes for promotion.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/yiwei79/azoth --skill remember-yiwei79
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: remember
Source: https://github.com/yiwei79/azoth/tree/main/.opencode/skills/remember
Command: npx skills add https://github.com/yiwei79/azoth --skill remember-yiwei79

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture durable lessons from experience. Every session produces knowledge — this skill ensures it's not lost.

Core Features & Use Cases

  • Episode capture to Azoth's memory system (memory/episodes.jsonl) for durable knowledge retention
  • Auto-classification of lessons to surface patterns and promote to higher memory tiers (M3→M2)
  • Governance-friendly surfacing and linking of episodes to support future recall and decision justification
  • Supports explicit promotion pathways and episodic remediation without mutating historical data

Quick Start

Run the remember capture at session end to archive a new episode and start classification

Frequently Asked Questions about remember

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

FAQPage Schema
How do I capture durable lessons from a session so knowledge isn't lost?

Capturing durable lessons from a session is automated by appending memory episodes to an append-only log. This ensures session knowledge is retained durably without manual effort, classifying lessons for future reuse.

What is the best way to classify session lessons and promote them to higher memory tiers?

Classifying session lessons involves auto-detecting patterns and applying governance rules for M3→M2 memory tier transitions. This promotion pathway surfaces reusable knowledge while enforcing governance over your memory system.

When should I trigger memory episode capture during my workflow?

Memory episode capture should be triggered at session end or after major decisions. Running the capture at these points archives the episode and starts classification, ensuring critical context is preserved.

Can I update or mutate historical memory episodes after they are logged?

Historical memory episodes cannot be mutated because the system uses an append-only log. You can apply episodic remediation and add new linked entries, but original historical data remains unchanged to preserve auditability.

Does the memory system support tagging and linking for session episodes?

The memory system supports tagging and linking for session episodes. This governance-friendly surfacing connects related episodes to support future recall and provide decision justification across sessions.