Agent skill

Gallery Memory

by OPPO-Mente-Lab in OPPO-Mente-Lab/X-OmniClaw

Sync gallery images into long-term memory files and rebuild the user profile from photo-derived memories.

Apache-2.0Auto-check passedAgent Workflows

Install Gallery Memory

skills CLI

$ npx skills add OPPO-Mente-Lab/X-OmniClaw --skill gallery-memory -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install OPPO-Mente-Lab/X-OmniClaw gallery-memory --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/OPPO-Mente-Lab/X-OmniClaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/app/src/main/assets/skills/gallery-memory .claude/skills/gallery-memory && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "gallery-memory" agent skill from https://github.com/OPPO-Mente-Lab/X-OmniClaw/tree/main/app/src/main/assets/skills/gallery-memory into .claude/skills/gallery-memory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gallery-memory", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/OPPO-Mente-Lab/X-OmniClaw/tree/main/app/src/main/assets/skills/gallery-memory

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add OPPO-Mente-Lab/X-OmniClaw --skill gallery-memory -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install OPPO-Mente-Lab/X-OmniClaw gallery-memory --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/OPPO-Mente-Lab/X-OmniClaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/app/src/main/assets/skills/gallery-memory .agents/skills/gallery-memory && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "gallery-memory" agent skill from https://github.com/OPPO-Mente-Lab/X-OmniClaw/tree/main/app/src/main/assets/skills/gallery-memory into .agents/skills/gallery-memory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gallery-memory", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add OPPO-Mente-Lab/X-OmniClaw --skill gallery-memory -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install OPPO-Mente-Lab/X-OmniClaw gallery-memory --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/OPPO-Mente-Lab/X-OmniClaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/app/src/main/assets/skills/gallery-memory .cursor/skills/gallery-memory && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "gallery-memory" agent skill from https://github.com/OPPO-Mente-Lab/X-OmniClaw/tree/main/app/src/main/assets/skills/gallery-memory into .cursor/skills/gallery-memory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gallery-memory", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/OPPO-Mente-Lab/X-OmniClaw.git --path app/src/main/assets/skills/gallery-memory

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add OPPO-Mente-Lab/X-OmniClaw --skill gallery-memory -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install OPPO-Mente-Lab/X-OmniClaw gallery-memory --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/OPPO-Mente-Lab/X-OmniClaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/app/src/main/assets/skills/gallery-memory .gemini/skills/gallery-memory && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "gallery-memory" agent skill from https://github.com/OPPO-Mente-Lab/X-OmniClaw/tree/main/app/src/main/assets/skills/gallery-memory into .gemini/skills/gallery-memory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gallery-memory", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install OPPO-Mente-Lab/X-OmniClaw gallery-memory

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add OPPO-Mente-Lab/X-OmniClaw --skill gallery-memory -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/OPPO-Mente-Lab/X-OmniClaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/app/src/main/assets/skills/gallery-memory .github/skills/gallery-memory && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "gallery-memory" agent skill from https://github.com/OPPO-Mente-Lab/X-OmniClaw/tree/main/app/src/main/assets/skills/gallery-memory into .github/skills/gallery-memory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gallery-memory", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add OPPO-Mente-Lab/X-OmniClaw --skill gallery-memory -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install OPPO-Mente-Lab/X-OmniClaw gallery-memory --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/OPPO-Mente-Lab/X-OmniClaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/app/src/main/assets/skills/gallery-memory .opencode/skills/gallery-memory && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "gallery-memory" agent skill from https://github.com/OPPO-Mente-Lab/X-OmniClaw/tree/main/app/src/main/assets/skills/gallery-memory into .opencode/skills/gallery-memory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gallery-memory", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: gallery-memory
GitHub stars: 265
Token cost: ~786 tokens
SKILL.md length: 344 words
Files: 1
Skills in repo: 14
Repo updated: May 22, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Sync gallery images into long-term memory files and rebuild the user profile from photo-derived memories.

Works in 6 steps: Start with a small max_images value for… → The maintained IMAGE-MEMORY.md format… → Keep each image summary short enough… → …
Tasks that involve Agent memory
SKILL.md covers Preferred Tool, Recommended Calls, Scheduling Pattern and Best Practices
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Gallery Memory is an agent skill from OPPO-Mente-Lab/X-OmniClaw. Sync gallery images into long-term memory files and rebuild the user profile from photo-derived memories.

Its SKILL.md is about 790 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Agent memory. The repository describes itself as: An edge-native Multimodal Android Agent that integrates multimodal perception, memory and action. The licence is Apache-2.0.

When your agent uses it

Tasks that involve Agent memory

Example prompts

“/gallery-memory”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

Start with a small max_images value for the first real-device verification.
The maintained IMAGE-MEMORY.md format should stay compact: filename, time, album (image source bucket), summary, and a clear separator…
Keep each image summary short enough that gallery-qa can load the entire file into context.
Prefer sync before build_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…

What it can do on your machine

Read from SKILL.md and the folder at commit 8614c93. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Gallery Memory loads about 786 tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 344 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~30
When it runs · the whole SKILL.md, loaded when a task matches: ~786

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from OPPO-Mente-Lab/X-OmniClaw at commit 8614c93, republished under its Apache-2.0 licence (© OPPO-Mente-Lab). 344 words, ~786 tokens.

Download SKILL.mdSave it as .claude/skills/gallery-memory/SKILL.md (or your agent's skills folder).

name: gallery-memory
description: Sync gallery images into long-term memory files and rebuild the user profile from photo-derived memories.

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

json

{
  "action": "sync",
  "max_images": 10,
  "update_profile": true
}

Only rebuild profile

json

{
  "action": "build_profile"
}

Check status

json

{
  "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

Example instruction:

使用 gallery_memory 工具同步相册中的新增图片记忆，并更新用户画像。

Best Practices

Start with a small max_images value for the first real-device verification.
The maintained IMAGE-MEMORY.md format should stay compact: filename, time, album (image source bucket), summary, and a clear separator between entries.
Keep each image summary short enough that gallery-qa can load the entire file into context.
Prefer sync before build_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.

Files

Just SKILL.md in app/src/main/assets/skills/gallery-memory of OPPO-Mente-Lab/X-OmniClaw.

Open the folder on GitHubat commit 8614c93

Compare with similar skills

Gallery Memory next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Gallery Memory compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Gallery Memory this skillOPPO-Mente-Lab/X-OmniClaw	265	—	~786	Automated safety check: Pass	Apache-2.0	4 mo ago
Neat-Freak Knowledge CloseoutKKKKhazix/khazix-skills	21k	—	~1.9k	Automated safety check: Pass	MIT	8 days ago
Beads Task Memorygastownhall/beads	28k	—	~1.2k	Automated safety check: Pass	MIT	today
Reflect on Session Learningscursor/plugins	10k	5 repos	~1.2k	Automated safety check: Pass	None	yesterday
MemPalace Memory SearchMemPalace/mempalace	59k	—	~1.4k	Automated safety check: Pass	MIT	yesterday
Compound Learning WriterEveryInc/compound-engineering-plugin	25k	—	~2k	Automated safety check: Pass	MIT	yesterday

Similar skills

Neat-Freak Knowledge Closeout
KKKKhazix/khazix-skills
Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.
21k GitHub stars~1.9k tokensUpdated 8 days ago
Agent WorkflowsAuto-check passed
Beads Task Memory
gastownhall/beads
Tracks multi-session work with dependencies in the bd issue tracker so the agent can find ready tasks and recover its context after conversation compaction.
28k GitHub stars~1.2k tokensUpdated today
Agent WorkflowsAuto-check passed
Reflect on Session Learnings
cursor/plugins
Official
Starts three parallel reviewer subagents over the current conversation transcript, then turns their findings into concrete edits to existing skills.
10k GitHub starsUsed in 5 repos~1.2k tokens
Agent WorkflowsAuto-check passed
MemPalace Memory Search
MemPalace/mempalace
Mines project files and conversation exports into a local, searchable memory palace and recalls past work by semantic search through the mempalace CLI.
59k GitHub stars~1.4k tokensUpdated yesterday
Agent WorkflowsAuto-check passed
Compound Learning Writer
EveryInc/compound-engineering-plugin
Records one solved and verified problem as a durable learning in the repository, but only when the reasoning is not already clear from the final code, tests or docs.
25k GitHub stars~2k tokensUpdated yesterday
Agent WorkflowsAuto-check passed
Session History Search
slopus/happy
Searches past Claude Code, Codex and Cursor sessions and summarizes what was worked on, tried or decided, using extraction scripts instead of reading raw logs.
24k GitHub stars~3.1k tokensUpdated today
Agent WorkflowsAuto-check passed

Questions about Gallery Memory

What does Gallery Memory do?

Sync gallery images into long-term memory files and rebuild the user profile from photo-derived memories. Gallery Memory is an agent skill from OPPO-Mente-Lab/X-OmniClaw. Sync gallery images into long-term memory files and rebuild the user profile from photo-derived memories.

When should I use Gallery Memory?

Gallery Memory fits situations like: tasks that involve Agent memory.

How do I install Gallery Memory in Claude Code?

Run `npx skills add OPPO-Mente-Lab/X-OmniClaw --skill gallery-memory -a claude-code`. Or copy the skill folder (app/src/main/assets/skills/gallery-memory in OPPO-Mente-Lab/X-OmniClaw) into .claude/skills/gallery-memory in your project. Claude Code loads it when a task matches its description.

How do I install Gallery Memory in Codex?

Run `npx skills add OPPO-Mente-Lab/X-OmniClaw --skill gallery-memory -a codex`. Or copy the skill folder (app/src/main/assets/skills/gallery-memory in OPPO-Mente-Lab/X-OmniClaw) into .agents/skills/gallery-memory in your project. Codex loads it when a task matches its description.

Can I use Gallery Memory in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add OPPO-Mente-Lab/X-OmniClaw --skill gallery-memory -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gallery-memory, .gemini/skills/gallery-memory, .github/skills/gallery-memory and .opencode/skills/gallery-memory in your project.

What does Gallery Memory need to run?

SKILL.md names no scripts, command-line tools or credentials: Gallery Memory is instructions for the agent only.

Does Gallery Memory access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Gallery Memory safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Gallery Memory use?

Gallery Memory is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Gallery Memory use?

About 786 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Gallery Memory?

Skills that share tags, products or a category with Gallery Memory: Neat-Freak Knowledge Closeout (KKKKhazix/khazix-skills, 21k stars), Beads Task Memory (gastownhall/beads, 28k stars), Reflect on Session Learnings (cursor/plugins, 10k stars) and MemPalace Memory Search (MemPalace/mempalace, 59k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Gallery Memory?

OPPO-Mente-Lab (a GitHub organization) maintains it in OPPO-Mente-Lab/X-OmniClaw, which has 265 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on May 22, 2026.

Source: OPPO-Mente-Lab/X-OmniClaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Gallery Memory

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Gallery Memory

Preferred Tool

gallery_memory

Recommended Calls

Sync and rebuild profile

Only rebuild profile

Check status

Scheduling Pattern

Best Practices

Files

Compare with similar skills

Similar skills

More from OPPO-Mente-Lab/X-OmniClaw

Related

Questions about Gallery Memory

`gallery_memory`