reasoning-bank

Retrieve and reinforce memories using confidence-weighted scoring across memory directories.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/ToanPV90/dotfiles --skill reasoning-bank
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reasoning-bank
Source: https://github.com/ToanPV90/dotfiles/tree/main/claude/.claude/skills/reasoning-bank
Command: npx skills add https://github.com/ToanPV90/dotfiles --skill reasoning-bank

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves noisy, flat memory retrieval by ranking memories by both confidence and recency, and by letting you deliberately reinforce what proved useful.

Core Features & Use Cases

  • Confidence-weighted retrieval: Searches memory directories and ranks matches using confidence × recency decay so the most relevant memories surface first.
  • Deliberate boosting loop: Updates a memory’s frontmatter (used_count, last_used, and confidence) with a controlled diminishing-returns curve.
  • Pruning-friendly maintenance signal: Flags older, low-confidence entries for eventual decay/pruning by keeping reinforcement and decay semantics aligned with the existing maintenance system.

Quick Start

Run /reasoning-bank retrieve <query> to get the top-ranked memories relevant to your question.

Frequently Asked Questions about reasoning-bank

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

FAQPage Schema
How do I rank memories by confidence and recency in an auto-memory system?

Confidence-weighted memory retrieval ranks memories using a confidence × recency decay formula. It searches project and agent memory directories with grep, parsing YAML frontmatter fields like confidence and last_used to surface the most relevant entries first.

How do I boost useful memories in a CLI workflow?

Run a boost command to deliberately reinforce useful memories by updating their YAML frontmatter. The boost workflow deterministically increments the used_count, updates last_used, and applies a controlled diminishing-returns curve to the confidence field.

What's the best way to flag low-confidence memories for pruning?

Flag low-confidence memories for pruning by keeping reinforcement and decay semantics aligned with your maintenance system. The workflow tracks older, low-confidence entries through frontmatter fields, producing ranked results that signal which entries are ready for eventual decay.

Can I retrieve project and agent memories without auto-boosting their scores?

Yes, memory retrieval is guarded and does not auto-boost scores. The workflow explicitly separates retrieve, boost, and show actions, ensuring that searching for memories with grep does not deterministically update confidence, used_count, or last_used fields.

Does memory retrieval work with missing YAML frontmatter fields?

Memory retrieval works with missing YAML frontmatter fields by applying default values during parsing. It safely handles entries lacking confidence, used_count, or last_used fields, scoring them with defaults so the ranking results remain functional.

Why does my memory retrieval return noisy flat results instead of ranked matches?

Flat memory retrieval returns noisy results when it lacks confidence × recency scoring. By parsing YAML frontmatter fields with defaults and applying a recency decay formula, the workflow ranks matches so the most relevant and reinforced memories surface first.