Agent Skills
› opensquilla/opensquilla
› memory
memory
GitHub管理OpenSquilla持久化记忆，支持读写USER.md、MEMORY.md及memory目录文件。涵盖记忆检索、更新、删除及边界约束，确保用户画像与长期事实的准确存储与安全合规。
Trigger Scenarios
用户要求记住信息
用户要求回忆或搜索历史记忆
用户要求遗忘或修正记忆
用户要求更新个人档案或长期笔记
Install
npx skills add opensquilla/opensquilla --skill memory -g -y
SKILL.md
Frontmatter
{
"name": "memory",
"always": false,
"metadata": {
"opensquilla": {
"requires_tools": [
"memory_search",
"memory_get"
]
}
},
"triggers": [
"remember",
"recall",
"forget"
],
"provenance": {
"origin": "opensquilla-original",
"license": "Apache-2.0",
"upstream_url": "",
"maintained_by": "OpenSquilla"
},
"description": "Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory\/**\/*.md."
}
OpenSquilla Memory
Use only tools that are visible in the current tool list. This skill explains OpenSquilla's memory source files; it does not make hidden tools available.
Source Files
USER.md: stable user profile fields such as name, preferred address, pronouns, timezone, and durable profile notes. Edit it with visible filesystem tools, notmemory_save.MEMORY.md: curated long-term non-profile facts, preferences, decisions, and constraints.memory/YYYY-MM-DD.mdandmemory/**/*.md: daily, session, or named memory notes.turns/**/*.md: private auto-captured turn state. These files are for audit/future processing and are not indexed or returned by ordinarymemory_search.
The Markdown files are the source of truth. The memory index/database is derived
from curated MEMORY.md and memory/**/*.md files only.
Recall
- Use injected
USER.mdfirst for current user identity/profile questions. - Use
memory_searchfor historical or non-profile recall that is not already in injected context. - Use
memory_getafter search when exact lines or more context are needed.
Remember Or Update
- If the user specifies a memory path, use that exact path if it is a valid memory source file.
- For profile facts, edit
USER.mdwith visible filesystem tools. - For daily or session notes, write to
memory/YYYY-MM-DD.mdor another appropriatememory/**/*.mdsource. - For curated long-term facts in
MEMORY.md, read the current file first and write the full updated content. Ifmemory_saveis available, usemode='replace'forMEMORY.md; do not append to it. - If
memory_saveis available, use it only forMEMORY.mdormemory/**/*.md, never forUSER.md. - If
memory_saveis not available but filesystem tools are visible, edit or create the same source files directly.
Forget Or Correct
- Search first, then read the relevant file/lines before removing anything.
- If
memory_deleteis available, use it only when the user wants to delete a whole memory source file. - To remove or correct one fact, edit the source file directly when filesystem tools are visible.
- If no write or delete tool is available, report the exact path and lines that should be changed instead of claiming the memory was updated.
Boundaries
- Do not store ordinary deliverables such as reports, JSON outputs, or result files in memory source files.
- Do not save secrets, tokens, private keys, or full credential contents.
- Only confirm memory was updated after the write or delete succeeds.
Version History
- 7f72a32 Current 2026-07-05 18:38
