Knowledge Agent Skill for Claude
Build and query AI-powered knowledge bases from claude-mem observations. Use when users want to create focused "brains" from their observation history, ask questions about past work patterns, or compile expertise on specific topics.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/thedotmack/claude-mem --skill knowledge-agentThe instruction itself
11 sections, as written by the authorKnowledge 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
build_corpus name="hooks-expertise" description="Everything about the hooks lifecycle" project="claude-mem" concepts="hooks" limit=500
Filter options:
project— filter by project nametypes— comma-separated: decision, bugfix, feature, refactor, discovery, changeconcepts— comma-separated concept tagsfiles— comma-separated file paths (prefix match)query— semantic search querydateStart/dateEnd— ISO date rangelimit— max observations (default 500)
Step 2: Prime the corpus
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
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
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)
rebuild_corpus name="hooks-expertise"
After rebuilding, reprime to load the updated knowledge:
Reprime (fresh session)
reprime_corpus name="hooks-expertise"
Clears prior Q&A context and reloads the corpus into a new session.
Other skills for the same job
different authors, same section of the catalogue
This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable. Documents the .claude/plugin-name.local.md pattern for storing plugin-specific configuration with YAML frontmatter and markdown content.
-Automatically convert documentation websites, GitHub repositories, and PDFs into Claude AI skills in minutes.
This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable. Documents the .claude/plugin-name.local.md pattern for storing plugin-specific configuration with YAML frontmatter and markdown content.
Standardize how an AI-collaboration project turns work into reusable knowledge. Use when initializing or retrofitting Project Cairn in a project, recording progress after meaningful work, maintaining AGENTS/CLAUDE/cairn docs, auditing project knowledge for drift or missing records, pulling and citing external knowledge, or graduating validated project experience into a reusable knowledge base.
Persistent memory and context management for AI agents using OpenContext. Keep context across sessions/repos/dates, store conclusions, and provide document search workflows.
> PARA method knowledge management for Obsidian vaults. Use this skill whenever the user wants to organize notes using PARA (Projects, Areas, Resources, Archive), classify a note into a PARA category, route a note to the right vault folder, normalize frontmatter fields, run a PARA hygiene review, suggest archiving, audit vault structure, or process new knowledge inputs into an existing PARA-based vault. Also trigger when the user mentions inbox processing, vault cleanup, note classification, PARA review, or asks "where does this note belong?". Works with existing Obsidian skills (obsidian-markdown, obsidian-cli) — never replaces them.
Keeps implementation and specs in sync. Use when working on a feature that has a spec in .agents/specs/, when the user says /spec, or when starting implementation of a documented feature. Also use when the user asks to verify implementation against a spec or update a spec after changes.
(builtin) Initialize hierarchical AGENTS.md knowledge base
How to use it
Take thedotmack/knowledge-agent from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.