remember

Append structured episodes to a JSONL memory store and classify lessons for promotion.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/yiwei79/root-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/root-azoth/tree/main/.opencode/skills/remember
Command: npx skills add https://github.com/yiwei79/root-azoth --skill remember-yiwei79

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Lessons learned during agent sessions are lost when the session ends. This Skill captures durable decisions, failures, and patterns as structured episodes in .azoth/memory/episodes.jsonl so knowledge persists across sessions. ## Core Features & Use Cases - Episode Capture: Append typed episodes (success, failure, decision, pattern, observation) with lessons, tags, and context to an append-only JSONL store. - Auto-Classification: Classify each episode by scope, reuse potential, and maturity to recommend a future home without triggering automatic promotion. - Promotion Proposals: Surface patterns reinforced across 2+ episodes as human-approved promotion proposals for skills, agents, or pattern files. - Use Case: At the end of a coding session where a TDD approach caught three edge cases, capture a success episode with specific lessons and tags so future sessions can surface and reinforce it. ## Quick Start Ask the agent to remember what was learned in this session by capturing an episode with the key lessons and tags.

Frequently Asked Questions about remember

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

FAQPage Schema
How do I capture lessons learned from an agent session?▼

Append a structured episode to `.azoth/memory/episodes.jsonl` with a type (success, failure, decision, pattern, or observation), a summary, specific actionable lessons, and tags. Capture at least one episode per session during the closeout phase.

What is the episode schema for JSONL memory capture?▼

Each episode includes a UUID, timestamp, session ID, type, goal, summary, lessons array, tags, reinforcement count, and context object with phase, pipeline, and files changed. Episodes are append-only and never edited or deleted.

How do I correct a wrong lesson in an append-only memory log?▼

Create a new episode linked to the older one via `related_episode_id` or `supersedes_episode_id`, and tag it as stale, superseded, or contradicted. Never rewrite or delete the original episode; corrections happen by addition.

When should a pattern be promoted from episodic memory?▼

Propose promotion only when a pattern is reinforced across 2 or more episodes, is generic rather than repo-local, and is objective rather than personal preference. Promotion always requires explicit human approval.

When should I not add a pattern to the promotion path?▼

Skip promotion for single-event lessons, highly repo-local or temporary behaviors, personal preferences, contradictory evidence, or unstable tags. Keep the episode in M3 memory and wait for reinforcement across sessions.