How do I install the Knowledge skill?

Run npx skillmds@latest add guaardvark/knowledge in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Knowledge safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Knowledge?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Knowledge free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Knowledge?

guaardvark (@guaardvark) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Knowledge by guaardvark — Agent Skill

Name: Knowledge
Author: guaardvark

Knowledge

Answer from the user's own indexed documents with Guaardvark's local RAG, browse and read indexed files section by section, remember facts across sessions, and process or fetch new material. Use when the user asks what their documents say, wants a source-cited answer from their files, says "remember this", or asks to index a PDF, DOCX, spreadsheet, image or URL.

guaardvark Updated Sep 21, 2026

File contents

Knowledge with Guaardvark (MCP tools)

Everything here is the guaardvark MCP server. All retrieval is local (Ollama embeddings, hybrid search, cross-encoder reranking on the user's GPU).

Find and read

tool	use
`search_knowledge_base`	the question in plain words; returns passages with sources. Cite them.
`summarize_corpus`	what the whole knowledge base covers, before searching blind
`list_documents`	which documents are indexed and how many passages each has
`get_document_outline`	sections or pages of one document, in order
`read_document_section`	the actual text of one section or page, no search
`process_file`	extract content from a PDF, DOCX, CSV, Excel, image or other file the user names
`fetch_url`	title, description and main text of one web page; pass `query` (the user's question) to get the passage about it instead of the top of the page
`web_search`	DuckDuckGo results (titles, snippets, URLs) when the answer is not local

Pattern: summarize_corpus or list_documents → search_knowledge_base → read the exact section with get_document_outline + read_document_section before quoting.

Remember

save_memory: a fact, preference or instruction to keep across sessions. Use when the user says "remember", or states a durable preference. One fact per call.
search_memory: check before assuming; recalled memories are what was true when saved.
Forgetting: delete_memory is not exposed by this server by default, because it deletes. Find the memory with search_memory, then delete it with DELETE /api/memory/<id> on the backend. An operator who wants the tool over MCP adds delete_memory to server.tools.allow in data/config/mcp.json.

Rules

Quote the source (document name and section) for any claim that came from retrieval.
If retrieval returns nothing, say so; do not fill the gap from general knowledge without labelling it.
Indexing new folders happens in the Studio's Library page; the MCP server reads what is indexed.

---name: knowledgedescription: Answer from the user's own indexed documents with Guaardvark's local RAG, browse and read indexed files section by section, remember facts across sessions, and process or fetch new material. Use when the user asks what their documents say, wants a source-cited answer from their files, says "remember this", or asks to index a PDF, DOCX, spreadsheet, image or URL.---# Knowledge with Guaardvark (MCP tools)Everything here is the `guaardvark` MCP server. All retrieval is local (Ollama embeddings,hybrid search, cross-encoder reranking on the user's GPU).## Find and read| tool | use ||---|---|| `search_knowledge_base` | the question in plain words; returns passages with sources. Cite them. || `summarize_corpus` | what the whole knowledge base covers, before searching blind || `list_documents` | which documents are indexed and how many passages each has || `get_document_outline` | sections or pages of one document, in order || `read_document_section` | the actual text of one section or page, no search || `process_file` | extract content from a PDF, DOCX, CSV, Excel, image or other file the user names || `fetch_url` | title, description and main text of one web page; pass `query` (the user's question) to get the passage about it instead of the top of the page || `web_search` | DuckDuckGo results (titles, snippets, URLs) when the answer is not local |Pattern: `summarize_corpus` or `list_documents` → `search_knowledge_base` → read the exactsection with `get_document_outline` + `read_document_section` before quoting.## Remember- `save_memory`: a fact, preference or instruction to keep across sessions. Use when the user says "remember", or states a durable preference. One fact per call.- `search_memory`: check before assuming; recalled memories are what was true when saved.- Forgetting: `delete_memory` is not exposed by this server by default, because it deletes. Find the memory with `search_memory`, then delete it with `DELETE /api/memory/<id>` on the backend. An operator who wants the tool over MCP adds `delete_memory` to `server.tools.allow` in `data/config/mcp.json`.## Rules- Quote the source (document name and section) for any claim that came from retrieval.- If retrieval returns nothing, say so; do not fill the gap from general knowledge without labelling it.- Indexing new folders happens in the Studio's Library page; the MCP server reads what is indexed.

Frequently asked questions