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.
Sorts what you learned in a session into the right memory surface, filtering out ephemeral notes and duplicates before anything is stored.
Install Remember Project Knowledge
$ npx skills add zereight/gitlab-mcp --skill remember -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install zereight/gitlab-mcp remember --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/zereight/gitlab-mcp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/remember .claude/skills/remember && 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 "remember" agent skill from https://github.com/zereight/gitlab-mcp/tree/main/.github/skills/remember into .claude/skills/remember/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remember", 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/zereight/gitlab-mcp/tree/main/.github/skills/rememberType 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 zereight/gitlab-mcp --skill remember -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install zereight/gitlab-mcp remember --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zereight/gitlab-mcp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/remember .agents/skills/remember && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "remember" agent skill from https://github.com/zereight/gitlab-mcp/tree/main/.github/skills/remember into .agents/skills/remember/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remember", 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 zereight/gitlab-mcp --skill remember -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install zereight/gitlab-mcp remember --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zereight/gitlab-mcp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/remember .cursor/skills/remember && 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 "remember" agent skill from https://github.com/zereight/gitlab-mcp/tree/main/.github/skills/remember into .cursor/skills/remember/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remember", 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/zereight/gitlab-mcp.git --path .github/skills/remember--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 zereight/gitlab-mcp --skill remember -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install zereight/gitlab-mcp remember --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zereight/gitlab-mcp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/remember .gemini/skills/remember && 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 "remember" agent skill from https://github.com/zereight/gitlab-mcp/tree/main/.github/skills/remember into .gemini/skills/remember/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remember", 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 zereight/gitlab-mcp rememberInstalls 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 zereight/gitlab-mcp --skill remember -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/zereight/gitlab-mcp.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/remember .github/skills/remember && 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 "remember" agent skill from https://github.com/zereight/gitlab-mcp/tree/main/.github/skills/remember into .github/skills/remember/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remember", 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 zereight/gitlab-mcp --skill remember -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install zereight/gitlab-mcp remember --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zereight/gitlab-mcp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/remember .opencode/skills/remember && 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 "remember" agent skill from https://github.com/zereight/gitlab-mcp/tree/main/.github/skills/remember into .opencode/skills/remember/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remember", 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
remember- GitHub stars
- 2k
- Used in
- 1 other repo
- Token cost
- ~846 tokens
- SKILL.md length
- 408 words
- Files
- 1
- Skills in repo
- 24
- Repo updated
- First seen
- Licence
- MIT
At a glance
Sorts what you learned in a session into the right memory surface, filtering out ephemeral notes and duplicates before anything is stored.
- Works in 5 steps: Gather the relevant session findings → Classify each item → Propose the best destination for each item → …
- Saving a convention discovered during a session for future work
- SKILL.md covers When to Use, When NOT to Use, Memory Surfaces and Workflow, plus 4 more sections
- Calls npm
What it does
When you ask the agent to remember, save or memorize something, this skill gathers the session's findings and classifies each one as a durable project fact, a temporary working note, an operator preference or instruction, or a duplicate, stale or conflicting item. It then proposes a destination among project memory, session context or docs and instructions, writes only to the appropriate one, and reports what was stored, where, and any conflicts found.
A three-question quality gate runs before anything is committed: is it actionable, will it still be true in 3 months, and is it unique rather than a copy of an existing entry. A no on any question means skipping storage. Entries stay concise, uncertain items are marked as uncertain, and nothing gets dumped into a single store. A rule such as using bcrypt for passwords passes the gate, while a note that the API was slow because of a reboot does not.
When your agent uses it
- Saving a convention discovered during a session for future work
- Cleaning duplicate or conflicting entries out of stored memory
- Deciding whether a finding belongs in project memory or session notes
- Turning scattered findings into structured memory entries
Example prompts
- “Remember that we always run the build before pushing, and store it with the project conventions.”
- “Go through today's findings and tell me which are worth keeping long term.”
- “Check our stored memory for duplicate or conflicting entries about deployment.”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Gather the relevant session findings
- Classify each item
- Propose the best destination for each item
- Write or update only the appropriate memory surface
- Call out duplicates or conflicts that should be cleaned up
What it can do on your machine
Read from SKILL.md and the folder at commit 0109168. 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
Shell commands in SKILL.md call:
npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
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
Remember Project Knowledge loads about 846 tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 408 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 zereight/gitlab-mcp at commit 0109168, republished under its MIT licence (© zereight). 408 words, ~846 tokens.
Download SKILL.mdSave it as
.claude/skills/remember/SKILL.md (or your agent's skills folder).- name
- remember
- description
- Promote reusable project knowledge to the right memory surface. Activate when user says: remember this, save this, store this, remember, memorize, keep this for later.
- argument-hint
- [what to remember]
Remember
Promote durable, reusable knowledge into the right memory surface instead of leaving it buried in chat history.
When to Use
- User wants to preserve knowledge discovered during a session
- Organizing scattered findings into structured memory
- Cleaning up duplicate or conflicting stored information
When NOT to Use
- Ephemeral task notes → just keep in conversation
- Already documented in code or docs → reference directly
Memory Surfaces
| Surface | Use For | Durability |
|---|---|---|
| Project memory | Durable team/project knowledge | Permanent |
| Session context | Short-lived working notes | Session only |
| Docs / Instructions | Conventions, instructions | Permanent |
Workflow
- Gather the relevant session findings
- Classify each item:
- Durable project fact
- Temporary working note
- Operator preference or instruction
- Duplicate / stale / conflicting information
- Propose the best destination for each item
- Write or update only the appropriate memory surface
- Call out duplicates or conflicts that should be cleaned up
Rules
- Do not dump everything into one store
- Prefer project memory for durable team knowledge
- Keep entries concise and actionable
- If something is uncertain, mark it as uncertain rather than storing it as fact
Output
- What was stored
- Where it was stored
- Any duplicates/conflicts found
Quality Gate (Before Storing)
Before committing anything to memory, apply this 3-question filter. Skip storage if the answer to any question is "No":
| Question | Rationale |
|---|---|
| Is it actionable? "Does this tell someone what to DO in a future situation?" | Observations are not memory entries; decisions are. |
| Is it durable? "Will this still be true in 3 months, or is it tied to a temporary workaround?" | Ephemeral findings belong in session notes, not project memory. |
| Is it unique? "Does something close already exist in memory that covers this?" | Duplicate entries create confusion; prefer updating existing entries. |
Show full SKILL.md (129 more words)Show less
Examples
| Item | Actionable? | Durable? | Unique? | Store? |
|---|---|---|---|---|
"Use bcrypt cost=12 for passwords in this project" | ✅ | ✅ | ✅ | YES |
| "API was slow today because server was rebooting" | ❌ | ❌ | ✅ | NO — ephemeral |
"Always run npm run build before pushing" | ✅ | ✅ | Check existing | YES if not already stored |
| "The login page has a bug in dark mode" | ❌ | ❌ | ✅ | NO — file a bug, not a memory entry |
"We prefer interface over type for object shapes" | ✅ | ✅ | Check existing | YES if not in coding-standards |
When to Update vs Create
- UPDATE an existing entry if the new information refines, corrects, or supersedes it
- CREATE a new entry only if no existing entry covers the topic
- DELETE entries that are provably outdated (check with user first)
See Also
/coding-standards— canonical rules reference (no need to duplicate into memory)/skill-stocktake— audit memory surfaces for quality
© zereight, 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 .github/skills/remember of zereight/gitlab-mcp.
Open the folder on GitHubat commit 0109168
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in zereight/gitlab-mcp, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Remember Project Knowledge 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 |
|---|---|---|---|---|---|---|
| Remember Project Knowledge this skillzereight/gitlab-mcp | 2k | 1 repos | ~846 | Automated safety check: Pass | MIT | |
| MemPalace Memory SearchMemPalace/mempalace | 59k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Context Mode Searchmksglu/context-mode | 26k | — | ~250 | Automated safety check: Pass | Custom licence | |
| LoopX Doc Registryloopx-project/loopx | 6.2k | — | ~707 | Automated safety check: Pass | Apache-2.0 | |
| LLM WikiYeachan-Heo/oh-my-claudecode | 40k | — | ~721 | Automated safety check: Pass | MIT | |
| Forgetful File StorageScottRBK/forgetful | 301 | — | ~618 | Automated safety check: Pass | MIT |
Similar skills
Context Mode Search
mksglu/context-mode
Search context-mode's persistent FTS5 knowledge base for previously indexed local project content, documentation, or session memory. Trigger…
LoopX Doc Registry
loopx-project/loopx
Registers durable project materials such as design docs, SOPs and research notes in a LoopX project's own registry so future agents can find them without raw URLs or private content.
LLM Wiki
Yeachan-Heo/oh-my-claudecode
Keeps a persistent markdown wiki of project and session knowledge that the agent can ingest into, query, lint and read across sessions.
Forgetful File Storage
ScottRBK/forgetful
Stores screenshots, PDFs, diagrams, fonts and other binary files in the Forgetful knowledge base, with a retrieval-friendly description and an attachment route.
Project Learnings Manager
garrytan/gstack
Lets you review, search, prune and export the learnings gstack has collected across sessions, and surfaces them when a past fix or pattern comes up.
More from zereight/gitlab-mcp
All 24 skills in this repoOMG Mode Canceller
zereight/gitlab-mcp
Detects which autonomous OMG mode is currently active - Autopilot, Ralph, Ultrawork, UltraQA, Team or Self-Improve - and shuts it down cleanly.
CCG Tri-Model Orchestration
zereight/gitlab-mcp
Runs a task through Codex and Gemini CLIs in parallel alongside Claude, then synthesizes the three outputs into one answer with agreements and conflicts called out.
Cross-Language Coding Standards
zereight/gitlab-mcp
Shared reference for naming, function size, complexity and error handling rules that reviewer agents apply across TypeScript, Python, Go, Rust, Java, C# and Swift.
Pre-Commit Security Scan
zereight/gitlab-mcp
Runs a fast security sweep of recent code changes before a commit or PR, checking for leaked secrets, vulnerable dependencies, unsafe input handling and auth gaps.
Skill Inventory Stocktake
zereight/gitlab-mcp
Audits a project's skill directories for broken frontmatter, missing template sync and quality gaps, then produces a health report of what needs fixing.
OMG Mode Status
zereight/gitlab-mcp
Reports which OMG modes are active, such as autopilot, ralph, team, ultraqa and self-improve, with phase, story or cycle progress read from their state files.
Related
Categories
Questions about Remember Project Knowledge
What does Remember Project Knowledge do?
Sorts what you learned in a session into the right memory surface, filtering out ephemeral notes and duplicates before anything is stored. When you ask the agent to remember, save or memorize something, this skill gathers the session's findings and classifies each one as a durable project fact, a temporary working note, an operator preference or instruction, or a duplicate, stale or conflicting item. It then proposes a destination among project memory, session context or docs and instructions, writes only to the appropriate one, and reports what was stored, where, and any conflicts found.
When should I use Remember Project Knowledge?
Remember Project Knowledge fits situations like: saving a convention discovered during a session for future work; cleaning duplicate or conflicting entries out of stored memory; deciding whether a finding belongs in project memory or session notes; turning scattered findings into structured memory entries.
How do I install Remember Project Knowledge in Claude Code?
Run `npx skills add zereight/gitlab-mcp --skill remember -a claude-code`. Or copy the skill folder (.github/skills/remember in zereight/gitlab-mcp) into .claude/skills/remember in your project. Claude Code loads it when a task matches its description.
How do I install Remember Project Knowledge in Codex?
Run `npx skills add zereight/gitlab-mcp --skill remember -a codex`. Or copy the skill folder (.github/skills/remember in zereight/gitlab-mcp) into .agents/skills/remember in your project. Codex loads it when a task matches its description.
Can I use Remember Project Knowledge 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 zereight/gitlab-mcp --skill remember -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/remember, .gemini/skills/remember, .github/skills/remember and .opencode/skills/remember in your project.
What does Remember Project Knowledge need to run?
Going by SKILL.md and its folder, Remember Project Knowledge needs the command-line tools its instructions call (npm).
Does Remember Project Knowledge access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Remember Project Knowledge 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 Remember Project Knowledge use?
Remember Project Knowledge 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 Remember Project Knowledge use?
About 846 tokens (SKILL.md is roughly 3.4k 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 Remember Project Knowledge?
Skills that share tags, products or a category with Remember Project Knowledge: MemPalace Memory Search (MemPalace/mempalace, 59k stars), Context Mode Search (mksglu/context-mode, 26k stars), LoopX Doc Registry (loopx-project/loopx, 6.2k stars) and LLM Wiki (Yeachan-Heo/oh-my-claudecode, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Remember Project Knowledge?
zereight (a GitHub user) maintains it in zereight/gitlab-mcp, which has 2,029 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on October 6, 2026.
Source: zereight/gitlab-mcp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.