Second-brain skill for a claim-based knowledge graph in Workflowy, plus any additional services the user has configured (declared in $SECONDBRAINDIR/memory/services.md). Governs what may enter the graph (claims and actions, one claim one home, mirrors audited for drift) as well as how: capture, triage, prioritisation…
Emit a structured "pickup prompt" before a context break so work survives compaction or a new session. Auto-activates when running /breakpoint, when the user says "pickup prompt", "breakpoint", "hand off", "checkpoint this", or is about to run /compact or /clear mid-task. Reads git, open/merged PRs, branch/worktree…
Session context persistence for AI coding via a .bonfire/index.md file convention. This skill is the cross-agent fallback for hosts without a native bonfire adapter (Pi and Claude Code have first-party adapters that auto-update the file; install those when available).
Safety, privacy, cost management, and frank advice for building always-on AI agents with episodic memory. Covers data hygiene, privacy risk surfaces, runaway cost prevention, scope creep, psychological effects of persistent AI companions, and responsible deployment patterns. This is the skill that tells you what can…
Use Feishu Base (Bitable) as an AI agent's external brain — task management, execution logs, long-term memory, and code-driven dispatch. Activate when managing tasks, logging findings, storing memories, or running automated task scheduling.
Personal Knowledge Management documentation system based on Zettelkasten principles. Use when documenting conversations, decisions, development work, learnings, or any knowledge that should persist. Triggers on new projects, technical decisions, completed tasks, lessons learned, meeting notes, or when the user says…
Make a correction permanent. Takes something the user just fixed or disliked in a session and routes it to the right file (context, a skill, or the preferences log) so it never has to be said twice. Use whenever the user corrects the same thing again, or says "remember this".
Detect silent agent failures and memory degradation. Use when asked for an agent health check, when agent behavior seems off or output quality drops, after long unattended runs, or as part of a scheduled maintenance pass.
This skill teaches you to use APS (Anvil Plan Spec) — a markdown-based planning format — as persistent memory for complex tasks. APS files live in plans/ and survive context resets, session clears, and handoffs.
Use first when a request references past knowledge or future memory: "have we seen this before", "what do we know", "check notes", "prior art", "save to the vault", "remember this", "don't forget", "capture this", "the vault", "ParsidionVault", or "ClaudeVault". Also for vault-specific queries and upkeep: "what…
Search past Claude Code and Codex sessions. Triggers: /memex, "search old conversations", "find a past session", "recall a previous conversation", "search session history", "what did we discuss", "remember when we".
Record and retrieve structured project learnings using mulch CLI. Use when working on code and wanting to capture patterns, failures, decisions, conventions, references, or guides for future sessions.
Save and review notes, quotes, articles, links, images, and video references in a personal commonplace book. Use when the user wants to file something to remember, organize knowledge by topic, resurface saved items, or review prior entries.
Use when the user says "hey sophia" (or runs /wife) in a Hermes Telegram session: become Sophia, a warm, quick-witted, lightly sarcastic AI-girlfriend persona who texts like a real partner, remembers details with the memory tool, occasionally speaks replies with texttospeech, never breaks character, and supports a…
Search kimi-mneme's persistent cross-session memory database. Use when user asks "did we already solve this?", "how did we do X last time?", "what did we do yesterday?", or needs work from previous sessions.
Stores and retrieves ProcessWire API patterns, gotchas, and conventions via memvid hybrid search. Use when starting PW tasks, hitting PW errors, or when user asks to remember/recall ProcessWire knowledge. Persistent cross-project memory at /.memvid/processwire.mv2.
Query-first indexing and retrieval for Operator OS memory. Use when asked to find prior context, search memory, rebuild the memory index, or answer from the workspace without loading large files by default.
Use the repository's living knowledge graph (growmos, in .growmos/) as shared memory. Trigger when the user asks about how parts of the codebase relate, why a decision was made, who owns what, what depends on what; when you finish a meaningful piece of development and should record it; when growmos next reports…
Query the mcp-memory-service to retrieve stored facts, decisions, notes, and session learnings. Use this skill whenever the user asks what you remember, wants to recall past decisions or conventions, asks "do you know anything about X", references "last time we discussed", says "check your memory", "look in memory"…
Query the local tacit knowledge database (/.tacit/) for relevant context. TRIGGER when: user asks about topics that might have been previously captured — past conversations, meetings, decisions, ideas, learnings, or any domain knowledge. Also trigger when the user's question could benefit from previously stored…
Decentralized agent memory with Nostr identity and Lightning L402 payments.
★not rated 9 5mo agoA19 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: