12 published skills
- ▌ Nowledge Mem Docker · nowledge-coInstall, check on, or upgrade a self-hosted Nowledge Mem server (the headless Docker deployment) using the `nmemctl` lifecycle controller. Use this whenever the user mentions running their own Nowledge Mem instance, self-hosting Mem on a NAS, VPS, homelab, or server, deploying `nowledgelabs/mem` from Docker Hub, troubleshooting their Mem container, or upgrading a Mem server to a newer version. Trigger even when the user says "my Mem server", "self-hosted Mem", "the docker version of Mem", "memory server on my Synology / Proxmox / Raspberry Pi", or just describes a container that's at `docker.io/nowledgelabs/mem` without naming the product. Do NOT trigger for the Mem desktop app, Mem Cloud, or anything that doesn't touch the operator's own server.
- ▌ Status · nowledge-coCheck Nowledge Mem connection status, server version, CLI version, and configuration. Use when diagnosing issues or verifying setup.
- ▌ Save Thread · nowledge-coDeprecated 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 connectors when you need actual session capture.
- ▌ Nowledge Mem · nowledge-coCross-tool knowledge for Amp. Read startup Context Bundle, search past decisions and conversations, save durable insights, and capture sessions as searchable threads with Nowledge Mem.
- ▌ Save Handoff · nowledge-coSave 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.
- ▌ Search Memory · nowledge-coSearch 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 · nowledge-coCapture breakthrough moments and valuable insights as searchable memories in your knowledge base.
- ▌ Working Memory · nowledge-coLoad cross-tool Nowledge context at session start. Shows current work, priorities, and unresolved flags. Codex local Memory is separate and does not replace this context; also trigger when resuming or when the user asks what am I working on.
- ▌ Check Integration · nowledge-coCheck Nowledge Mem setup, detect your agent, and guide native connector setup. Use when the user asks about setup, configuration, or when memory tools aren't working as expected.
- ▌ Nowledge Mem Guide · nowledge-coCross-AI personal knowledge graph memory (Nowledge Mem). Stores memories from this tool, Claude Code, Cursor, browser capture, imported documents, and more. Use when: (1) the user asks about prior work, decisions, preferences, people, dates, plans, or todos, (2) the user references something discussed before or says "remind me" / "what did we decide" / "what was I working on", (3) the conversation produces a decision, preference, plan, or learning worth keeping, (4) the user wants to browse recent activity or explore how ideas connect, (5) the user asks about a past conversation or wants to find a specific thread.
- ▌ Read Working Memory · nowledge-coRead 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.
- ▌ Browse Now · nowledge-coControl the user's actual browser through the browse-now CLI when a task needs authenticated pages, dynamic interaction, form filling, screenshots, or other browser automation that web search cannot reach. Prefer it whenever the task depends on the user's real browser state rather than a generic fetch.