OpenParable
Skip to content
← Back to skills

Wiki Query

Research
wiki-query

Wiki Query is an Agent Skill for research published in the paperclipai/paperclip repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/paperclipai/paperclip/blob/HEAD/packages/plugins/plugin-llm-wiki/skills/wiki-query/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/wiki-query, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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

  1. Open the target space's wiki/index.md first — it is the navigation aid. Identify candidate pages.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.