Home / michielinksee / linksee-memory · GitHub

linksee-memory SKILL.md skillA

linksee-memory from michielinksee/linksee-memory is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add michielinksee/linksee-memory/linksee-memory@git:20261105.8e74853

Pins git:20261105.8e74853 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
michielinksee/linksee-memory
Path
src/skill/SKILL.md
Versions recorded
5
Latest version
git:20261105.8e74853, committed Nov 5, 2026
First version recorded
Jun 9, 2026
Size
32,306 bytes
Repository stars
16
License
MIT

The bridge to the agent's "past self". Before any new task, file edit, decision, or right after a failure, recall past caveats (pain records) / learnings (growth log) / implementation history from linksee-memory. This is the only way to solve Claude Code's "memory amnesia every session" problem. The "never repeat the same mistake" mechanism that Mem0 / Letta / Zep can't provide. エージェントの「過去の自分」への橋。新しい作業・ファイル編集・意思決定・失敗の前後で、linksee-memory から過去の caveat（痛みの記録）/ learning（成長ログ）/ implementation（成功失敗）を…

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

# Linksee Memory Skill — Connecting the agent's past and future

## 🧠 Core Principle

**This skill is the only way to persist agent growth across sessions.**

Claude Code forgets everything when a session ends. The solution the user taught yesterday, the failure you hit today, the decision made three days ago — all of it is normally lost. **linksee-memory is the "memory that doesn't disappear" device.**

Writes are handled automatically by the Stop hook (already running). But **reads require the agent to actively pull**. This skill instills that "go look first" habit in the agent.

*JP: Claude Code は session が終わると全部忘れる。linksee-memory は「消えない記憶」を作る装置。書き込みは Stop hook が自動でやってくれるが、読み出しはエージェントが能動的にやる必要がある。*

---

## 📐 The 6 layers — what goes where

Which layer you record into determines later retrieval accuracy.

| Layer | When to use | Example |
|---|---|---|
| 🎯 `goal` | The user states a clear goal | "want to integrate with freee", "want to npm publish" |
| 📍 `context` | Background on when/why this is happening | "because there's a meeting with company X on Wednesday" |
| 💭 `emotion` | User's temperature / tone | "tired", "excited", "stressed", 「疲れた」「焦ってる」 |
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add michielinksee/linksee-memory/linksee-memory@sha256:fa0b5d9682572c38

The line at the top of this page pins the label git:20261105.8e74853, 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.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_aatyntik4xz2jpxo.svg)](https://markdownregistry.com/a/art_aatyntik4xz2jpxo)

0 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 5 versions of this file, between Jun 9, 2026 and Nov 5, 2026, about one every 37 days.

versioncommittedcommitsizeaudit
git:20261105.8e74853 latest2026-11-05 8e74853 32,306 BA view · diff
git:20261104.dabff5a2026-11-04 dabff5a 32,178 BA view · diff
git:20260907.7e13c962026-09-07 7e13c96 32,015 BA view · diff
git:20260610.a5a6c662026-06-10 a5a6c66 31,516 BA view · diff
git:20260609.d4bf8962026-06-09 d4bf896 29,731 BA view

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (32306 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

GitHub

michielinksee/linksee-memory · 16 stars · license MIT · pushed 2026-11-05 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_aatyntik4xz2jpxo
GET https://markdownregistry.com/api/v1/resolve?ref=michielinksee/linksee-memory/linksee-memory
GET https://markdownregistry.com/api/v1/blob/fa0b5d9682572c3829bd09e35d0224db8be72aadd673b5ca3b43f6f2f946ee13

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.

Browse by kind, by grade A, or by owner.