atxp-memory

Agent memory management — cloud backup, restore, and local vector search of .md memory files

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "atxp-memory" with this command: npx skills add atxp-dev/cli/atxp-dev-cli-atxp-memory

ATXP Memory — Agent Memory Management

Manage your agent's .md memory files: back up and restore to/from ATXP cloud servers, and search your local memories using zvec vector similarity search.

Capabilities

CapabilityDescription
Cloud BackupPush/pull .md files to ATXP servers for disaster recovery
Local SearchIndex .md files into a local zvec vector database, then search by natural language query
StatusView cloud backup info and local index statistics

Security Model

  • Only .md files are collected and transmitted (push/pull). No credentials, JSON configs, binaries, or other file types are ever sent.
  • Files are sent to ATXP servers over HTTPS, associated with the authenticated agent's identity.
  • push replaces the server snapshot entirely (latest snapshot only, no history).
  • pull is non-destructive — it writes server files to the local directory but does not delete local files absent from the server.
  • Local search index is stored in a .atxp-memory-index/ subdirectory inside --path. It never leaves the local machine.
  • index and search do not require authentication or network access.
  • Filesystem access: reads from --path directory (push/index), writes to --path directory (pull) and --path/.atxp-memory-index/ (index). No other directories are touched.
  • No modification of OpenClaw config or auth files.

When to Use

SituationCommand
After meaningful changes to SOUL.md, MEMORY.md, or at end of sessionpush
Bootstrapping a fresh workspace or recovering from environment losspull
After updating memory files and before starting a task that requires recallindex
Looking for relevant context in past memoriessearch
Verify backup exists before risky operationsstatus

Commands Reference

CommandDescription
npx atxp@latest memory push --path <dir>Recursively collect all *.md files from <dir> and upload to server
npx atxp@latest memory pull --path <dir>Download backup from server and write files to <dir>
npx atxp@latest memory index --path <dir>Chunk .md files by heading and build a local zvec search index
npx atxp@latest memory search <query> --path <dir>Search indexed memories by similarity
npx atxp@latest memory status [--path <dir>]Show cloud backup info and/or local index stats

Options

OptionRequiredDescription
--path <dir>Yes (push/pull/index/search)Directory to operate on
--topk <n>No (search only)Number of results to return (default: 10)

How Local Search Works

  1. Indexing (memory index):

    • Scans all .md files recursively from --path
    • Splits each file into chunks at heading boundaries (h1/h2/h3)
    • Converts each chunk into a 256-dimensional feature vector using locality-sensitive hashing (unigrams + bigrams)
    • Stores vectors and metadata in a local zvec database (HNSW index) at <path>/.atxp-memory-index/
  2. Searching (memory search):

    • Converts the query text into the same vector representation
    • Performs approximate nearest neighbor search via zvec's HNSW index
    • Returns the top-k most similar chunks with file paths, headings, line numbers, and similarity scores

The search is purely local — no network requests, no API keys, no cost. Re-index after modifying memory files.

Path Conventions

Typical OpenClaw workspace paths:

~/.openclaw/workspace-<id>/
~/.openclaw/workspace-<id>/SOUL.md
~/.openclaw/workspace-<id>/MEMORY.md
~/.openclaw/workspace-<id>/memory/
~/.openclaw/workspace-<id>/AGENTS.md
~/.openclaw/workspace-<id>/USER.md

Backward Compatibility

The backup command is still accepted as an alias for memory:

npx atxp@latest backup push --path <dir>   # works, same as memory push
npx atxp@latest backup pull --path <dir>   # works, same as memory pull
npx atxp@latest backup status              # works, same as memory status

Limitations

  • .md files only — all other file types are ignored during push/index and not present in pull.
  • Latest snapshot only — each push overwrites the previous backup. There is no version history.
  • Requires ATXP auth for cloud operations — run npx atxp@latest login or npx atxp@latest agent register first.
  • --path is required — there is no auto-detection of workspace location.
  • Local search requires @zvec/zvec — install with npm install @zvec/zvec before using index/search.
  • Feature-hash embeddings — local search uses statistical text hashing, not neural embeddings. It works well for keyword and phrase matching but is not a full semantic search. For best results, use specific terms from your memory files.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

atxp

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

atxp-git

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

lark-doc

飞书云文档(v2):创建和编辑飞书文档。使用本 skill 时,docs +create、docs +fetch、docs +update 必须携带 --api-version v2;默认使用 DocxXML 格式(也支持 Markdown)。创建文档、获取文档内容(支持 simple/with-ids/full 三种导出详细度,以及 full/outline/range/keyword/section 五种局部读取模式,可按目录、block id 区间、关键词或标题自动成节只拉部分内容以节省上下文)、更新文档(八种指令:str_replace/block_insert_after/block_copy_insert_after/block_replace/block_delete/block_move_after/overwrite/append)、上传和下载文档中的图片和文件、搜索云空间文档。当用户需要创建或编辑飞书文档、读取文档内容、在文档中插入图片、搜索云空间文档时使用;如果用户是想按名称或关键词先定位电子表格、报表等云空间对象,也优先使用本 skill 的 docs +search 做资源发现。

Repository Source
84.8K9Klarksuite
Coding

lark-base

当需要用 lark-cli 操作飞书多维表格(Base)时调用:搜索 Base、建表、字段管理、记录读写、记录分享链接、视图配置、历史查询,以及角色/表单/仪表盘管理/工作流;也适用于把旧的 +table / +field / +record 写法改成当前命令写法。涉及字段设计、公式字段、查找引用、跨表计算、行级派生指标、数据分析需求时也必须使用本 skill。

Repository Source
84.6K9Klarksuite