Agent Skills › QuixiAI/Hexis › core-memory

core-memory

GitHub

提供跨会话记忆检索、精确搜索、经验存储及目标维护功能。支持语义回忆、文档查阅与持久化记录，确保对话连续性。

skills/installed/core-memory/SKILL.md QuixiAI/Hexis

触发场景

用户询问可能已存在于记忆中的信息当前对话包含值得保存的信息需要创建或更新目标/计划回答文档暂存审批请求

安装

npx skills add QuixiAI/Hexis --skill core-memory -g -y

更多选项

非标准路径

npx skills add https://github.com/QuixiAI/Hexis/tree/main/skills/installed/core-memory -g -y

不安装直接使用

npx skills use QuixiAI/Hexis@core-memory

指定 Agent (Claude Code)

npx skills add QuixiAI/Hexis --skill core-memory -a claude-code -g -y

安装 repo 全部 skill

npx skills add QuixiAI/Hexis --all -g -y

预览 repo 内 skill

npx skills add QuixiAI/Hexis --list

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_availability for a cheap check when unsure whether memory is likely to help.
Use recall for targeted retrieval. Prefer specific queries over broad ones.
Use search_history for 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_documents for files or search_document_chunks for citable passages -> open_document / open_document_chunk for read-only inspection -> load_documents / load_document_chunks (with a reason) when the material must stay searchable -> search_history with sources=["desk"] while reasoning -> open_desk_item to scroll long items -> cite the document/chunk/page handle. Run list_desk first -- do not re-load what is already on the desk. pin_desk_item what stays actively needed; clear_desk when done (cleared items archive; sources stay in the cabinet).
Use remember when 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; use manage_schedule only 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.