hf.memory

Capture conversation learnings as structured memory items in a local JSONL store.

5|2|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/T-rav/hydraflow --skill hf-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hf.memory
Source: https://github.com/T-rav/hydraflow/tree/main/.codex/skills/hf.memory
Command: npx skills add https://github.com/T-rav/hydraflow --skill hf-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture Session Learnings as memory items to persist decisions, root causes, configuration choices, and workflow preferences from conversations into a local, machine-readable memory store for future reference.

Core Features & Use Cases

  • Deduplicate and store architectural and process learnings extracted from chat histories to a durable JSONL memory store.
  • Normalize disparate discussion artifacts into structured memory items for quick lookup and retrieval by agents.
  • Use in project retrospectives, incident reviews, and design discussions to preserve decision contexts and rationale.

Quick Start

Trigger memory capture by issuing the /hf.memory command in your chat or IDE to scan the current conversation and persist new memory items to the local JSONL store.

Frequently Asked Questions about hf.memory

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

FAQPage Schema
How do I save conversation decisions and root causes into a knowledge base for future reference?

You can persist conversation decisions and root causes into a knowledge base by extracting them into structured memory items. This Skill scans chat histories, normalizes the discussion artifacts, and stores them locally in a durable JSONL format for future agent lookup.

What is the best way to deduplicate and normalize learnings extracted from chat histories?

The best way to deduplicate and normalize learnings from chat histories is to scan the conversation and apply rules that resolve configuration overlaps. This process structures disparate discussion artifacts into clean, machine-readable memory objects without redundant entries.

Can I capture architectural decisions and configuration choices from project discussions into a local JSONL store?

Yes, you can capture architectural decisions and configuration choices from project discussions into a local JSONL store. Triggering the memory capture command scans your current conversation and persists new structured memory items directly to the local data store.

Does this memory capture approach work for tracking incident reviews and design rationale?

This memory capture approach works effectively for tracking incident reviews and design rationale by preserving decision contexts. It is designed for project retrospectives and design discussions where configuration choices and workflow preferences need persistent tracking.

How do I trigger memory capture to scan my current conversation and persist learnings?

To trigger memory capture, issue the dedicated command in your chat or IDE. This action scans the current conversation, deduplicates the findings, and persists new structured memory items to the local JSONL store for immediate future reference.

Do I need any external dependencies to store conversation learnings as durable memory items?

No external dependencies are required to store conversation learnings as durable memory items. The Skill operates independently to normalize discussion artifacts and writes them directly to a local, machine-readable JSONL memory store.