Turn a captured source document into linked LLM Wiki pages for sources, entities, concepts, and combined insights. Update the index and log, preserve the original material, and flag contradictions with existing knowledge instead of silently replacing it.
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.
wiki-ingest reads saved material and adds it to LLM Wiki as knowledge with traceable sources. It creates a source page summarizing the material and its claims, then creates or updates pages for people, organizations, concepts, and combined insights. It connects pages, adds source references, and updates the index and ingestion history. When new material contradicts an existing page, it preserves the disagreement in annotations and history instead of silently replacing earlier text.
Use it to build a collection of research that you can refer to later. It checks the existing index and recent history first, helping avoid repeated ingestion or repeated handling of an already recorded contradiction. It also avoids creating unnecessary pages for ideas that appear only once.
raw/ and update the related concept pages and index.”You need the target wikiId, spaceSlug, space root information, and Wiki tools. Originals in raw/ remain unchanged. For interactive requests, it presents the main takeaways and confirms the emphasis before writing. Paperclip bundles must use paperclip-distill.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 20, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Turn one source document into durable, interlinked wiki knowledge.
operationType: "ingest" assigned to you.raw/ path mentioned in the issue body (always treat raw/ as immutable).wikiId, spaceSlug, and space root (otherwise stop and surface the missing config to the requester).AGENTS.md for page conventions (filenames, frontmatter, voice, citation style).wiki/index.md to see what already exists.wiki/log.md to avoid re-ingesting a source or re-resolving a contradiction someone else already filed.wiki_read_source, passing the operation issue's wikiId and spaceSlug. Do not skim. Note the source's structure, claims, dates, and anything that contradicts existing pages.wiki/sources/<slug>.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.entities/, concepts/, and synthesis/. A typical ingest touches 5–15 pages; resist creating pages for ideas that only appear once.(see [[wiki/sources/<slug>]]). Every entity / concept mentioned by name on more than one page links to its dedicated page.> ⚠ contradicted by [[wiki/sources/<slug>]] (YYYY-MM-DD) callout to the older page and note the conflict in the log.wiki/index.md with one-line summaries for any new pages.wiki/log.md:
## [YYYY-MM-DD] ingest | <source title>
- source: raw/<filename>
- new pages: [[...]], [[...]]
- updated pages: [[...]], [[...]]
- notes: <one-line synthesis or open question>
Before closing the operation issue:
wiki/sources/<slug>.md with valid frontmatter and a sources: field pointing to the raw path.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).raw/ was modified.wiki_list_sources, wiki_read_source, wiki_search, wiki_read_page, wiki_write_page. Always include the operation issue's wikiId and spaceSlug.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Add or extend Paperclip end-to-end evaluations that exercise real browser workflows across the server, database, and runner. Define expected outcomes, check independent evidence, and connect results to the existing reporting pipeline for local or Daytona execution.
Add or extend Paperclip Runner evaluations that test real sessions against a mock control service. Define observable pass conditions, validate cases and run selections, and retain source revisions, evidence, and costs for authorized live runs.
Use a real browser to verify web pages and apps through short, supervised interactions. Capture screenshots, inspect errors and network requests, and document reproducible steps for UI bugs or expected behavior checks.
Read email linked to assigned Paperclip tasks, send new messages or replies through an assigned AgentMail inbox, and check delivery outcomes. Follow task permissions and preserve retry identifiers to avoid duplicate sends.
Inspect proposed changes in GitHub, GitLab, or Perforce for review feedback, failed automated checks, and incomplete descriptions. It separates actionable findings from informational or resolved comments, then helps fix issues and close addressed review threads when requested.
Create an AI agent company or team package from an idea or an existing repository. Define roles, reporting lines, skills, and work handoffs, then generate structured files that follow the Agent Companies specification.