القائمة
Use when user says "/munin:projectid", "/projectid", or wants to set the current project ID for Munin memory system. Also use when MCP tools fail with "projectId is required" error.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Munin - The Free (or $1.6/mo) Persistent Memory for OpenClaw. Stop your agent from having Alzheimer's.
Use when user mentions "search memory", "remember", "what did we do before", "check memory", "lookup", "find in memory", "memory recall", "tìm memory", or needs to access long-term project memory. Also use when starting a new task and wanting relevant context.
Use when user mentions "ask munin", "@munin", or wants the memory system to respond directly. Also activates automatically at session start to provide project context from long-term memory.
Use when discussing "architecture", "tech stack", "system design", "kiến trúc", "thiết kế", "cấu trúc project", or how components fit together. Also use when proposing or discussing technical changes.
Use when errors, bugs, exceptions, crashes, or failures appear. Also use when user mentions "bug", "lỗi", "crash", "doesn't work", "how to fix", or is troubleshooting. Store every bug fix in the error catalog.
| name | munin-projectid |
| description | Use when user says "/munin:projectid", "/projectid", or wants to set the current project ID for Munin memory system. Also use when MCP tools fail with "projectId is required" error. |
I set or show the current MUNIN_PROJECT environment variable in the project's .env file (NOT in the global ~/.claude/settings.json). Using per-project .env files is required for multi-project workflows.
When user provides a project ID (e.g., /munin:projectid proj_my-project):
MUNIN_PROJECT should be set in the project directory's .env file.munin-claude env set MUNIN_PROJECT <projectId>When user asks to show/check current project (e.g., /munin:projectid without value):
munin-claude env get MUNIN_PROJECT~/.claude/settings.json, warn the user that this is deprecated and should be moved to the project's .env file.If the user has MUNIN_PROJECT in ~/.claude/settings.json:
munin-claude env get MUNIN_PROJECTcd ~/projects/my-project.env: munin-claude env set MUNIN_PROJECT <value>settings.json: edit ~/.claude/settings.json, remove the MUNIN_PROJECT entry from the env block.| Priority | Source |
|---|---|
| 1 (highest) | Explicit MUNIN_PROJECT env var in shell |
| 2 | MUNIN_PROJECT in $PROJECT_DIR/.env.local |
| 3 | MUNIN_PROJECT in $PROJECT_DIR/.env |
| 4 (deprecated) | MUNIN_PROJECT in ~/.claude/settings.json (warning emitted) |
If a project has encryptionEnabled: true or aiPoweredE2EE: true:
.env:
munin-claude env set MUNIN_ENCRYPTION_KEY <user's-hash-key>~/.claude/settings.json (shared across all projects).MUNIN_ENCRYPTION_KEY in its own .env.This skill ensures MUNIN_PROJECT is available so all other Munin skills (memory, architecture, error-catalog) can function correctly.