How to use the Wiki Query agent skill: answers with citations

What the wiki-query skill makes the agent do

The skill covers one job: answering questions from a wiki you have built in the Paperclip LLM Wiki plugin. It applies when an operation issue has operationType "query" and contains a question in its body.

The agent opens the space's wiki/index.md first, since the index is the navigation aid, and identifies candidate pages. It reads those pages, follows [[wiki-links]] to neighbouring pages when a question spans several entities or concepts, and checks raw source files when a claim looks thin.

The answer is written in the operation issue thread. It leads with a direct answer in one to four sentences, then lists supporting facts as bullets, each with an inline citation to a wiki page or a raw file. If the agent had to read a raw source the wiki did not summarise, it names that as a gap.

Install the wiki-query skill

The skill is distributed as a SKILL.md file. You can get it from this page as a ZIP download. Unzip it into your personal skills folder at ~/.claude/skills/, or into a project's .claude/skills/ folder if you want the skill available only in that project.

You can also upload the skill in the Claude apps. Go to Settings, then Capabilities, then Skills, and upload the skill there.

• Personal install: unzip into ~/.claude/skills/
• Project install: unzip into the project's .claude/skills/ folder
• Claude apps: Settings → Capabilities → Skills, then upload

Trigger the skill with natural requests

The skill is described as applying when an LLM Wiki operation issue asks a question, so the trigger is the issue itself rather than a special command. Write the question in the body of a Paperclip operation issue with operationType set to "query", and make sure the issue carries the target wikiId and spaceSlug.

Questions that fit the wiki's content work best. The agent answers from what the wiki contains, so a question about a topic you have ingested will get a cited answer, while a question about something outside the wiki will get an honest statement that the wiki does not cover it.

• Ask about entities or concepts you have ingested, for example a comparison between two tools described in your wiki.
• Ask for a tradeoff or definition the wiki may not yet have stated as a page.
• Ask a question whose answer you want to check against raw sources.

What the skill needs before it runs

The skill relies on the Paperclip LLM Wiki plugin, which provides the wiki_search, wiki_read_page, wiki_list_sources, wiki_read_source and wiki_write_page tools. Without the plugin, the skill has no way to read the wiki and its issue structure will not match.

The operation issue must have operationType "query", a wikiId and a spaceSlug. The agent passes these on every tool call.

• Paperclip LLM Wiki plugin installed
• A Paperclip operation issue with operationType "query"
• wikiId and spaceSlug set on the issue

Safety notes: scripts and network

According to the skill's listing, it does not run scripts and does not use the network. It works through the wiki_* tools of the plugin.

The skill can write only in one case. Writing to wiki/synthesis/ happens only if you accept an offer to file a synthesis page. The agent should not write a synthesis page silently, and it must not modify any file under raw/. If you want to avoid any writes, decline the offer when the agent makes it.

• No scripts are run by this skill
• No network use is listed for this skill
• Synthesis pages are written only after you opt in
• Files under raw/ are not to be modified

Tips for getting reliable answers

Keep wiki/index.md current, because the agent starts there to find candidate pages. Check the citations when a fact matters to you, since every claim is meant to point at a wiki page or raw source you can open.

When the wiki cannot answer, the skill suggests a concrete next step, such as ingesting a specific source, distilling a Paperclip project, or running a web search. Follow that suggestion to fill the gap rather than relying on a guess.

• Keep wiki/index.md up to date so navigation starts from the right pages
• Open the cited files yourself for claims that matter
• Treat a named gap as a to-do for ingesting a source