How do I install the Llmwiki Query skill?

Run npx skillmds@latest add pratiyush/llmwiki-query 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 Llmwiki Query 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 Llmwiki Query?

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 Llmwiki Query free to use?

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

Who published Llmwiki Query?

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

Llmwiki Query by pratiyush — Agent Skill

Name: Llmwiki Query
Author: pratiyush

Llmwiki Query

Answer a question by querying the user's llmwiki. Use when the user asks about their own past work — "what did I decide about X", "what have I been working on", "how did I solve Y", "what's my preferred approach to Z", or any question that the wiki (built from their session history) might answer. Always read the wiki first before falling back to external search.

pratiyush 17fa3ef 2.7 KB Updated Sep 17, 2026

File contents

llmwiki-query

What this skill does

Reads the user's local llmwiki (llmwiki/wiki/) and synthesises an answer to their question, with [[wikilink]] citations pointing to the source pages.

When to use

Invoke this skill when the user asks a question about their own work or history. Examples:

"What did I decide about the AiShorts backend?"
"What MCP servers do I have configured?"
"How did I fix the X bug last week?"
"What's my preferred way to ingest sessions?"
"What have I been working on in the germanly project?"

Do NOT invoke for questions that can be answered without the user's personal knowledge base (e.g., "how does TCP work?" → answer from general knowledge).

Workflow

Follow the Query Workflow from the repo's CLAUDE.md:

Locate the llmwiki install (see llmwiki-sync skill for the fallback search order).
Read wiki/index.md to identify the set of pages that might be relevant.
Read wiki/overview.md to get the living synthesis context.
Pick the most relevant pages (sources, entities, concepts) based on the question.
Read those pages with the Read tool.
Synthesise an answer with inline [[wikilink]] citations. Quote directly from source pages when the wording matters.
If the answer is substantial (3+ paragraphs), ask the user whether to save it as a synthesis page:
```
Would you like me to save this as wiki/syntheses/<slug>.md for future reference?
```
If yes, write it using the Synthesis Page Format from CLAUDE.md.

Append to wiki/log.md:

## [YYYY-MM-DD] query | <short question>

Fallback behavior

If the wiki has no relevant pages:

Tell the user "I don't see anything about this in your wiki yet."
Suggest running /wiki-sync to pull in any recent sessions that might cover the topic.
If the topic is unlikely to be in session history, offer to answer from general knowledge (and make that explicit: "this is general knowledge, not from your wiki").

Don't do

Don't make up wiki pages that don't exist.
Don't confuse general knowledge with wiki content in the answer.
Don't over-cite — if the whole answer comes from one page, cite once at the top.
Don't write a wall of text. The answer should be as short as the question allows.

---name: llmwiki-querydescription: Answer a question by querying the user's llmwiki. Use when the user asks about their own past work — "what did I decide about X", "what have I been working on", "how did I solve Y", "what's my preferred approach to Z", or any question that the wiki (built from their session history) might answer. Always read the wiki first before falling back to external search.---# llmwiki-query## What this skill doesReads the user's local llmwiki (`llmwiki/wiki/`) and synthesises an answer to their question, with `[[wikilink]]` citations pointing to the source pages.## When to useInvoke this skill when the user asks a question about their own work or history. Examples:- "What did I decide about the AiShorts backend?"- "What MCP servers do I have configured?"- "How did I fix the X bug last week?"- "What's my preferred way to ingest sessions?"- "What have I been working on in the germanly project?"Do NOT invoke for questions that can be answered without the user's personal knowledge base (e.g., "how does TCP work?" → answer from general knowledge).## WorkflowFollow the **Query Workflow** from the repo's `CLAUDE.md`:1. **Locate the llmwiki install** (see `llmwiki-sync` skill for the fallback search order).2. **Read `wiki/index.md`** to identify the set of pages that might be relevant.3. **Read `wiki/overview.md`** to get the living synthesis context.4. **Pick the most relevant pages** (sources, entities, concepts) based on the question.5. **Read those pages** with the Read tool.6. **Synthesise an answer** with inline `[[wikilink]]` citations. Quote directly from source pages when the wording matters.7. **If the answer is substantial** (3+ paragraphs), ask the user whether to save it as a synthesis page: ```markdown Would you like me to save this as wiki/syntheses/<slug>.md for future reference? ``` If yes, write it using the Synthesis Page Format from CLAUDE.md.8. **Append to `wiki/log.md`**: ``` ## [YYYY-MM-DD] query | <short question> ```## Fallback behaviorIf the wiki has no relevant pages:1. Tell the user "I don't see anything about this in your wiki yet."2. Suggest running `/wiki-sync` to pull in any recent sessions that might cover the topic.3. If the topic is unlikely to be in session history, offer to answer from general knowledge (and make that explicit: "this is general knowledge, not from your wiki").## Don't do- Don't make up wiki pages that don't exist.- Don't confuse general knowledge with wiki content in the answer.- Don't over-cite — if the whole answer comes from one page, cite once at the top.- Don't write a wall of text. The answer should be as short as the question allows.

Frequently asked questions