Agent skill

Memex Retro

by iamtouchskyer in iamtouchskyer/memex

Save insights from completed tasks to Zettelkasten memory. An agent skill from iamtouchskyer/memex.

MITAuto-check passedKnowledge Management

Install Memex Retro

skills CLI
$ npx skills add iamtouchskyer/memex --skill memex-retro -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install iamtouchskyer/memex memex-retro --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/iamtouchskyer/memex.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/memex-retro .claude/skills/memex-retro && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
memex-retro
GitHub stars
143
Token cost
~1.6k tokens
SKILL.md length
541 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Save insights from completed tasks to Zettelkasten memory. An agent skill from iamtouchskyer/memex.

  • Works in 7 steps: Ask yourself: what did I learn from this… → If nothing worth remembering, skip — not… → For each insight, draft an atomic card… → …
  • Tasks that involve Note-taking
  • SKILL.md covers Tools Available, Process, Card Format and Rules, plus 1 more section
  • Calls node

What it does

Memex Retro is an agent skill from iamtouchskyer/memex. Save insights from completed tasks to Zettelkasten memory.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Knowledge Management, covering Note-taking. It works with Visual Studio Code. The repository describes itself as: Zettelkasten-based persistent memory for AI coding agents. Works with Claude Code, Cursor, VS Code Copilot, Codex, Windsurf & any MCP client. No vector DB — just markdown + git… The licence is MIT.

When your agent uses it

  • Tasks that involve Note-taking

