New to Claude Skills? Learn how to install them →

jeremylongshore on GitHub

Cache Management

Free

Efficiently manage your hyperflow memory entries.

Get this skill

Free · Opens the source repo

What Cache Management does

The Cache Management skill provides a comprehensive CRUD interface for handling memory entries within the .hyperflow/memory/ directory. This skill is particularly useful for developers and designers who rely on maintaining project-specific knowledge without altering source code files. Users can view, search, add, edit, prune, archive, or clear memory entries, ensuring that all operations are confined to memory files, thereby preserving the integrity of the original project files.

When using this skill, users can execute various subcommands to interact with their memory. For instance, the show command allows users to view an index of memory entries or filter them by tags, while the search command enables full-text searches across multiple memory files. Adding new entries is straightforward with the add command, which prompts for essential details and categorizes the entry appropriately. The skill also supports editing existing entries, pruning outdated ones, and archiving older entries to keep the memory organized and relevant.

The Cache Management skill is ideal for teams or individuals who want to keep track of their project's evolving knowledge base. By allowing users to manage memory entries without modifying source code, it facilitates a clean separation between project documentation and implementation. This separation is crucial for maintaining clarity and preventing unintended side effects in the codebase. Additionally, the skill's ability to migrate legacy memory entries from older formats ensures that users can transition smoothly to the new memory management system.

Overall, this skill enhances productivity by streamlining the process of managing project knowledge, making it easier to retrieve and update information as needed. It is particularly beneficial for those who frequently reference past decisions, learnings, and patterns within their projects, allowing for a more informed development process.

When to use it

Use this skill when you need to organize, search, or maintain project memory entries in a structured way.

When not to use it

Avoid using this skill for tasks that require direct modifications to source code or for projects not utilizing the hyperflow memory system.

What you can build with it

Organizing Project Knowledge

Use the Cache Management skill to systematically organize and maintain knowledge entries relevant to your project.

Searching for Past Decisions

Quickly retrieve past decisions or learnings by utilizing the search functionality to find specific entries in your memory.

Archiving Old Entries

Keep your memory files clean by archiving entries older than 30 days, ensuring only relevant information is readily accessible.

How to install Cache Management

View source

1. Install with the skills CLI

npx skills add jeremylongshore/claude-code-plugins-plus-skills/cache --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by jeremylongshore

Cache

CRUD interface for .hyperflow/memory/. Full protocol: memory-system.md.

Storage

All operations target .hyperflow/memory/ at the project root. Never modify source code files — if asked to "remember X about file Y", add a memory entry only, never edit Y.

Subcommands

SubcommandDescription
show [tag]Print index or filter entries by tag
search <query>Full-text search across all memory files
add <category> <title>Append a new entry (prompts for details)
edit <entry-id>Find entry by date+title slug and update in place
pruneRemove stale, superseded, and orphaned entries
archiveMove entries older than 30 days to cold storage
clearWipe all memory (with confirmation, recoverable)
statsCounts, tier breakdown, tag frequency, oldest/newest
migrateImport entries from legacy ~/.claude/hyperflow-memory.md
offDisable memory writes for this session
compactSummarise aged memory entries into stubs + monthly archive sidecars

Subcommand Details

show [tag]

No arg → print index.md. With tag → filter all files for matching entries. Output table: Date | Title | Tags | File | Tier

search <query>

grep/ripgrep across learnings.md, decisions.md, pitfalls.md, patterns.md, conventions.md. Return file:line + snippet, ranked by relevance.

add <category> <title>

Categories: learning decision pitfall pattern convention Prompt via AskUserQuestion for: what, why it matters, tags (controlled vocab). Append to the matching file using:

### [YYYY-MM-DD] <title>  `[tag1, tag2]`
**What:** ...
**Why it matters:** ...
**Evidence:** ...

That is the whole write. index.md is derived — scripts/memory-index.py rebuilds it at the next session start. Never append index rows by hand; to refresh it now, run python3 scripts/memory-index.py .hyperflow.

edit <entry-id>

Locate by date+title slug. Show current value, prompt for new value, update in place.

prune

Per memory-system.md pruning protocol:

  • Remove [SUPERSEDED] entries older than 7 days
  • Remove entries whose referenced files no longer exist (test -f)
  • Archive entries unreferenced 90+ days to .hyperflow/memory/archive/YYYY-MM.md Print summary of removed/archived counts.

archive

Compress hot entries older than 30 days → .hyperflow/memory/archive/YYYY-MM.md. Leave one-line summary in original file. The stub keeps its date, so the derived index re-tiers it to cold on its own.

clear

Confirm via AskUserQuestion: "This wipes all memory for this project. Are you sure?" If yes → move all content to .hyperflow/memory/archive/cleared-<timestamp>.md, then reset files to empty stubs.

stats

Print: total entries, hot/warm/cold counts, tag frequency table, oldest and newest entry dates.

migrate

Read ~/.claude/hyperflow-memory.md, filter entries matching current project path. Append matching entries to learnings.md. Leave legacy file untouched. Print count of migrated entries.

off

Print: "Memory writes disabled for this session." No files modified.

compact

