Agent Skills
› QuixiAI/Hexis
› core-memory
core-memory
GitHub提供跨会话记忆检索、精确搜索、经验存储及目标维护功能。支持语义回忆、文档查阅与持久化记录,确保对话连续性。
Trigger Scenarios
用户询问可能已存在于记忆中的信息
当前对话包含值得保存的信息
需要创建或更新目标/计划
回答文档暂存审批请求
Install
npx skills add QuixiAI/Hexis --skill core-memory -g -y
SKILL.md
Frontmatter
{
"name": "core-memory",
"category": "system",
"contexts": [
"heartbeat",
"chat"
],
"requires": {
"tools": [
"recall",
"search_history",
"remember"
]
},
"bound_tools": [
"recall",
"search_history",
"remember",
"add_evidence",
"belief_history",
"open_memory",
"search_documents",
"open_document",
"open_documents",
"load_documents",
"search_document_chunks",
"open_document_chunk",
"load_document_chunks",
"list_desk",
"open_desk_item",
"pin_desk_item",
"unpin_desk_item",
"clear_desk",
"sense_memory_availability",
"read_journal",
"write_journal",
"search_journal",
"manage_goals",
"manage_schedule",
"manage_responsibility",
"manage_backlog",
"list_document_fade_requests",
"resolve_document_fade",
"associate",
"explore_concept",
"explore_subgraph",
"trace_why",
"get_procedures",
"get_strategies"
],
"description": "Semantic recall, exact cross-session search, remembering, and normal continuity"
}
Core Memory and Continuity
Use this skill for ordinary continuity: recalling relevant memories, opening exact source material, storing new experiences, maintaining goals, consulting the permanent journal, and resolving pending document-fade approvals.
When to Use
- The user asks about something that may already be in memory.
- The current conversation contains information worth preserving.
- A goal, schedule item, backlog item, or journal entry should be created or updated.
- The user answers a document-fade approval request.
- Before claiming you do not know something, check memory when the answer plausibly lives there.
Method
- Use
sense_memory_availabilityfor a cheap check when unsure whether memory is likely to help. - Use
recallfor targeted retrieval. Prefer specific queries over broad ones. - Use
search_historyfor exact names, phrases, or details from earlier sessions, especially when semantic recall is weak or embeddings are unavailable. - When the answer depends on an ingested source rather than distilled memory,
climb the cabinet ladder:
search_documentsfor files orsearch_document_chunksfor citable passages ->open_document/open_document_chunkfor read-only inspection ->load_documents/load_document_chunks(with a reason) when the material must stay searchable ->search_historywithsources=["desk"]while reasoning ->open_desk_itemto scroll long items -> cite the document/chunk/page handle. Runlist_deskfirst -- do not re-load what is already on the desk.pin_desk_itemwhat stays actively needed;clear_deskwhen done (cleared items archive; sources stay in the cabinet). - Use
rememberwhen a durable fact, event, preference, promise, or decision should persist. - Use journal tools only for deliberate permanent entries, not ordinary memory.
- Use goal, schedule, or backlog tools when the user asks for ongoing commitments or work tracking. For durable watch-and-notify commitments that outlive the conversation ("let me know whenever X happens", "watch for email from Hope", recurring medication reminders), use
manage_responsibility; usemanage_scheduleonly for simple timed reminders that observe nothing. - Use document approval tools when the user explicitly says to keep or let an ingested document fade.
Quality Guidelines
- Memory is evidence, not omniscience. If retrieved context is weak or absent, say so.
- Do not store secrets unless the user explicitly asks.
- Do not turn every minor sentence into memory; persist what will matter later.
- Keep tool use proportional. A direct answer does not need a recall if the answer is already present in the current conversation.
Version History
-
97f625f
Current 2026-08-29 01:30
修复审批门禁逻辑,使技能可达;增加别名机制提升匹配精度;将只读日常工具设为始终可用;重新绑定孤儿工具至核心记忆等技能。
- 990da5f 2026-08-20 13:52


