From memex
Saves distilled insights from completed coding tasks to Zettelkasten memory via memex CLI. Use after code changes, architecture, debugging, or problem-solving.
npx claudepluginhub iamtouchskyer/memex --plugin memexThis skill uses the workspace's default tool permissions.
You have access to a Zettelkasten memory system via the `memex` CLI. After completing this task, reflect on what you learned and save valuable insights.
Produces high-quality atomic memory cards from agentic workflows via triage, drafting, metadata enrichment, retrieval, and deliberate linking. Requires experimental.agenticMemory enabled in .memexrc.
PROACTIVELY query Forgetful MCP (mcp__forgetful__* tools) when starting work on any project, when user references past decisions or patterns, when implementing features that may have been solved before, or when needing context about preferences. Save important decisions, patterns, and architectural insights to memory.
Manages persistent semantic memory across sessions: store/retrieve knowledge/TODOs/issues, hybrid semantic search, hierarchy/tags organization, and maintenance tools.
Share bugs, ideas, or general feedback.
You have access to a Zettelkasten memory system via the memex CLI. After completing this task, reflect on what you learned and save valuable insights.
Three equivalent interfaces — use whichever your environment supports:
| CLI (memex in PATH) | Plugin CLI fallback (Claude Code) | MCP tool (VSCode / Cursor) |
|---|---|---|
memex search <q> | node ~/.claude/plugins/cache/cc-plugins/memex/*/dist/cli.js search <q> | memex_search with query arg |
memex read <slug> | node ~/.claude/plugins/cache/cc-plugins/memex/*/dist/cli.js read <slug> | memex_read with slug arg |
memex write <slug> | node ~/.claude/plugins/cache/cc-plugins/memex/*/dist/cli.js write <slug> | memex_write with slug arg and body |
Resolution order: Try memex in PATH first. If not found, define a shell function and use it:
# Define once per session — DO NOT use variable assignment ($VAR won't expand correctly in zsh)
memex() { node $HOME/.claude/plugins/cache/cc-plugins/memex/*/dist/cli.js "$@"; }
# Then use normally
memex search "some query"
memex read some-slug
memex write some-slug << 'EOF'
card content here
EOF
If both CLI approaches fail, use MCP tools (memex_search, memex_read, memex_write).
The rest of this skill uses memex CLI syntax for brevity.
digraph retro {
"Task completed" -> "Distill: what insights came from this task?";
"Distill: what insights came from this task?" -> "Any insights worth keeping?" [shape=diamond];
"Any insights worth keeping?" -> "Done, no card written" [label="no"];
"Any insights worth keeping?" -> "For each insight: draft atomic card" [label="yes"];
"For each insight: draft atomic card" -> "Fact Hygiene Check (WHO/WHAT-WHEN/RELATIONSHIP)";
"Fact Hygiene Check (WHO/WHAT-WHEN/RELATIONSHIP)" -> "Ambiguity found?" [shape=diamond];
"Ambiguity found?" -> "Fix draft: make implicit context explicit" [label="yes"];
"Fix draft: make implicit context explicit" -> "Fact Hygiene Check (WHO/WHAT-WHEN/RELATIONSHIP)";
"Ambiguity found?" -> "memex search for related existing cards" [label="no"];
"memex search for related existing cards" -> "memex read candidates";
"memex read candidates" -> "Existing card covers same insight?" [shape=diamond];
"Existing card covers same insight?" -> "Update existing card (append new info)" [label="yes"];
"Existing card covers same insight?" -> "Write new card with [[links]]" [label="no"];
"Update existing card (append new info)" -> "memex write <existing-card>";
"Write new card with [[links]]" -> "memex write <new-card>";
"memex write <existing-card>" -> "More insights?" [shape=diamond];
"memex write <new-card>" -> "More insights?" [shape=diamond];
"More insights?" -> "For each insight: draft atomic card" [label="yes"];
"More insights?" -> "Done" [label="no"];
}
memex search for related existing cardsmemex read it, then update it by appending new information (use memex write with the full updated content)[[links]] to related cards in the prose---
title: <descriptive title>
created: <today's date YYYY-MM-DD>
source: <auto-filled by client>
category: <optional category>
---
<One atomic insight, written in your own words.>
<Natural language sentences with [[links]] to related cards, explaining WHY they're related.>
Note: You do NOT need to include modified — the CLI auto-sets it on write.
[[links]] must be embedded in sentences that explain the relationship.
jwt-revocation-blacklist-patternsource is auto-managed by the MCP server.When curating cards from external sources like flomo:
source: flomo (not source: retro). This is critical for anti-loopback guards.