Gallery Memory
Documentsgallery-memoryGallery Memory is an Agent Skill for documents published in the OPPO-Mente-Lab/X-OmniClaw repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Sync gallery images into long-term memory files and rebuild the user profile from photo-derived memories.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/OPPO-Mente-Lab/X-OmniClaw/blob/HEAD/app/src/main/assets/skills/gallery-memory/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/gallery-memory, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Gallery Memory
Use this skill when the user wants to:
- scan new images from the phone gallery
- extract memories from screenshots or photos
- rebuild a user profile from image memories
- schedule periodic gallery memory updates
Do not use this skill as the first choice for questions like 今天我拍了什么照片 or 我最近拍过什么截图.
For image-question answering or gallery-image operations based on existing memory/IMAGE-MEMORY.md, prefer gallery-qa.
This skill is responsible for producing and maintaining image memories.
It is not the primary consumer for gallery-image questions or operations once memory/IMAGE-MEMORY.md already exists.
When image memories are already available:
gallery-qashould consume them- the full
memory/IMAGE-MEMORY.mdfile should be loaded into context - later execution should rely on the filename stored in each entry, not wildcard filename guesses
Preferred Tool
gallery_memory
Use gallery_memory as the direct tool for this workflow.
Supported actions:
sync: scan new gallery images, summarize them, and rewritememory/IMAGE-MEMORY.mdin compact format (filename, time, album, summary)build_profile: rebuildmemory/USER-PROFILE.mdfrom existing memoriesstatus: inspect cursor and output file availabilityreset_cursor: clear the incremental scan cursorclear_image_memories: resetmemory/IMAGE-MEMORY.mdto the initial templateclear_user_profile: resetmemory/USER-PROFILE.mdto the initial templatereset_all: clear both files and reset the scan cursor
Recommended Calls
Sync and rebuild profile
{
"action": "sync",
"max_images": 10,
"update_profile": true
}
Only rebuild profile
{
"action": "build_profile"
}
Check status
{
"action": "status"
}
Scheduling Pattern
To run this periodically, combine it with schedule_task.
Example idea:
- create a scheduled task
- set
instructionto a natural-language request that clearly tells the agent to usegallery_memory
Example instruction:
使用 gallery_memory 工具同步相册中的新增图片记忆,并更新用户画像。
Best Practices
- Start with a small
max_imagesvalue for the first real-device verification. - The maintained
IMAGE-MEMORY.mdformat should stay compact: filename, time, album (image source bucket), summary, and a clear separator between entries. - Keep each image summary short enough that
gallery-qacan load the entire file into context. - Prefer
syncbeforebuild_profile, so the profile reflects the newest image memories. - If the user asks for daily or hourly gallery syncing, combine this skill with
scheduled-automation. - If the user mentions privacy concerns, remind them that sensitive content should be filtered and the feature should only run with explicit authorization.