memex

Featured

Collaborative memory plugin for Claude Code — persistent, searchable, interconnected. Captures the collaborative process as structured memos in an Obsidian vault with hybrid search.

plugin 5 stars 2 forks Updated yesterday MIT

Install

Plugins install via a marketplace, in two steps.

This plugin isn't listed in a marketplace we've indexed. Install it directly from its GitHub repository — the README has the setup steps.

View on GitHub

Bundles

Everything this plugin ships — skills, agents, commands, hooks, and MCP servers it bundles.

Skills (4)

AI & Automation Listed

curator-practice

Operating philosophy for autonomous memex curator tending — orientation protocol, signal triage, bounded work units, initiative thresholds, logging conventions. Trigger on cron-launched runs with no user prompt, "use your judgment", "tend without instructions", "do a pass on the vault", "I'll be away — do what needs doing", or "what should I work on next?" in vault context. For procedural how-to on specific operations (condense, link, archive, crystallize), defer to garden-tending. Do NOT trigger when the user gives an explicit task ("update X project overview", "fix broken links in topics/Y", "condense Z's memos") — those go straight to garden-tending without the judgment layer.

5 Updated yesterday
linxule
AI & Automation Listed

garden-tending

Tend the knowledge garden — diagnose vault health, condense project memos into `_project.md` overviews, create/merge cross-project topics, fix broken links, archive superseded notes, extend trails. Trigger on "tend the garden", "condense", "update project overview", "check vault health", "where are we with X?", "what does this project know?", "extend a trail", or when a `_project.md` is empty/stale, a project has 5+ unprocessed memos, or a concept appears in 2+ projects. For autonomous tending with judgment, prefer curator-practice.

5 Updated yesterday
linxule
Data & Documents Listed

memo-writing

How to write effective session memos — format, frontmatter schema, observation extraction, topic-signal append. Trigger on `/memex:save`, "save this for later", "remember this", "save what we discussed", "document this session", "create a memo", or when the `[memex]` activity nudge appears in context. Do NOT trigger for general note-taking, scratchpads, technical specs, design docs, READMEs, or code comments — memos are session-reflection artifacts that capture what happened (decisions, tensions, surprises, open threads), not project documentation.

5 Updated yesterday
linxule
Data & Documents Listed

recall

Retrieve session memory across 4 modes — TEMPORAL (date browsing), KEYWORD (FTS lookup), DEEP (cross-session synthesis), LOAD (specific file). Trigger on "what did I do yesterday/last week", "why did we...", "remind me...", "find the memo about...", "last time we...", "patterns across projects", "load the X topic". Do NOT trigger for future-oriented questions ("how should we..."), general knowledge, current-session-answerable questions, or vault maintenance (use garden-tending).

5 Updated yesterday
linxule

Commands (3)

open.md save.md status.md

Hooks (6)

hooks.json post-tool-use.py pre-compact.py session-end.py session-start.py user-prompt-submit.py

Quality Score: 76/100

Stars 20%
26
Recency 20%
100
Manifest 20%
100
Documentation 15%
0
Issue Health 10%
80
License 10%
100
Description 5%
100

Details

Author
linxule
Repository
linxule/memex-plugin
Created
3 months ago
Last Updated
yesterday
Language
Python
License
MIT