MCP.Market

wiki-ingest skill

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

Use when an operation issue asks to ingest a captured `raw/` source into the LLM Wiki, or the user says "ingest <slug>". Create durable source, entity, concept, synthesis, index, and log pages; use paperclip-distill for Paperclip bundles.

A100/100content scan

Is the wiki-ingest 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-ingest 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-ingest ~/.claude/skills/wiki-ingest
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 Ingest

Turn one source document into durable, interlinked wiki knowledge.

Inputs

  • An operation issue with operationType: "ingest" assigned to you.
  • A raw/ path mentioned in the issue body (always treat raw/ as immutable).
  • The operation issue's target wikiId, spaceSlug, and space root (otherwise stop and surface the missing config to the requester).

Workflow

  1. Read context first.
  • Read the target space's AGENTS.md for page conventions (filenames, frontmatter, voice, citation style).
  • Read the target space's wiki/index.md to see what already exists.
  • Read the target space's last ~20 entries of wiki/log.md to avoid re-ingesting a source or re-resolving a contradiction someone else already filed.
  1. Read the source end to end with wikireadsource, passing the operation issue's wikiId and spaceSlug. Do not skim. Note the source's structure, claims, dates, and anything that contradicts existing pages.
  2. Plan, then confirm — but only if the user is in the loop. If the operation came from a routine (no live user), proceed. If a user is asking interactively, summarise the 3–5 takeaways you intend to file and ask which to emphasise before writing.
  3. Write the source page at wiki/sources/.md — ~300–800 words, frontmatter per the wiki schema, neutral voice, key claims with quoted excerpts where they carry weight. The source page is the canonical citation target for everything else this skill writes.
  4. Update or create downstream pages in entities/, concepts/, and synthesis/. A typical ingest touches 5–15 pages; resist creating pages for ideas that only appear once.
  5. Wire the cross-links. Every claim that comes from the source cites it as (see [[wiki/sources/]]). Every entity / concept mentioned by name on more than one page links to its dedicated page.
  6. Flag contradictions; do not silently overwrite. When new material disagrees with an existing page, append a > ⚠ contradicted by [[wiki/sources/]] (YYYY-MM-DD) callout to the older page and note the conflict in the log.
  7. Refresh wiki/index.md with one-line summaries for any new pages.
  8. Append a log entry in wiki/log.md:
## [YYYY-MM-DD] ingest | <source title>
   - source: raw/<filename>
   - new pages: [[...]], [[...]]
   - updated pages: [[...]], [[...]]
   - notes: <one-line synthesis or open question>

Voice

  • Terse, factual, neutral. Reference material, not narrative.
  • No "Today I learned" or "This is interesting because" framing.
  • Quote the source verbatim when paraphrasing would lose precision.

Verification

Before closing the operation issue:

  • [ ] Source page exists at wiki/sources/.md with valid frontmatter and a sources: field pointing to the raw path.
  • [ ] Every new or updated page links back to the source page or a downstream page that does.
  • [ ] wiki/index.md lists every new page under the right category with a one-line summary.
  • [ ] wiki/log.md has the ingest entry with the exact filename heading format (so grep "^## \[" wiki/log.md keeps working).
  • [ ] Any contradiction between the new source and an older page is annotated, not silently overwritten.
  • [ ] No file under raw/ was modified.

Tools

wikilistsources, wikireadsource, wikisearch, wikireadpage, wikiwrite_page. 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