Agent skill
check-integration
Check Nowledge Mem setup, detect your agent, and guide native plugin installation. Use when the user asks about setup, configuration, or when memory tools aren't working as expected.
Install this agent skill to your Project
npx add-skill https://github.com/nowledge-co/community/tree/main/nowledge-mem-npx-skills/skills/check-integration
SKILL.md
Check Integration
Verify Nowledge Mem is running and guide the user to the best integration for their agent.
When to Use
- User asks about Nowledge Mem setup or configuration
- Memory tools are failing or not available
- User asks "is my memory working?" or "how do I set up Nowledge Mem?"
- First time using Nowledge Mem in this agent
- User asks about upgrading from skills to a native plugin
Step 1: Check nmem CLI
nmem --json status
If this fails, Nowledge Mem is not installed or not running. Guide the user:
- Install: https://mem.nowledge.co/docs/installation
- Start: open the Nowledge Mem desktop app, or run the server
Step 2: Detect Agent and Recommend The Best Path
Do not only answer "install X". Explain the behavior contract the user will get:
- what starts automatically
- what is only guided by skills/rules and still model-driven
- whether threads are captured automatically, saved explicitly, or only supported as handoff summaries
Use this priority order:
- Native integration first when the host has one
- Reusable package when the host supports shared skills/prompts but has no native integration
- Direct MCP only when there is no better package path
Fresh users care about outcome, not transport. Tell them what they will actually get after setup.
Autonomy levels
| Path | What usually happens | What it does not guarantee |
|---|---|---|
| Native integration | Strongest setup: session bootstrap is often automatic; some hosts also add auto-capture or hook-driven recall | Exact proactive recall/distill timing can still be host-specific |
| Reusable package | Working Memory, recall, and distill are guided by rules/skills | The host may still ignore the guidance unless prompts and project guidance are strong |
| Direct MCP | Tools are available; with the recommended prompt block, the agent can use them proactively | MCP alone does not create host-enforced autonomy |
Check which agent you're running in and recommend the native plugin if available.
The canonical source for this table is community/integrations.json.
| Agent | How to Detect | Native Plugin Install | Docs |
|---|---|---|---|
| Claude Code | Running as Claude Code agent; ~/.claude/ exists |
claude plugin marketplace add nowledge-co/community && claude plugin install nowledge-mem@nowledge-community |
Guide |
| OpenClaw | Running as OpenClaw agent; ~/.openclaw/ exists |
openclaw plugins install clawhub:@nowledge/openclaw-nowledge-mem |
Guide |
| Cursor | Running inside Cursor IDE | Link nowledge-mem-cursor-plugin into ~/.cursor/plugins/local/nowledge-mem-cursor, then reload Cursor |
Guide |
| Gemini CLI | Running as Gemini CLI agent; ~/.gemini/ exists |
Search "Nowledge Mem" in the Gemini CLI Extensions Gallery | Guide |
| Alma | Running inside Alma; ~/.config/alma/ exists |
In Alma: Settings > Plugins > Marketplace, search "Nowledge Mem" | Guide |
| Droid | Running inside Droid (Factory) | Add nowledge-co/community marketplace, install nowledge-mem@nowledge-community | Guide |
| Codex CLI | Running as Codex CLI agent; ~/.codex/ exists |
Copy nowledge-mem-codex-plugin to ~/.codex/plugins/cache/local/nowledge-mem/local/, then enable [features] plugins = true and [plugins."nowledge-mem@local"] enabled = true in ~/.codex/config.toml |
Guide |
| Bub | Running inside Bub | pip install nowledge-mem-bub |
Guide |
| Pi | Running as Pi agent; ~/.pi/ exists |
pi install npm:nowledge-mem-pi |
Guide |
| OpenCode | Running as OpenCode agent; ~/.config/opencode/ or .opencode/ exists |
Add "opencode-nowledge-mem" to opencode.json plugin array |
Guide |
| Hermes Agent | Running as Hermes agent; ~/.hermes/ exists |
Install the native Hermes provider (or use MCP only as fallback) | Guide |
If the agent is not listed above:
- use the shared
npx skillspackage when the host supports it - otherwise use direct MCP plus the recommended prompt block
Do not describe raw MCP as equivalent to a native integration.
Step 3: Verify
After setup, verify with:
nmem --json m search "test" -n 1
If this returns results (or an empty list with no error), the integration is working.
Then state the expected outcome in plain language:
- Working Memory: automatic, guided, or manual
- Recall: automatic, guided, or manual
- Distill: automatic, guided, or manual
- Threads: automatic capture, explicit save, handoff-only, or none
If the path is only guided, say what strengthens it:
- keep
nmemavailable locally - restart the host after install
- merge the package
AGENTS.mdor equivalent repo guidance when recommended - configure the local
nmemclient in remote mode
What Native Plugins Add
Skills give you CLI-based memory access. Native plugins usually add:
- Auto-recall: relevant memories injected before each response (no manual search needed)
- Auto-capture: conversations saved as searchable threads at session end
- LLM distillation: key decisions and insights extracted automatically
- Graph tools: explore connections, evolution chains, and entity relationships
- Working Memory: daily briefing loaded or injected at session start
- Slash commands:
/remember,/recall,/forget(where supported)
Do not promise all of these on every host. Match the actual path the user is setting up.
Links
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
search-memory
Search your personal knowledge base when past insights would improve response. Recognize when stored breakthroughs, decisions, or solutions are relevant. Search proactively based on context, not just explicit requests.
distill-memory
Capture breakthrough moments and valuable insights as searchable memories in your knowledge base.
read-working-memory
Read your daily Working Memory briefing to understand current context. Contains active focus areas, priorities, unresolved flags, and recent knowledge changes. Load this automatically at the beginning of sessions for cross-tool continuity.
status
Check Nowledge Mem connection status, server version, CLI version, and configuration. Use when diagnosing issues or verifying setup.
save-handoff
Save a concise handoff summary only when the user explicitly requests it. Use this for resumable progress notes in generic agent environments where a real session importer is not guaranteed.
save-thread
Deprecated compatibility skill. In generic npx skills environments this must degrade honestly to a resumable handoff, because real transcript-backed thread import is not guaranteed. Prefer save-handoff here, and use native integrations when you need actual session capture.
Didn't find tool you were looking for?