How do I install the Agentdb Hierarchical Store skill?

Run npx skillmds@latest add ruvnet-agentdb/agentdb-hierarchical-store in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Agentdb Hierarchical Store safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Agentdb Hierarchical Store?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Agentdb Hierarchical Store free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Agentdb Hierarchical Store?

ruvnet (@ruvnet-agentdb) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Agentdb Hierarchical Store by ruvnet-agentdb

Name: Agentdb Hierarchical Store
Rating: 4.2 (5 reviews)
Author: ruvnet

Agentdb Hierarchical Store

Store memories in tier-aware hierarchical memory — working / short-term / long-term — and recall with tier filters. Use for working-set context that should fade, vs facts that should persist, vs patterns that should be searchable forever.

ruvnet Updated Sep 10, 2026

File contents

Hierarchical Store

Three-tier memory matching how humans actually use memory. Each tier has different retention, retrieval cost, and query semantics.

Tiers

Tier	Retention	Use for
working	minutes (auto-expires)	The current task's scratch — files open, hypotheses, in-flight decisions
short	hours-days	Recent session context — what was decided this morning
long	indefinite (until pruned)	Cross-session facts, patterns, lessons

API

agentdb_hierarchical_store(
  key:      <namespace key>           // e.g. 'task:auth-refactor:hypothesis'
  tier:     'working' | 'short' | 'long'
  value:    <stringified content>
  ttl?:     <seconds>                 // overrides tier default
  metadata?: { topic, project, ... }
)

agentdb_hierarchical_recall(
  query:    <semantic or exact key>
  tier?:    <filter>                  // omit to search all tiers
  k?:       5
)

agentdb_hierarchical_delete(
  key:      <namespace key>
  tier?:    <filter>
)

The delete tool was added in agentdb 3.0.0-alpha.13. Before that, there was no first-class way to remove an entry — re-indexing workflows like ruflo's /adr-index couldn't purge stale ADRs. Now they can.

Recall flow

Query working first — it's smallest, freshest, highest signal for "what am I doing right now."
Fall back to short if working returns nothing.
Search long last for established knowledge.
Or search all three with tier=undefined and let the bandit weight by tier × similarity.

Don't

Don't put long-term facts in working — they expire and you lose them.
Don't put session scratch in long — it pollutes searches forever.
Don't forget to set TTL when overriding tier defaults; the engine won't infer it.

---name: agentdb-hierarchical-storedescription: Store memories in tier-aware hierarchical memory — working / short-term / long-term — and recall with tier filters. Use for working-set context that should fade, vs facts that should persist, vs patterns that should be searchable forever.---# Hierarchical StoreThree-tier memory matching how humans actually use memory. Each tier has different retention, retrieval cost, and query semantics.## Tiers| Tier | Retention | Use for ||---|---|---|| **working** | minutes (auto-expires) | The current task's scratch — files open, hypotheses, in-flight decisions || **short** | hours-days | Recent session context — what was decided this morning || **long** | indefinite (until pruned) | Cross-session facts, patterns, lessons |## API```agentdb_hierarchical_store( key: <namespace key> // e.g. 'task:auth-refactor:hypothesis' tier: 'working' | 'short' | 'long' value: <stringified content> ttl?: <seconds> // overrides tier default metadata?: { topic, project, ... })agentdb_hierarchical_recall( query: <semantic or exact key> tier?: <filter> // omit to search all tiers k?: 5)agentdb_hierarchical_delete( key: <namespace key> tier?: <filter>)```The delete tool was added in agentdb 3.0.0-alpha.13. Before that, there was no first-class way to remove an entry — re-indexing workflows like ruflo's `/adr-index` couldn't purge stale ADRs. Now they can.## Recall flow1. Query `working` first — it's smallest, freshest, highest signal for "what am I doing right now."2. Fall back to `short` if working returns nothing.3. Search `long` last for established knowledge.4. Or search all three with `tier=undefined` and let the bandit weight by tier × similarity.## Don't- Don't put long-term facts in `working` — they expire and you lose them.- Don't put session scratch in `long` — it pollutes searches forever.- Don't forget to set TTL when overriding tier defaults; the engine won't infer it.

Frequently asked questions