ReddRadar
Topic: persistent-memory
34 skills in this topic.
-
mind
Claude Mind - Search and manage Claude's persistent memory stored in a single portable .mv2 file
memvid/claude-brain 355
-
memory
Claude Mind - Search and manage Claude's persistent memory stored in a single portable .mv2 file
memvid/claude-brain 355
-
recall-log
Quick append to daily log without write gate evaluation.
davegoldblatt/total-recall 192
-
recall-init
Scaffold the Total Recall memory directory structure in this project.
davegoldblatt/total-recall 192
-
recall-forget
Mark memory entries as superseded. Preserves history, does not delete.
davegoldblatt/total-recall 192
-
recall-context
Show what memory files are loaded and available in the current session.
davegoldblatt/total-recall 192
-
recall-promote
Review daily logs and promote entries to registers or working memory.
davegoldblatt/total-recall 192
-
recall-status
Show memory system health — word counts, stale entries, hook status, recommendations.
davegoldblatt/total-recall 192
-
recall-init-ids
Add durable IDs to memory entries. Required before /recall-maintain can run.
davegoldblatt/total-recall 192
-
recall-maintain
Pressure-based memory cleanup. Demotes, archives, or pins entries when working memory exceeds budget.
davegoldblatt/total-recall 192
-
recall-search
Search across all memory tiers (registers, daily logs, archive) for relevant information.
davegoldblatt/total-recall 192
-
recall-write
Write a note to memory with write gate evaluation. Only saves behavior-changing facts.
davegoldblatt/total-recall 192
-
ourmem
Shared memory that never forgets. Cloud hosted or self-deployed.
Collective intelligence for AI agents with Space-based sharing across agents and teams.
Use when users say:
- "install ourmem" / "install omem"
- "setup memory" / "setup omem"
- "add memory plugin"
- "ourmem onboarding" / "omem onboarding"
- "memory not working"
- "remember this"
- "save this for later"
- "don't forget"
- "recall preferences"
- "what did I say last time"
- "import memories"
- "share memories"
- "share with user"
- "share memories to someone"
- "team memory"
- "shared space"
- "persistent memory"
- "cross-session memory"
- "collective intelligence"
- "memory analytics"
- "memory stats"
- "self-host memory"
- "deploy memory server"
Even if the user doesn't say "ourmem" or "omem", trigger when they want persistent memory,
memory sharing between agents, memory analytics, or memory import/export.
ourmem/omem 186
-
memory-store
Store a memory in ourmem. Use when user says remember, save, store, or don't forget something.
ourmem/omem 186
-
memory-recall
Search and recall memories from ourmem. Use when user asks to find, recall, search, or remember something.
ourmem/omem 186
-
schema-workflow
Guide an MCP work item through its schema-defined lifecycle — filling required notes using guidancePointer and advancing through gate-enforced phases. Internal skill triggered by hooks and output styles during orchestration workflows. Use when an item has schema tags and needs to progress through queue, work, review, or terminal phases with note gates.
jpicklyk/task-orchestrator 177
-
feature-implementation
Guide the full lifecycle of a feature-implementation tagged MCP item (the feature container) — from queue through review
jpicklyk/task-orchestrator 177
-
work-summary
jpicklyk/task-orchestrator 177
-
status-progression
Navigate role transitions for MCP work items using advance_item. Shows current role, gate status, required notes, and the correct trigger to use. Use when a user says "advance this item", "move to work", "start this task", "complete this item", "what's the next status", "why can't I advance", "unblock this", "cancel this item", or "check gate status".
jpicklyk/task-orchestrator 177
-
spec-quality
Specification quality framework for planning. Defines the minimum bar for what a plan must address — alternatives, non-goals, blast radius, risk flags, and test strategy. Referenced by schema guidance fields during queue-phase note filling. Read this skill whenever filling requirements or design notes for any MCP work item.
jpicklyk/task-orchestrator 177
-
implement
End-to-end workflow for taking MCP work items from backlog to merged PR. Handles git branching, schema-driven planning, implementation, independent review, and PR creation. Composes spec-quality, review-quality, and schema-workflow skills into a single pipeline. Use when a user says "implement this", "work on this item", "fix these bugs", "pick up the next task", "create a PR for this", "go through the backlog", or references specific MCP item IDs for implementation.
jpicklyk/task-orchestrator 177
-
manage-schemas
Create, view, edit, delete, and validate note schemas for the MCP Task Orchestrator in .taskorchestrator/config.yaml — the templates that define which notes agents must fill at each workflow phase. Use when user says "create schema", "show schemas", "edit schema", "delete schema", "validate config", "what schemas exist", "add a note to schema", "remove note from schema", or "configure gates".
jpicklyk/task-orchestrator 177
-
dependency-manager
Visualize, create, and diagnose dependencies between MCP work items. Use when a user says "what blocks this", "add a dependency", "show dependency graph", "why can't this start", "link these items", "unblock this", "remove dependency", or "show blockers".
jpicklyk/task-orchestrator 177
-
create-item
Create an MCP work item from conversation context. Scans existing containers to anchor the item in the right place (Bugs, Features, Tech Debt, Observations, etc.), infers type and priority, creates single items or work trees, and pre-fills required notes. Use this whenever the conversation surfaces a bug, feature idea, tech debt item, or observation worth tracking persistently. Also use when user says "track this", "log this bug", "create a task for", or "add this to the backlog".
jpicklyk/task-orchestrator 177