User-invoked memory compaction. Summarises entries older than 7 days into stub lines and preserves the full text in monthly archive sidecars at .hyperflow/memory/archive/YYYY-MM.md.

Flow:

  1. The compact subcommand handler reads the target memory file (default: learnings.md; pass a path to target another).
  2. The Date/tag parser splits entries into hot (≤7 days, preserved) and eligible (>7 days). Both [domain, type] and legacy backticked `[domain, type]` tag forms are accepted.
  3. The Compaction Writer is dispatched in a single batch with all eligible entries.
  4. The Stub formatter renders each replacement line as ### [YYYY-MM-DD] Short title [domain, type] — summarized, see archive/YYYY-MM.md.
  5. The Dedup Reviewer performs source-side stub-line match and archive-side header match (date + title + tags on both sides) to prevent duplicates.
  6. The Archive-sidecar writer appends accepted entries to archive/YYYY-MM.md, grouped by each entry's calendar month.
  7. The source file is rewritten with stubs replacing the original entries.
  8. The compact subcommand handler refreshes .hyperflow/memory/.checksums (a memory-scoped sidecar — distinct from .hyperflow/.checksums which the scaffold staleness check owns) and exits with a summary.

Output: N entries compacted into archive/YYYY-MM.md · M stubs rejected as duplicates · source N→M lines. Full protocol in compaction.md.

Flow

  1. Parse invocation to determine subcommand
  2. If subcommand missing → list subcommands table above with one-line descriptions
  3. Execute subcommand
  4. Print structured result with counts/changes summary

Overview

/hyperflow:cache is the operator interface to project-scoped memory under .hyperflow/memory/. It's the only skill that mutates memory files directly (other skills append via the memory-system protocol). Subcommands cover the full lifecycle: show, search, add, edit, prune, archive, clear, stats, migrate. All operations are project-local — entries never leak across projects.

Prerequisites

  • .hyperflow/ initialized (run /hyperflow:scaffold if missing — cache creates .hyperflow/memory/ on first write but expects the parent dir).
  • Write access to .hyperflow/memory/ and .hyperflow/memory/archive/.
  • For migrate only: read access to ~/.claude/hyperflow-memory.md (legacy global memory).

Instructions

See Subcommands and Subcommand Details above for the full operational spec. Summary:

  1. Parse the subcommand from the user's invocation (or list subcommands if none given).
  2. Validate prerequisites for the chosen subcommand (e.g. clear requires AskUserQuestion confirmation; migrate requires legacy file presence).
  3. Execute the subcommand against .hyperflow/memory/.
  4. Print structured result with counts and any file-level changes.

Output

Each subcommand prints a compact summary:

  • show — table of matching entries (Date | Title | Tags | File | Tier).
  • searchfile:line matches with snippets, ranked by relevance.
  • add / edit — confirmation line with new entry id and target file.
  • prune / archive / clear — counts of removed/archived/cleared entries plus destination paths.
  • stats — totals + hot/warm/cold breakdown + top-N tags.
  • migrate — count of migrated entries + source legacy file path.
  • off — single-line Memory writes disabled for this session.

Error Handling

FailureBehavior
.hyperflow/memory/ missingAuto-create skeleton (index.md + 5 category files + archive/.gitkeep) on first write; for read-only subcommands, print (no memory yet — invoke /hyperflow:scaffold first).
Subcommand unknownPrint subcommands table; suggest closest match via Levenshtein distance.
add with invalid categoryReject and list valid categories: learning, decision, pitfall, pattern, convention.
edit entry id not foundList 3 closest matches by title slug + date.
clear without confirmation (headless)Refuse and print clear requires interactive confirmation. Do not wipe.
migrate source file missingPrint (nothing to migrate — ~/.claude/hyperflow-memory.md not found) and stop.

Examples

Show all entries

/hyperflow:cache show

Date         Title                              Tags                  File              Tier
2026-05-16   Bash scoping required by validator [validator, marketplace] learnings.md   hot
2026-05-15   No AI attribution in commits       [convention, git]     conventions.md    hot
2026-05-14   Per-task commits in plugin dev     [convention, git]     conventions.md    hot
3 entries (3 hot, 0 warm, 0 cold)

Search

/hyperflow:cache search "validator"

.hyperflow/memory/learnings.md:42 — "Jeremy's validator requires scoped Bash..."
.hyperflow/memory/decisions.md:8 — "...validator score of 73 → 94 after fix"
2 matches

Add a learning

/hyperflow:cache add learning "Markdown frontmatter needs block scalar for colons"

? What: Block scalar (|) preserves : and backticks in YAML values
? Why it matters: prevents fatal YAML parse failures in marketplace validators
? Tags: yaml, validator, frontmatter
Added — .hyperflow/memory/learnings.md (entry 2026-05-16-block-scalar-frontmatter)

Stats

/hyperflow:cache stats

Memory entries: 47
  Hot   (≤7d)   12
  Warm  (8-30d) 23
  Cold  (30d+)  12
Top tags: validator (8), convention (7), git (6), yaml (4)
Oldest: 2026-02-14   Newest: 2026-05-16

Resources

Frequently asked questions about Cache Management

Similar skills