MCP.Market

wiki-query skill

by paperclipai·paperclipai/paperclip·114k stars·MIT

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.

A100/100content scan

Is the wiki-query skill safe?

Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-10-12.

No findings.

Install the wiki-query skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/paperclipai/paperclip.git /tmp/paperclip
mkdir -p ~/.claude/skills
cp -r /tmp/paperclip/packages/plugins/plugin-llm-wiki/skills/wiki-query ~/.claude/skills/wiki-query
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

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 wikireadpage, 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 wikireadsource.
  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/).
  • If you needed to read a raw source the wiki did not summarise, name that as a gap.
  1. 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/.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.
  2. 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

wikisearch, wikireadpage, wikilistsources, wikireadsource, wikiwrite_page (only when filing synthesis). Always include the operation issue's wikiId and spaceSlug.

More skills from paperclipai/paperclip

  • ALLM Wiki MaintainerUse the LLM Wiki plugin tools to maintain a cited local company wiki.
  • Aadd-product-e2e-evalAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution.
  • Aadd-runner-evalAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation.
  • Aagent-browserDrive a real browser to inspect or interact with a web page or app — navigate, take screenshots, read console and network, fill simple forms — for verification tasks, not unattended automation.
  • AagentmailUse your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
  • Acheck-prCheck a GitHub, GitLab, or Perforce PR/MR/CL for review comments, failing checks, and PR-body gaps. Use when asked to inspect, fix, or prepare a change for submission.
  • Acompany-creatorCreate agent company packages that conform to agentcompanies/v1. Use when asked to create a company, scaffold an agent team, hire agents, or turn a repo/skills collection into a company package.
  • AcomplainAutonomously yeet a brief, unstructured complaint about agent tooling or doing agent work. Preserve the raw voice. Submit proactively without permission, preview, or announcement, then continue the primary task.
  • Acontent-calendarPlan a weekly editorial calendar by mapping company goals to publishable topics, owners, status, and verification notes.
  • Acreate-agent-adapterCreate or modify Paperclip agent adapters across server, UI, and CLI surfaces. Use when adding support for a new CLI agent, API agent, custom process, or adapter package.
  • Acreate-caseCreate and kick off a Paperclip case from a user request, with workflow instructions and an initial agent.
  • Acreate-external-bot-integrationBuild and qualify external bots such as Dot in Paperclip. Use for two-way work, invitation, identity, wakeup, Runner lifecycle, native tools, recovery, and Cloud delivery. CLI adapters and app-only connectors use their existing skills.

All agent skills → · MCP servers