memo-writing SKILL.md skillA
memo-writing from linxule/memex-plugin is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add linxule/memex-plugin/memo-writing@git:20261028.67d6693Pins git:20261028.67d6693 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- linxule/memex-plugin
- Path
plugins/memex/skills/memo-writing/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261028.67d6693, committed Oct 28, 2026
- First version recorded
- Sep 23, 2026
- Size
- 14,285 bytes
- Repository stars
- 7
- License
- MIT
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…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
> Portable copy of `skills/memo-writing/SKILL.md` for Codex and Kimi Code, generated by `scripts/portable_plugin.py` (do not edit here). Needs the `memex` CLI on PATH. Claude Code names (the Task/Agent tool, `/memex:save`, hooks) map to your host's equivalents.
# Writing Effective Session Memos
## Context
**Date:** (run: `date +%Y-%m-%d`)
**Project:** (run: `basename $(git remote get-url origin 2>/dev/null | sed 's/\.git$//' | xargs basename 2>/dev/null) 2>/dev/null || basename $(pwd)`)
**Topics available for [[wikilinks]]:** (run: `ls $(memex path 2>/dev/null)/topics/*.md 2>/dev/null | xargs -I{} basename {} .md | sort | tr '\n' ' ' || echo "(no topics found)"`)
## Core Principle
**You were there. A subagent reading the transcript later wasn't.** Your memo from full context will always be better than a reconstructed one. Write from experience, not summary.
Capture the **journey**, not just the destination. Future-Claude needs to understand:
- How things were discovered, not just what was found
- What was tried and failed, not just what worked
- What surprised you or was unexpectedly hard
- Where user and AI disagreed or changed direction
## Memo Format
```markdown
---
…Read the whole file at its exact version.
How to install
mdr add linxule/memex-plugin/memo-writing@sha256:50bae75389377105The line at the top of this page pins the label git:20261028.67d6693, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ap7uvwnasfu2tjaa)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Sep 23, 2026 and Oct 28, 2026, about one every 18 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261028.67d6693 latest | 2026-10-28 | 67d6693 | 14,285 B | A | view · diff |
| git:20261028.8eb19a8 | 2026-10-28 | 8eb19a8 | 12,784 B | A | view · diff |
| git:20260923.9411521 | 2026-09-23 | 9411521 | 10,549 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (14285 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
linxule/memex-plugin · 7 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ap7uvwnasfu2tjaa GET https://markdownregistry.com/api/v1/resolve?ref=linxule/memex-plugin/memo-writing GET https://markdownregistry.com/api/v1/blob/50bae7538937710509f0fda98e97388680e0a11e83be44bf1e22db69fad64d72
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from linxule/memex-plugin
Every file in linxule/memex-plugin