Skip to main content

wenyuan-memory

Remember and recall what this project's coding sessions have already established

Source facts

Repository
studyzy/wenyuan
Last source activity
October 17, 2026 at 07:25
Detected SKILL.md language
English
Stars
0
Forks
0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
wenyuan-memory
description
Remember and recall what this project's coding sessions have already established
# wenyuan-memory The WenYuan memory service is wired into this coding agent: a lifecycle hook captures the session, an MCP server exposes the memory tools, and this skill tells you how to use them well. ## What happens automatically You do not have to do anything for the basics: the session-start hook primes your context with the memory that is relevant to this project, and the stop hook captures the conversation when the session ends. Treat what the context block says about this project and the user as already-established ground. ## When the user asks you to remember something Store deliberately, not automatically. When the user says to remember, or asks you to capture a document, call the `retain` tool with the content and a short title. When a new initiative or workstream starts and the user wants it tracked, call `create_knowledge_page` with the title and, when it relates to an existing page, the `relates_to` argument naming that page. ## When you need to retrieve something Search first. Call `search_knowledge_base` before answering anything about this project's history, decisions or conventions; read a specific page with `get_knowledge_page`; list what exists under a folder with `get_knowledge_base_tree`; and when the question needs reasoning across several memories rather than a lookup, call `reflect`. Whenever the memory informs your answer, say so: give the user visible credit for where it came from rather than presenting recalled facts as your own. ## When you find memory that is stale Correct it by writing a correction document rather than editing history. Call `retain` with a title prefixed by the correction marker and a body that states what is now true and what it replaces. The old memory stays for provenance; the correction is what future retrievals will surface. ### Using the companion skill Once installed, each host loads the packaged skill from its own skills root. The skill instructs the agent to store deliberately, to retrieve search-first, and to correct stale memory with a correction document — the same tool surface the installed MCP server exposes.
View on GitHub