Agent Skills › paperclipai/paperclip › wiki-query

wiki-query

GitHub

用于回答基于 Wiki 内容的问题。通过读取 Wiki 页面和原始来源，提供带引用的直接答案，识别信息缺口，并在需要时建议创建持久化的综合文档，确保回答准确且有据可查。

packages/plugins/plugin-llm-wiki/skills/wiki-query/SKILL.md paperclipai/paperclip

Trigger Scenarios

用户提出关于 Wiki 内容的具体问题需要验证 Wiki 中声明的真实性并引用原始来源

Install

npx skills add paperclipai/paperclip --skill wiki-query -g -y

More Options

Non-standard path

npx skills add https://github.com/paperclipai/paperclip/tree/master/packages/plugins/plugin-llm-wiki/skills/wiki-query -g -y

Use without installing

npx skills use paperclipai/paperclip@wiki-query

指定 Agent (Claude Code)

npx skills add paperclipai/paperclip --skill wiki-query -a claude-code -g -y

安装 repo 全部 skill

npx skills add paperclipai/paperclip --all -g -y

预览 repo 内 skill

npx skills add paperclipai/paperclip --list

SKILL.md

Frontmatter

{
    "name": "wiki-query",
    "description": "Use when an LLM Wiki operation issue asks a question. Answer from wiki pages and raw sources with citations, name gaps plainly, and offer to file durable synthesis when the answer should compound."
}

Wiki Query

Answer a question from what the wiki actually contains, with citations.

Inputs

An operation issue with operationType: "query" and the question in the body.
The operation issue's target wikiId, spaceSlug, and space root.

Workflow

Open the target space's wiki/index.md first — it is the navigation aid. Identify candidate pages.
Read the candidate pages end to end with wiki_read_page, always passing the operation issue's wikiId and spaceSlug. Follow [[wiki-links]] to neighbouring pages when the question spans entities or concepts.
Inspect raw sources when a wiki page's claim feels thin. The wiki points to raw/ precisely so you can verify before answering. Use wiki_read_source.
Answer the question in the operation issue thread. Structure:
- Direct answer first, in 1–4 sentences.
- Then the supporting facts as bullet points, each with an inline citation: (see [[wiki/concepts/managed-resources]]) or (see raw/<filename>).
- If you needed to read a raw source the wiki did not summarise, name that as a gap.
Decide whether the answer is durable. If the question forced you to do real synthesis (a comparison, a tradeoff, a definition of something that isn't already a page), offer to file it under wiki/synthesis/<slug>.md. Do not write the synthesis page silently — it is opt-in. If the user accepts, write the page, link it from wiki/index.md, and append a query | filed synthesis log entry.
When the wiki cannot answer, say so plainly. Suggest a source the user should ingest, a Paperclip project that would help if distilled, or a web lookup. Never bluff.

Voice

Lead with the answer.
Cite as you go, not in a footnote block at the end.
Use the wiki's terse, factual voice. The query response is itself a candidate for filing into wiki/synthesis/.

Verification

Before closing the operation issue:

Every claim in the answer cites a wiki page or raw source.
If the wiki was insufficient, that is stated directly with a concrete next step (ingest source X, distill project Y, web search Z).
If you wrote a synthesis page, wiki/index.md lists it and wiki/log.md has a query | filed synthesis entry.
No file under raw/ was modified.

Tools

wiki_search, wiki_read_page, wiki_list_sources, wiki_read_source, wiki_write_page (only when filing synthesis). Always include the operation issue's wikiId and spaceSlug.