Use when the user refers to previous decisions, corrections, forgotten context, already-built work, install/test/release status, source-backed evidence, or next steps in ongoing work. Treat Time Library as a standing active memory routing rule: call timelibraryrecall before answering memory-dependent prompts. Also…
A front-door routing skill for HMA, a long-term memory system. It first identifies what a submitted text or file is, then sends it to the matching storage workflow.
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community…
Format and validate Obsidian wiki links with proper filename, section, and folder conventions. Verify links exist before creation and fix broken links. Use when creating or checking wiki links in markdown files.
File experiment results to the wiki following the SCHEMA Ingest procedure. Use after an experiment run produces metrics, ablations, or comparisons worth keeping as durable project memory.
Use when the user wants AI project memory, task documentation, decision records, bug history, feature notes, context recovery, or "document everything" behavior without forcing a project structure. This skill keeps engineering context recoverable and only creates project files when the user explicitly asks to…
Use this skill when the user wants to build a knowledge base for their project, create an Obsidian wiki from project data, analyze project structure for knowledge management, or mentions "obsidian-kb", "knowledge base", or "compile wiki".
Scaffold a personal LLM wiki (Karpathy pattern) — multi-agent, MCP-ready, with SEO/GEO publish target. Compiles knowledge into a persistent wiki instead of re-deriving from raw docs on every query. One paste from any agent (OpenClaw, Claude Code, Codex, Cursor, Hermes) installs it.
Persistent memory and task coordination for AI coding sessions. Creates a .fireteam/ folder with mission context, task state, checkpoints, and handoff notes that survive session restarts, context limits, and crashes. Use this skill whenever the user wants to set up a fireteam, continue a fireteam, resume after a…
A skill that stores a user's project decisions and constraints in mdbase, a persistent project knowledge store. The records can be reused across sessions and by different coding assistants.
Audits Claude Code context consumption across agents, skills, commands, hooks, MCP servers, and the CLAUDE.md/MEMORY chain. Identifies bloat and redundancy, then produces prioritized token-savings recommendations. Backs the /context-budget command.
Query and propose local knowledge cards for this repo. Always use at the start of work here — run npx knowcards query before acting. Also use when wrapping up if this session proved a durable repo fact that later work will reuse (at most 2 cards). Skip propose when nothing would change a later action. Skip query only…
A reference for using weasley-deepmind, a server that stores and retrieves an AI agent’s long-term memories between sessions. It describes memory storage, search, language processing, and related tools.
A Chinese-language local search tool for finding content in your own documents, code, images, saved web pages, and video dialogue. It can also index new files and find similar content.
Turns handwritten reMarkable notes into a queryable semantic memory. Syncs pages from a reMarkable tablet (via the reMarkable MCP server, rmapi, or a USB/SSH bridge), renders each page to an image and reads the handwriting with Claude vision — no OCR key — then extracts each page into confidence-scored, human-editable…
Give the agent episodic memory so it improves every cycle instead of repeating mistakes. Use this skill whenever working in a project that has a .loop/LESSONS.md file, whenever a task is being retried after a failure, whenever the user says "remember this", "don't make that mistake again", "learn from this", or "why…
Persistent project memory via AgentMemory MCP. Use when the user asks you to remember something, recall a project convention, search past context, or forget a memory. Always search before answering project-specific questions.
An interactive setup skill that turns an empty Claude Code folder into an OpenClaw-style personal assistant. It asks about the assistant's identity, tone, communication channels, permissions, and memory, then creates the related instruction and memory files.
Clip content from a URL into the knowledge base through browser automation. Use when the user sends a URL (for example a WeChat Official Account article link) and asks to clip, ingest, capture, or save it — even if the user says "ingest" followed by a URL, the URL means this must be clipped first. Also use when the…
Use when the user wants to capture, ingest, organize, query, or lint cross-project engineering experience or evidence-backed technical learning and AI-discussion conclusions in a configured Craft Wiki. Also use after a substantive approved architecture decision; verified development, performance, debugging, or review…
Use at the end of a session (or midway through a long one) to deliberately capture what was learned — lessons, decisions, workflows, state changes, and facts — into the knowledge base. The nightly harvest is a safety net for lessons; unless the host opted into KBHARVESTFACTS, /debrief is the only thing that records…
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: