メニュー
Use after important user-approved decisions, when durable context should be proposed or reviewed, and for explicit Link memory lifecycle work: remember, recall, review, update, archive, restore, forget, or explain local memories through the CLI without requiring MCP.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use at the start of Link work when readiness is unclear, after installs or upgrades, and before repairs; verify health, inspect interrupted writes, back up, and repair generated indexes without MCP.
Use before answering work that may depend on user memory, project history, source-backed notes, or prior decisions; retrieve compact Link context through the CLI without loading the whole wiki or requiring MCP.
Use when raw files are present, source pages look stale, or a user asks to ingest notes into Link; refresh source-backed wiki pages, propose memories, and validate updates through the CLI without MCP.
| name | link-memory |
| description | Use after important user-approved decisions, when durable context should be proposed or reviewed, and for explicit Link memory lifecycle work: remember, recall, review, update, archive, restore, forget, or explain local memories through the CLI without requiring MCP. |
Use this skill after important user-approved decisions, preference changes, project conventions, or long work sessions that may deserve durable context. In a source checkout, replace lnk with python3 link.py. Do not silently save durable memory; propose first unless the user directly asks to remember, approves a proposal, or explicitly confirms an important decision should become durable memory.
If Link session hooks are installed for this agent, the memory brief is injected automatically at session start — skip step 1 and go straight to task-specific recall.
Prime before work:
lnk brief "<current task>" [link-root]
Recall specific memory:
lnk recall "<topic>" [link-root]
End a session with proposal-only memory candidates:
lnk session-end <session-notes-or-transcript> [link-root] --limit 3
Use - as the input when piping a transcript on stdin. Show the proposals to the user; do not save durable memory until the user approves one.
Save an explicit memory:
lnk remember "<user-approved memory>" [link-root] --type note --scope user
Use --project <slug> for project-scoped memory, --visibility private|project|team for sharing intent, --review-after YYYY-MM-DD for stale-risk memories, and --expires-at YYYY-MM-DD for temporary context.
When a brief or recall reports a memory backlog (pending captures or reviews above threshold), offer the user a short consolidation pass:
lnk consolidate [link-root]
The plan is read-only: it groups duplicates and recurring themes and prints accept/discard/review commands. Apply an action only after the user approves it.
Review and explain before trusting uncertain memory:
lnk memory-inbox [link-root]
lnk explain-memory <name-or-title> [link-root]
lnk review-memory <name-or-title> [link-root]
Change lifecycle safely:
lnk update-memory <name-or-title> "<new text>" [link-root]
lnk archive-memory <name-or-title> [link-root] --reason "<why>"
lnk restore-memory <name-or-title> [link-root]
lnk forget-memory <name-or-title> [link-root] --confirm
When duplicate or conflict warnings appear, prefer updating, reviewing, or archiving existing memory over creating another page.