Build, query, test, and optimize a local agent memory CLI where durable memories are represented as retrieval unit tests. Use when the user asks Codex to create, maintain, inspect, or improve a memory-cli project; when a workspace already contains a memory-cli, .memory, or memories project; or when Codex must add…
How the Furl context-compression plugin works in Claude Code and Codex — the furlcompress / furlretrieve / furlstats / furlpurge / furlsearch / furllist MCP tools, the > retrieval flow, and Claude Code's optional automatic hooks. Use when the user asks what Furl is doing, how to compress or retrieve content, why…
Use the another-brain MCP tools (remember, search, recent, get, reinforce, forget) as shared long-term memory. Activates at the start of a task that may continue previous work, when recalling past decisions/fixes/preferences, when learning something worth remembering across sessions or agents, or after using a…
View and sync Claude Code, Codex, Grok, and Antigravity memories, plans, tasks, and graph memory mirrored in Eagle Mem. Use when: 'eagle memories', 'show memories', 'sync memories', 'what does the agent remember', 'show plans', 'show tasks', 'mirror memories', 'onboard project', 'what did past sessions learn'. Uses…
Use when the user refers to previous decisions, corrections, forgotten context, already-built work, install/test/release status, source-backed evidence, or next steps in ongoing work. Treat Time Library as a standing active memory routing rule: call timelibraryrecall before answering memory-dependent prompts. Also…
A front-door routing skill for HMA, a long-term memory system. It first identifies what a submitted text or file is, then sends it to the matching storage workflow.
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community…
Format and validate Obsidian wiki links with proper filename, section, and folder conventions. Verify links exist before creation and fix broken links. Use when creating or checking wiki links in markdown files.
File experiment results to the wiki following the SCHEMA Ingest procedure. Use after an experiment run produces metrics, ablations, or comparisons worth keeping as durable project memory.
Use when the user wants AI project memory, task documentation, decision records, bug history, feature notes, context recovery, or "document everything" behavior without forcing a project structure. This skill keeps engineering context recoverable and only creates project files when the user explicitly asks to…
Use this skill when the user wants to build a knowledge base for their project, create an Obsidian wiki from project data, analyze project structure for knowledge management, or mentions "obsidian-kb", "knowledge base", or "compile wiki".
Scaffold a personal LLM wiki (Karpathy pattern) — multi-agent, MCP-ready, with SEO/GEO publish target. Compiles knowledge into a persistent wiki instead of re-deriving from raw docs on every query. One paste from any agent (OpenClaw, Claude Code, Codex, Cursor, Hermes) installs it.
Persistent memory and task coordination for AI coding sessions. Creates a .fireteam/ folder with mission context, task state, checkpoints, and handoff notes that survive session restarts, context limits, and crashes. Use this skill whenever the user wants to set up a fireteam, continue a fireteam, resume after a…
A skill that stores a user's project decisions and constraints in mdbase, a persistent project knowledge store. The records can be reused across sessions and by different coding assistants.
Audits Claude Code context consumption across agents, skills, commands, hooks, MCP servers, and the CLAUDE.md/MEMORY chain. Identifies bloat and redundancy, then produces prioritized token-savings recommendations. Backs the /context-budget command.
Use when the user asks to personalize their assistant, to use vardoger, or to analyze their Windsurf conversation history. Runs the vardoger CLI to read past conversations and generate tailored instructions.
Query and propose local knowledge cards for this repo. Always use at the start of work here — run npx knowcards query before acting. Also use when wrapping up if this session proved a durable repo fact that later work will reuse (at most 2 cards). Skip propose when nothing would change a later action. Skip query only…
Search, recall, and reason over the user's personal knowledge base — their Obsidian/Markdown vault — via the Stellavault MCP server. Use whenever the user refers to their own notes, past decisions, or accumulated knowledge: "search my notes", "what do I know about X", "what did I decide about Y", "from my vault", "my…
Maintain a review-first Markdown knowledge base for Codex practices with source provenance, engineering capture, citation-aware queries, explicit archive and promotion, and deterministic linting. Use when asked to capture a durable engineering lesson, ingest Codex research, query or archive what the repository knows…
A Chinese-language local search tool for finding content in your own documents, code, images, saved web pages, and video dialogue. It can also index new files and find similar content.
Turns handwritten reMarkable notes into a queryable semantic memory. Syncs pages from a reMarkable tablet (via the reMarkable MCP server, rmapi, or a USB/SSH bridge), renders each page to an image and reads the handwriting with Claude vision — no OCR key — then extracts each page into confidence-scored, human-editable…
Use when the user asks to use Throughline from Codex, continue or restore Throughline memory, export read-only handoff context for a local launcher, prepare a new Codex thread handoff, summarize a captured Codex session, or check whether the Throughline Codex Stop hook captured the current session. Hide long…
★not rated 4 5d agoA75 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: