Agent skill

Memex Agentic Memory

by iamtouchskyer in iamtouchskyer/memex

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

MITAuto-check passedAgent Workflows

Install Memex Agentic Memory

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

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

GitHub CLI
$ gh skill install iamtouchskyer/memex memex-agentic-memory --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-agentic-memory .claude/skills/memex-agentic-memory && 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-agentic-memory
GitHub stars
142
Token cost
~1.7k tokens
SKILL.md length
674 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 8 steps: Input Triage → Draft Atomic Card → Metadata Draft → …
  • Agent Workflows work in your project
  • SKILL.md covers Prerequisite: Feature Flag Guard, Tools Available, Workflow and Rules
  • Calls node

What it does

Memex Agentic Memory is an agent skill from iamtouchskyer/memex. A-MEM-inspired agentic memory workflow for structured knowledge capture.

Its SKILL.md is about 1.7k 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 Agent Workflows. 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

  • Agent Workflows work in your project

Example prompts

  • “/memex-agentic-memory”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Input Triage
  2. Draft Atomic Card
  3. Metadata Draft
  4. Candidate Retrieval
  5. Decision
  6. Preview
  7. Write
  8. Verify

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 Agentic Memory loads about 1.7k tokens when it runs. Until then it costs about 23 tokens; SKILL.md has 674 words of instructions outside code blocks.

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

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). 674 words, ~1,698 tokens.

Download SKILL.mdSave it as .claude/skills/memex-agentic-memory/SKILL.md (or your agent's skills folder).
name
memex-agentic-memory
description
A-MEM-inspired agentic memory workflow for structured knowledge capture.
whenToUse
When experimental.agenticMemory is enabled in .memexrc AND the agent has completed meaningful work that produced reusable insights. This skill provides a…

Agentic Memory Skill (Experimental)

An A-MEM-inspired workflow that uses existing memex primitives to produce higher-quality memory cards through structured observation, enrichment, retrieval, and deliberate linking.

This skill is experimental and requires opt-in.

Prerequisite: Feature Flag Guard

Before proceeding, locate .memexrc using the same precedence as core memex:

  1. $MEMEX_HOME/.memexrc (if MEMEX_HOME env var is set)
  2. Walk up from the current directory looking for .memexrc
  3. ~/.memex/.memexrc (fallback)

Check that experimental.agenticMemory is exactly true.

If the flag is missing, false, or not exactly true, STOP. Use the standard memex-retro skill instead. Do not proceed with the agentic workflow.

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, use the plugin fallback or MCP tools.

Workflow

Step 1: Input Triage

Identify whether there is a memory-worthy insight from the completed work.

Skip if the content is:

  • Temporary or session-specific (current task state, in-progress work)
  • Obvious or well-known (standard library usage, common patterns)
  • Not reusable across future sessions

If nothing is worth remembering, stop here.

Step 2: Draft Atomic Card

For each insight, draft one card:

  • Title: Short, descriptive
  • Slug: English kebab-case (e.g., yaml-array-roundtrip-bug)
  • Body: One atomic insight in your own words. Distill, don't copy.
  • Context: Add explicit project/domain context when the insight would be ambiguous without it
Step 3: Metadata Draft

Generate candidate metadata as simple string fields:

yaml
---
title: <title>
created: <YYYY-MM-DD>
source: <client>
category: <optional>
context: <one sentence explaining domain and purpose>
keywords: <3-8 salient terms, comma-separated>
tags: <broad categories, comma-separated>
---

Important: Store context, keywords, and tags as comma-separated strings, not YAML arrays. This avoids frontmatter serialization issues with the current stringifyFrontmatter implementation.

Step 4: Candidate Retrieval

Before writing, search for related existing cards.

Try semantic search first:

bash
memex search "<topic query>" --semantic --compact --limit 8

If semantic search fails or is unavailable, fall back to keyword search:

bash
memex search "<topic query>" --compact --limit 8

Read the top candidates that look relevant:

bash
memex read <slug>

Limits to avoid runaway retrieval:

  • Max candidate searches: 3
  • Max cards read: 10
  • Max link hops: 2
Step 5: Decision

Choose exactly one primary action per insight:

ActionWhen
createNo existing card covers the insight. Embed [[wikilinks]] in the new card pointing to related candidates when meaningfully related.
updateExisting card covers the same insight but lacks new detail
skipInsight is duplicate, too obvious, or not durable

Rules:

  • Merge/archive is out of scope for this version unless the user explicitly asks.
  • Links must be chosen by the agent after reading candidate cards. Embedding similarity or keyword match is only a candidate signal, not an automatic link decision.
  • Updating existing cards is allowed only after preview (Step 6).
Show full SKILL.md (223 more words)Show less
Step 6: Preview

Before writing, produce a preview of planned changes:

Planned memory changes:
- create: <slug> (<title>)
- update: <slug> because <reason why update is better than new card>
- links: [[a]], [[b]] because <relationship explanation>
- metadata: context/keywords/tags draft

For updates to existing cards, the agent MUST explain why updating is preferable to creating a new card.

Step 7: Write

Use existing memex write paths:

bash
memex write <slug> << 'EOF'
---
title: <title>
created: <YYYY-MM-DD>
source: <client>
category: <optional>
context: <one sentence>
keywords: <comma-separated terms>
tags: <comma-separated categories>
---

<One atomic insight in your own words.>

This relates to [[existing-card]] because <explicit relationship explanation>.
EOF

On update, copy ALL existing frontmatter fields from the current card (title, created, source, category, context, keywords, tags, and any custom fields). Only modify the specific fields previewed in Step 6. Append new information to the body.

Step 8: Verify

After writing:

bash
memex read <slug>

Confirm:

  • Required frontmatter exists (title, created, source)
  • Wikilinks are syntactically valid ([[slug]] format)
  • Body contains the intended insight

Rules

  • Atomic: One insight per card. Multiple insights = multiple cards.
  • Own words: Distill and rephrase. Don't copy-paste.
  • Links in context: [[links]] must appear in sentences explaining the relationship.
    • Good: "This contradicts the approach in [[jwt-migration]] — stateless tokens can't be revoked."
    • Bad: "Related: [[jwt-migration]]"
  • No auto-linking: Never add links based solely on keyword overlap or embedding score.
  • No silent mutation: Never update an existing card without the preview step.
  • Preserve frontmatter: When updating, copy all existing frontmatter fields. Only change fields explicitly previewed.
  • Metadata as strings: Use comma-separated strings for keywords/tags, not arrays.
  • No raw secrets: Never search for or write actual secrets, credentials, tokens, or exact secret file contents. Use redacted examples and abstract descriptions instead.
  • Fallback: If the feature flag is disabled, use memex-retro instead.

© 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-agentic-memory of iamtouchskyer/memex.

Open the folder on GitHubat commit 453c0e3

Compare with similar skills

Memex Agentic Memory 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 Agentic Memory compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Memex Agentic Memory this skilliamtouchskyer/memex142—~1.7kAutomated safety check: PassMIT
Microsoft Skill CreatorMicrosoftDocs/mcp1.9k3 repos~2.1kAutomated safety check: PassCC-BY-4.0
Cao MCP Appsawslabs/cli-agent-orchestrator1.4k—~1.9kAutomated safety check: PassApache-2.0
CC Workflow Studio AI Editorbreaking-brake/cc-wf-studio5.4k—~561Automated safety check: PassCustom licence
Squad Commands Menumicrosoft/waza1.4k1 repos~2.7kAutomated safety check: PassMIT
Agnixagent-sh/agnix445—~874Automated safety check: PassApache-2.0

Similar skills

  • Microsoft Skill Creator

    MicrosoftDocs/mcp

    Official

    Create agent skills for Microsoft technologies using official documentation.

    1.9k GitHub starsUsed in 3 repos~2.1k tokens
    Agent WorkflowsAuto-check passed
  • Cao MCP Apps

    awslabs/cli-agent-orchestrator

    Official

    Enable, operate, and extend CAO's MCP Apps surface — the host-rendered fleet dashboard visible inside MCP App hosts (Claude Desktop, ChatGPT, VS Code Copilot, Goose, Postman).

    1.4k GitHub stars~1.9k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • CC Workflow Studio AI Editor

    breaking-brake/cc-wf-studio

    Creates and edits visual agent workflows in CC Workflow Studio through conversation, with the agent reading and writing the canvas over MCP.

    5.4k GitHub stars~561 tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Squad Commands Menu

    microsoft/waza

    Official

    Shows a categorized, interactive menu of common Squad operations, such as install, upgrade and team management, and collects arguments before running anything.

    1.4k GitHub starsUsed in 1 repo~2.7k tokens
    Agent WorkflowsAuto-check passed
  • Agnix

    agent-sh/agnix

    A skill your agent uses when user asks to 'lint agent configs', 'validate skills', 'check CLAUDE.md', 'validate hooks', 'lint MCP'.

    445 GitHub stars~874 tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Claude Docs Consultant

    centminmod/my-claude-code-setup

    Consult official Claude Code documentation from code.claude.com using selective fetching.

    2.7k GitHub stars~959 tokensUpdated today
    Agent WorkflowsAuto-check passed

More from iamtouchskyer/memex

  • Agent Prompts Warmup

    iamtouchskyer/memex

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

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

    iamtouchskyer/memex

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

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

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

    142 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check passed
  • Memex Retro

    iamtouchskyer/memex

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

    142 GitHub stars~1.6k tokensUpdated 1 mo ago
    Auto-check passed
  • Memex Sync

    iamtouchskyer/memex

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

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

Questions about Memex Agentic Memory

What does Memex Agentic Memory do?

A-MEM-inspired agentic memory workflow for structured knowledge capture. Memex Agentic Memory is an agent skill from iamtouchskyer/memex. A-MEM-inspired agentic memory workflow for structured knowledge capture.

When should I use Memex Agentic Memory?

Memex Agentic Memory fits situations like: agent Workflows work in your project.

How do I install Memex Agentic Memory in Claude Code?

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

How do I install Memex Agentic Memory in Codex?

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

Can I use Memex Agentic Memory 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-agentic-memory -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-agentic-memory, .gemini/skills/memex-agentic-memory, .github/skills/memex-agentic-memory and .opencode/skills/memex-agentic-memory in your project.

What does Memex Agentic Memory need to run?

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

Does Memex Agentic Memory 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 Agentic Memory 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 Agentic Memory use?

Memex Agentic Memory 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 Agentic Memory use?

About 1.7k tokens (SKILL.md is roughly 6.8k 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 Agentic Memory?

Skills that share tags, products or a category with Memex Agentic Memory: Microsoft Skill Creator (MicrosoftDocs/mcp, 1.9k stars), Cao MCP Apps (awslabs/cli-agent-orchestrator, 1.4k stars), CC Workflow Studio AI Editor (breaking-brake/cc-wf-studio, 5.4k stars) and Squad Commands Menu (microsoft/waza, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Memex Agentic Memory?

iamtouchskyer (a GitHub user) maintains it in iamtouchskyer/memex, which has 142 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.