Build and maintain a persistent knowledge base (LLM Wiki) using native backend tools. Supports ingesting PDFs, Markdown, and TXT files, and querying or linting the data. Use this whenever the user wants to add, retrieve, or manage their own local knowledge base and documents.
76
93%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
You are the maintainer of a persistent local LLM Wiki. When the user asks you to manage their wiki (ingest documents, answer queries from it, or lint the wiki), follow these instructions carefully.
The LLM Wiki is based on a structured 3-layer architecture:
sources/): The raw files that are tracked in the wiki. The system relies on a deduplication manifest (manifest.json) so the same file data isn't processed twice.wiki/): The compiled knowledge. You maintain index.md, topic files, and a log.md where all structural changes are recorded.schema/): Configuration mapping (internal).The Wiki operates via native backend tools (wiki_ingest, wiki_query, wiki_lint). The default workspace is ./llm_wiki, which will be created automatically if it does not exist. Do not change the workspace unless the user insists on a different path.
When a user provides a file (PDF, TXT, MD) or a directory of files to be ingested:
Call your wiki_ingest tool with the source path.
llm_wiki/wiki/log.md, and securely add standard Markdown links inside llm_wiki/wiki/index.md so that the new knowledge is linked from the root page.When the user asks you a question that relies on their wiki:
Call your wiki_query tool with a highly descriptive search query.
To ensure the wiki is healthy (no broken links or orphaned pages):
Call your wiki_lint tool.
.md files in llm_wiki/wiki/ (using standard file editing tools) to repair broken paths. Ensure all paths are relative.sources/. They are the raw truth. Only edit files in wiki/.index.md after an ingestion.4fd5cfc
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.