Example prompts

  • “/memex-retro”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Ask yourself: what did I learn from this task that would be useful in the future?
  2. If nothing worth remembering, skip — not every task produces insights
  3. For each insight, draft an atomic card (one insight per card)
  4. Fact Hygiene Check — before writing, scan the draft for implicit context that a stranger (or future AI) couldn't decode. Ask three questions
  5. Before writing, memex search for related existing cards
  6. Dedup check: If an existing card already covers this insight, memex read it, then update it by appending new information (use memex write…
  7. If it's genuinely new, write a new card with [[links]] to related cards in the prose

What it can do on your machine

Read from SKILL.md and the folder at commit 453c0e3. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • node

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Memex Retro loads about 1.6k tokens when it runs. Until then it costs about 18 tokens; SKILL.md has 541 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~18
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from iamtouchskyer/memex at commit 453c0e3, republished under its MIT licence (© iamtouchskyer). 541 words, ~1,634 tokens.

Download SKILL.mdSave it as .claude/skills/memex-retro/SKILL.md (or your agent's skills folder).
name
memex-retro
description
Save insights from completed tasks to Zettelkasten memory.
whenToUse
After completing any task involving code changes, architectural decisions, debugging, or non-trivial problem solving. Distill what you learned into atomic…

Memory Retro

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.

Tools Available

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:

bash
# 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.

Process

dot
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"];
}
  1. Ask yourself: what did I learn from this task that would be useful in the future?
  2. If nothing worth remembering, skip — not every task produces insights
  3. For each insight, draft an atomic card (one insight per card)
  4. Fact Hygiene Check — before writing, scan the draft for implicit context that a stranger (or future AI) couldn't decode. Ask three questions:
    • WHO: Every project/product/team mentioned — is it the user's own work or external? Would a reader with zero context know?
    • WHAT-WHEN: Every number (days, tokens, cost) — is it bound to a specific project name and time period?
    • RELATIONSHIP: Words like "对标/参照/基于/借鉴/reference" — spell out the actual relationship (authored, benchmarked against, forked from, inspired by, etc.)
    • If any answer is "a stranger couldn't tell", fix the draft before writing. One sentence of context prevents hallucinated narratives downstream.
  5. Before writing, memex search for related existing cards
  6. Dedup check: If an existing card already covers this insight, memex read it, then update it by appending new information (use memex write with the full updated content)
  7. If it's genuinely new, write a new card with [[links]] to related cards in the prose
Show full SKILL.md (224 more words)Show less

Card Format

markdown
---
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.

Rules

  • Atomic: One insight per card. If you have 3 insights, write 3 cards.
  • Own words: Don't copy-paste. Distill and rephrase — this is the Feynman method.
  • Link in context: [[links]] must be embedded in sentences that explain the relationship.
    • Good: "This contradicts what we found in [[jwt-migration]] — stateless tokens can't be revoked."
    • Bad: "Related: [[jwt-migration]]"
  • Slug: English kebab-case, descriptive. e.g., jwt-revocation-blacklist-pattern
  • Don't over-record: Only save insights that would change how you approach a similar task in the future.
  • Preserve frontmatter on update: When updating an existing card, preserve its original frontmatter fields (title, created). Only append to the body. source is auto-managed by the MCP server.
  • No raw secrets: Never write actual secrets, credentials, tokens, or exact secret file contents into memory. Use redacted examples and abstract descriptions instead.

External Source Cards (Flomo, etc.)

When curating cards from external sources like flomo:

  • Use source: flomo (not source: retro). This is critical for anti-loopback guards.
  • Digest, don't copy. Read the raw memo, extract the genuine insight, rewrite as atomic Zettelkasten card.
  • Merge multiple related memos into one card when they're about the same topic.
  • Skip low-quality fragments — the bar for external imports is higher than session retro.
  • These cards follow the same quality rules above (atomic, own words, linked).

© iamtouchskyer, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/memex-retro of iamtouchskyer/memex.

Open the folder on GitHubat commit 453c0e3

Compare with similar skills

Memex Retro next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Memex Retro compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Memex Retro this skilliamtouchskyer/memex143—~1.6kAutomated safety check: PassMIT
Qmdalsk1992/CloddsBot3k3 repos~1.2kAutomated safety check: PassMIT
Obsidian Canvas BoardsAgriciDaniel/claude-obsidian15k—~1.4kAutomated safety check: PassMIT
LLM Wikilewislulu/llm-wiki-skill655—~3.7kAutomated safety check: PassNone
Para Memory Filespaperclipai/paperclip99k1 repos~909Automated safety check: PassMIT
Copilot History IngestAr9av/obsidian-wiki3.5k—~4.4kAutomated safety check: NotesMIT

Similar skills

  • Qmd

    alsk1992/CloddsBot

    Local hybrid search for markdown notes and docs. An agent skill from alsk1992/CloddsBot.

    3k GitHub starsUsed in 3 repos~1.2k tokens
    Knowledge ManagementAuto-check passed
  • Obsidian Canvas Boards

    AgriciDaniel/claude-obsidian

    Creates, inspects and updates Obsidian JSON Canvas boards in a vault, with text, file, link, group and edge nodes, using safe recoverable edits.

    15k GitHub stars~1.4k tokensUpdated 29 days ago
    Knowledge ManagementAuto-check passed
  • LLM Wiki

    lewislulu/llm-wiki-skill

    Build and maintain a Karpathy-style LLM knowledge base — a self-compiling Obsidian markdown wiki where an Agent ingests raw sources, compiles cross-linked concept/entity/summary pages, answers…

    655 GitHub stars~3.7k tokensUpdated 5 mo ago
    Knowledge ManagementAuto-check passed
  • Para Memory Files

    paperclipai/paperclip

    Use a file-based PARA memory system to store, retrieve, and organize durable knowledge across sessions.

    99k GitHub starsUsed in 1 repo~909 tokens
    Knowledge ManagementAuto-check passed
  • Copilot History Ingest

    Ar9av/obsidian-wiki

    Ingest GitHub Copilot CLI/session history into Obsidian as distilled knowledge.

    3.5k GitHub stars~4.4k tokensUpdated yesterday
    Knowledge ManagementAuto-check: notes
  • Add Frontmatter

    heyitsnoah/claudesidian

    Add or update YAML frontmatter properties to enhance Obsidian note organization.

    2.6k GitHub stars~951 tokensUpdated 6 mo ago
    Knowledge ManagementAuto-check passed

More from iamtouchskyer/memex

  • Agent Prompts Warmup

    iamtouchskyer/memex

    Audit and sync agent instruction files across all coding agent formats.

    143 GitHub stars~1k tokensUpdated 1 mo ago
    Auto-check passed
  • Memex Agentic Memory

    iamtouchskyer/memex

    A-MEM-inspired agentic memory workflow for structured knowledge capture.

    143 GitHub stars~1.7k tokensUpdated 1 mo ago
    Auto-check passed
  • Memex Best Practices

    iamtouchskyer/memex

    Zettelkasten best practices for building a high-quality knowledge graph.

    143 GitHub stars~2.9k tokensUpdated 1 mo ago
    Auto-check passed
  • Memex Organize

    iamtouchskyer/memex

    Periodic maintenance of the Zettelkasten card network. An agent skill from iamtouchskyer/memex.

    143 GitHub stars~1.7k tokensUpdated 1 mo ago
    Auto-check passed
  • Memex Recall

    iamtouchskyer/memex

    Load prior knowledge from Zettelkasten memory when the task likely benefits from past context.

    143 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check passed
  • Memex Sync

    iamtouchskyer/memex

    Sync Zettelkasten cards across devices via git. An agent skill from iamtouchskyer/memex.

    143 GitHub stars~533 tokensUpdated 1 mo ago
    Auto-check passed

Questions about Memex Retro

What does Memex Retro do?

Save insights from completed tasks to Zettelkasten memory. An agent skill from iamtouchskyer/memex. Memex Retro is an agent skill from iamtouchskyer/memex. Save insights from completed tasks to Zettelkasten memory.

When should I use Memex Retro?

Memex Retro fits situations like: tasks that involve Note-taking.

How do I install Memex Retro in Claude Code?

Run `npx skills add iamtouchskyer/memex --skill memex-retro -a claude-code`. Or copy the skill folder (skills/memex-retro in iamtouchskyer/memex) into .claude/skills/memex-retro in your project. Claude Code loads it when a task matches its description.

How do I install Memex Retro in Codex?

Run `npx skills add iamtouchskyer/memex --skill memex-retro -a codex`. Or copy the skill folder (skills/memex-retro in iamtouchskyer/memex) into .agents/skills/memex-retro in your project. Codex loads it when a task matches its description.

Can I use Memex Retro in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add iamtouchskyer/memex --skill memex-retro -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/memex-retro, .gemini/skills/memex-retro, .github/skills/memex-retro and .opencode/skills/memex-retro in your project.

What does Memex Retro need to run?

Going by SKILL.md and its folder, Memex Retro needs the command-line tools its instructions call (node).

Does Memex Retro access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Memex Retro safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Memex Retro use?

Memex Retro is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Memex Retro use?

About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Memex Retro?

Skills that share tags, products or a category with Memex Retro: Qmd (alsk1992/CloddsBot, 3k stars), Obsidian Canvas Boards (AgriciDaniel/claude-obsidian, 15k stars), LLM Wiki (lewislulu/llm-wiki-skill, 655 stars) and Para Memory Files (paperclipai/paperclip, 99k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Memex Retro?

iamtouchskyer (a GitHub user) maintains it in iamtouchskyer/memex, which has 143 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on September 8, 2026.

Source: iamtouchskyer/memex on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.