gallery-memory

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-qa should consume them
• the full memory/IMAGE-MEMORY.md file 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 rewrite memory/IMAGE-MEMORY.md in compact format (filename, time, album, summary)
• build_profile: rebuild memory/USER-PROFILE.md from existing memories
• status: inspect cursor and output file availability
• reset_cursor: clear the incremental scan cursor
• clear_image_memories: reset memory/IMAGE-MEMORY.md to the initial template
• clear_user_profile: reset memory/USER-PROFILE.md to the initial template
• reset_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 instruction to a natural-language request that clearly tells the agent to use gallery_memory