knowledge-agent
The knowledge-agent skill lets users create filtered collections of observations from claude-mem and query them conversationally through an AI-powered session. Use it when you need to extract focused expertise from your observation history, such as compiling all decisions from a time period, gathering everything about a specific technical topic, or asking questions about past work patterns without manually searching through raw notes.
git clone --depth 1 https://github.com/thedotmack/claude-mem /tmp/knowledge-agent && cp -r /tmp/knowledge-agent/plugin/skills/knowledge-agent ~/.claude/skills/knowledge-agentSKILL.md
# Knowledge Agent Build and query AI-powered knowledge bases from claude-mem observations. ## What Are Knowledge Agents? Knowledge agents are filtered corpora of observations compiled into a conversational AI session. Build a corpus from your observation history, prime it (loads the knowledge into an AI session), then ask it questions conversationally. Think of them as custom "brains": "everything about hooks", "all decisions from the last month", "all bugfixes for the worker service". ## Workflow ### Step 1: Build a corpus ```text build_corpus name="hooks-expertise" description="Everything about the hooks lifecycle" project="claude-mem" concepts="hooks" limit=500 ``` Filter options: - `project` — filter by project name - `types` — comma-separated: decision, bugfix, feature, refactor, discovery, change - `concepts` — comma-separated concept tags - `files` — comma-separated file paths (prefix match) - `query` — semantic search query - `dateStart` / `dateEnd` — ISO date range - `limit` — max observations (default 500) ### Step 2: Prime the corpus ```text prime_corpus name="hooks-expertise" ``` This creates an AI session loaded with all the corpus knowledge. Takes a moment for large corpora. ### Step 3: Query ```text query_corpus name="hooks-expertise" question="What are the 5 lifecycle hooks and when does each fire?" ``` The knowledge agent answers from its corpus. Follow-up questions maintain context. ### Step 4: List corpora ```text list_corpora ``` Shows all corpora with stats and priming status. ## Tips - **Focused corpora work best** — "hooks architecture" beats "everything ever" - **Prime once, query many times** — the session persists across queries - **Reprime for fresh context** — if the conversation drifts, reprime to reset - **Rebuild to update** — when new observations are added, rebuild then reprime ## Maintenance ### Rebuild a corpus (refresh with new observations) ```text rebuild_corpus name="hooks-expertise" ``` After rebuilding, reprime to load the updated knowledge: ### Reprime (fresh session) ```text reprime_corpus name="hooks-expertise" ``` Clears prior Q&A context and reloads the corpus into a new session.
Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.
Audit a design against Dieter Rams' ten "Good design is..." principles, then hand off a /make-plan prompt for one of three outcomes — new design, refine design, or redesign. Use when the user says "audit this design", "design review", "check this UI against Rams", "is this UI good", "critique this design", "design audit", or asks for a critique that should lead to a plan.
Execute a phased implementation plan using subagents. Use when asked to execute, run, or carry out a plan — especially one created by make-plan.
Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".
Prime a codebase by reading every source file in full. Use when starting work on a new or unfamiliar project, or when the user asks to "learn the codebase", "read the codebase", "prime", or "get up to speed".
Create a detailed, phased implementation plan with documentation discovery. Use when asked to plan a feature, task, or multi-step implementation — especially before executing with do.
Search claude-mem's persistent cross-session memory database. Use when user asks "did we already solve this?", "how did we do X last time?", or needs work from previous sessions.