MemPalace Memory
MemPalace/mempalace
Gives an agent a local memory palace over MCP: verbatim conversation memory, semantic search and a temporal knowledge graph, with a per-session recall protocol.
Admin and maintenance workflows for Ogham shared memory. An agent skill from ogham-mcp/ogham-mcp.
Install Ogham Maintain
$ npx skills add ogham-mcp/ogham-mcp --skill ogham-maintain -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ogham-mcp/ogham-mcp ogham-maintain --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ogham-mcp/ogham-mcp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ogham-maintain .claude/skills/ogham-maintain && rm -rf skills-srcUse ~/.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/
Install the "ogham-maintain" agent skill from https://github.com/ogham-mcp/ogham-mcp/tree/main/skills/ogham-maintain into .claude/skills/ogham-maintain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ogham-maintain", 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 install https://github.com/ogham-mcp/ogham-mcp/tree/main/skills/ogham-maintainType 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.
$ npx skills add ogham-mcp/ogham-mcp --skill ogham-maintain -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ogham-mcp/ogham-mcp ogham-maintain --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ogham-mcp/ogham-mcp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/ogham-maintain .agents/skills/ogham-maintain && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ogham-maintain" agent skill from https://github.com/ogham-mcp/ogham-mcp/tree/main/skills/ogham-maintain into .agents/skills/ogham-maintain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ogham-maintain", 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.
$ npx skills add ogham-mcp/ogham-mcp --skill ogham-maintain -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ogham-mcp/ogham-mcp ogham-maintain --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ogham-mcp/ogham-mcp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/ogham-maintain .cursor/skills/ogham-maintain && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ogham-maintain" agent skill from https://github.com/ogham-mcp/ogham-mcp/tree/main/skills/ogham-maintain into .cursor/skills/ogham-maintain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ogham-maintain", 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 https://github.com/ogham-mcp/ogham-mcp.git --path skills/ogham-maintain--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ogham-mcp/ogham-mcp --skill ogham-maintain -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ogham-mcp/ogham-mcp ogham-maintain --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ogham-mcp/ogham-mcp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/ogham-maintain .gemini/skills/ogham-maintain && rm -rf skills-srcUse ~/.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/
Install the "ogham-maintain" agent skill from https://github.com/ogham-mcp/ogham-mcp/tree/main/skills/ogham-maintain into .gemini/skills/ogham-maintain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ogham-maintain", 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.
$ gh skill install ogham-mcp/ogham-mcp ogham-maintainInstalls 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).
$ npx skills add ogham-mcp/ogham-mcp --skill ogham-maintain -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ogham-mcp/ogham-mcp.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/ogham-maintain .github/skills/ogham-maintain && rm -rf skills-srcUse ~/.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/
Install the "ogham-maintain" agent skill from https://github.com/ogham-mcp/ogham-mcp/tree/main/skills/ogham-maintain into .github/skills/ogham-maintain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ogham-maintain", 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.
$ npx skills add ogham-mcp/ogham-mcp --skill ogham-maintain -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ogham-mcp/ogham-mcp ogham-maintain --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ogham-mcp/ogham-mcp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/ogham-maintain .opencode/skills/ogham-maintain && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ogham-maintain" agent skill from https://github.com/ogham-mcp/ogham-mcp/tree/main/skills/ogham-maintain into .opencode/skills/ogham-maintain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ogham-maintain", 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
ogham-maintain- GitHub stars
- 115
- Token cost
- ~1.1k tokens
- SKILL.md length
- 528 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- MIT
At a glance
Admin and maintenance workflows for Ogham shared memory. An agent skill from ogham-mcp/ogham-mcp.
- Works in 4 steps: Run get_stats to show how many memories… → Check if any profiles have TTLs set… → If there are expired memories, tell the… → …
- The user wants to clean up memories
- SKILL.md covers Available operations and General approach
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Ogham Maintain is an agent skill from ogham-mcp/ogham-mcp. Admin and maintenance workflows for Ogham shared memory. Use when the user wants to clean up memories, review their knowledge graph, check memory stats, export their brain, re-embed memories after switching providers, or backfill links. Triggers on "clean up my memory", "memory stats", "how many memories", "export my brain", "export memories", "review knowledge graph", "re-embed", "link unlinked", "backfill links", "memory health", "ogham stats", "cleanup expired", "condense old memories", "compress memories", or…
Its SKILL.md is about 1.1k 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 Knowledge graphs, MCP servers and Vector databases. It works with Model Context Protocol, pgvector and PostgreSQL. The repository describes itself as: Shared memory MCP server — persistent, searchable, cross-client Claude, Opencode. The licence is MIT.
When your agent uses it
- The user wants to clean up memories
- Review their knowledge graph
- Check memory stats
- Export their brain
Example prompts
- “clean up my memory”
- “memory stats”
- “how many memories”
- “/ogham-maintain”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Run get_stats to show how many memories exist
- Check if any profiles have TTLs set (this info comes from list_profiles)
- If there are expired memories, tell the user how many before running cleanup_expired
- Run cleanup_expired only after confirming with the user -- deletion is permanent
What it can do on your machine
Read from SKILL.md and the folder at commit 7184b6b. 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.
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
Ogham Maintain loads about 1.1k tokens when it runs. Until then it costs about 155 tokens; SKILL.md has 528 words of instructions outside code blocks.
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 ogham-mcp/ogham-mcp at commit 7184b6b, republished under its MIT licence (© ogham-mcp). 528 words, ~1,086 tokens.
Download SKILL.mdSave it as
.claude/skills/ogham-maintain/SKILL.md (or your agent's skills folder).- name
- ogham-maintain
- description
- Admin and maintenance workflows for Ogham shared memory. Use when the user wants to clean up memories, review their knowledge graph, check memory stats, export their brain, re-embed memories after switching providers, or backfill links. Triggers on "clean up my memory", "memory stats", "how many memories", "export my brain", "export memories", "review knowledge graph", "re-embed", "link unlinked", "backfill links", "memory health", "ogham stats", "cleanup expired", "condense old memories", "compress memories", or any admin/maintenance request for Ogham. Requires the Ogham MCP server to be connected.
Ogham maintenance
You handle admin tasks for Ogham shared memory. Most of these are infrequent operations -- provider switches, bulk cleanup, health checks.
Available operations
Health check
Run health_check first if the user reports problems. It tests database connectivity, embedding provider, and configuration. Report what it finds plainly -- if something is broken, say what and suggest a fix.
Stats overview
Run get_stats and list_profiles to give the user a picture of their memory:
- Total memories and breakdown by profile
- Top sources (which clients are storing)
- Top tags (what categories dominate)
- Cache stats via
get_cache_statsif they ask about performance
Present it as a concise summary, not raw JSON.
Cleanup expired memories
- Run
get_statsto show how many memories exist - Check if any profiles have TTLs set (this info comes from
list_profiles) - If there are expired memories, tell the user how many before running
cleanup_expired - Run
cleanup_expiredonly after confirming with the user -- deletion is permanent
Export
Run export_profile with the format the user wants (JSON or Markdown). Tell them where the output goes and how to use it.
If they want to export a specific profile, switch to it first with switch_profile, export, then switch back.
Re-embed all memories
This is needed after switching embedding providers (e.g. Ollama to OpenAI). It regenerates every vector in the active profile.
Before running:
- Confirm the user has switched providers in their config
- Warn that this takes time -- roughly 100ms per memory with a remote provider
- Run
re_embed_allwhich reports progress as it goes
After: suggest running link_unlinked to rebuild the knowledge graph with the new embeddings, since similarity scores will be different.
Backfill knowledge graph links
link_unlinked scans memories that don't have relationship edges yet and creates links where embedding similarity is above threshold.
- Default threshold 0.85 is conservative -- only very similar memories get linked
- Suggest 0.7 for broader connections in diverse collections
- The user can set
batch_sizeto control how many are processed at once
Report how many links were created when it finishes.
Show full SKILL.md (190 more words)Show less
Condense old memories
compress_old_memories shrinks old, inactive memories to save space and reduce search noise.
Three levels:
- Full text (default, recent memories)
- Condensed (key sentences, code blocks preserved, ~30% of original)
- Trace (one-line summary with tags)
Before running:
- Explain that condensing is based on age and activity -- important, frequently-accessed, or high-confidence memories resist condensing
- Explain that original content is always preserved and can be restored
- Run
compress_old_memories-- it reports how many were condensed at each level
Profile management
list_profiles-- show all profiles with memory countsswitch_profile-- change active profile (session only)set_profile_ttl-- set auto-expiry. Explain that expired memories are filtered from searches immediately but not deleted untilcleanup_expiredruns- To remove a TTL, call
set_profile_ttlwithttl_days=None
General approach
These are power-user operations. Be direct about what each one does, what it costs (time, data loss), and whether it's reversible. Deletion and re-embedding are not reversible. Exports, stats, and health checks are read-only and safe to run anytime.
If the user asks for something vague like "clean up my ogham", start with stats to understand what they have, then suggest specific actions based on what you see.
© ogham-mcp, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/ogham-maintain of ogham-mcp/ogham-mcp.
Open the folder on GitHubat commit 7184b6b
Compare with similar skills
Ogham Maintain 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ogham Maintain this skillogham-mcp/ogham-mcp | 115 | — | ~1.1k | Automated safety check: Pass | MIT | |
| MemPalace MemoryMemPalace/mempalace | 60k | — | ~2.7k | Automated safety check: Pass | MIT | |
| Agent RecallGoldentrii/AgentRecall-X | 371 | — | ~5.2k | Automated safety check: Notes | MIT | |
| Cortex Mem MCPsopaco/cortex-mem | 313 | — | ~2.8k | Automated safety check: Pass | MIT | |
| Session Ingestdnotitia/akb | 162 | — | ~8.1k | Automated safety check: Pass | Custom licence | |
| Cognee Docker Setuptopoteretes/cognee | 32k | — | ~901 | Automated safety check: Notes | Apache-2.0 |
Similar skills
Agent Recall
Goldentrii/AgentRecall-X
Persistent compounding memory for AI agents. An agent skill from Goldentrii/AgentRecall-X.
Cortex Mem MCP
sopaco/cortex-mem
Persistent memory enhancement for AI agents. An agent skill from sopaco/cortex-mem.
Session Ingest
dnotitia/akb
Ingest a coding session JSONL into AKB as structured notes — session report + parallel-drafted TIL / task / idea / decision sub-notes.
Cognee Docker Setup
topoteretes/cognee
Runs the Cognee AI memory platform in Docker, from a one-file prebuilt image to a full compose stack with UI, MCP server, Postgres and Neo4j.
Mesh Memory
sickn33/agentic-awesome-skills
Self-hosted semantic memory for AI agents via MCP. An agent skill from sickn33/agentic-awesome-skills.
More from ogham-mcp/ogham-mcp
Ogham Research
ogham-mcp/ogham-mcp
Structured memory capture for Ogham shared memory. An agent skill from ogham-mcp/ogham-mcp.
Ogham Recall
ogham-mcp/ogham-mcp
Smart retrieval from Ogham shared memory. An agent skill from ogham-mcp/ogham-mcp.
Related
Works with
Categories
Questions about Ogham Maintain
What does Ogham Maintain do?
Admin and maintenance workflows for Ogham shared memory. An agent skill from ogham-mcp/ogham-mcp. Ogham Maintain is an agent skill from ogham-mcp/ogham-mcp. Admin and maintenance workflows for Ogham shared memory.
When should I use Ogham Maintain?
Ogham Maintain fits situations like: the user wants to clean up memories; review their knowledge graph; check memory stats; export their brain.
How do I install Ogham Maintain in Claude Code?
Run `npx skills add ogham-mcp/ogham-mcp --skill ogham-maintain -a claude-code`. Or copy the skill folder (skills/ogham-maintain in ogham-mcp/ogham-mcp) into .claude/skills/ogham-maintain in your project. Claude Code loads it when a task matches its description.
How do I install Ogham Maintain in Codex?
Run `npx skills add ogham-mcp/ogham-mcp --skill ogham-maintain -a codex`. Or copy the skill folder (skills/ogham-maintain in ogham-mcp/ogham-mcp) into .agents/skills/ogham-maintain in your project. Codex loads it when a task matches its description.
Can I use Ogham Maintain 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 ogham-mcp/ogham-mcp --skill ogham-maintain -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ogham-maintain, .gemini/skills/ogham-maintain, .github/skills/ogham-maintain and .opencode/skills/ogham-maintain in your project.
What does Ogham Maintain need to run?
SKILL.md names no scripts, command-line tools or credentials: Ogham Maintain is instructions for the agent only.
Does Ogham Maintain 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 Ogham Maintain 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 Ogham Maintain use?
Ogham Maintain is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ogham Maintain use?
About 1.1k tokens (SKILL.md is roughly 4.3k 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 Ogham Maintain?
Skills that share tags, products or a category with Ogham Maintain: MemPalace Memory (MemPalace/mempalace, 60k stars), Agent Recall (Goldentrii/AgentRecall-X, 371 stars), Cortex Mem MCP (sopaco/cortex-mem, 313 stars) and Session Ingest (dnotitia/akb, 162 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ogham Maintain?
ogham-mcp (a GitHub organization) maintains it in ogham-mcp/ogham-mcp, which has 115 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on September 30, 2026.
Source: ogham-mcp/ogham-mcp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.