wiki-ingest
Use when an operation issue asks you to ingest a captured source from `raw/` into the LLM Wiki, or when the user explicitly says "ingest <slug>". The issue body will name a file under `raw/` (e.g. `raw/karpathy-llm-wiki.md`) and ask for durable wiki pages. Do not invoke this skill for Paperclip activity bundles — those use `paperclip-distill` instead.
- License 许可
- MIT
- 最近更新
- 2026-10-30
- Stars
- ★ 1
- Forks
- 2
01 前言 Front Matter
- name
- wiki-ingest
- description
- Use when an operation issue asks you to ingest a captured source from `raw/` into the LLM Wiki, or when the user explicitly says "ingest <slug>". The issue body will name a file under `raw/` (e.g. `raw/karpathy-llm-wiki.md`) and ask for durable wiki pages. Do not invoke this skill for Paperclip activity bundles — those use `paperclip-distill` instead.
03 SKILL.md 正文
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 treatraw/as immutable). - The operation issue's target
wikiId,spaceSlug, and space root (otherwise stop and surface the missing config to the requester).
Workflow
- Read context first.
- Read the target space's
AGENTS.mdfor page conventions (filenames, frontmatter, voice, citation style). - Read the target space's
wiki/index.mdto see what already exists. - Read the target space's last ~20 entries of
wiki/log.mdto avoid re-ingesting a source or re-resolving a contradiction someone else already filed.
- Read the target space's
- Read the source end to end with
wiki_read_source, passing the operation issue'swikiIdandspaceSlug. Do not skim. Note the source's structure, claims, dates, and anything that contradicts existing pages. - 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.
- Write the source page at
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. - Update or create downstream pages in
entities/,concepts/, andsynthesis/. A typical ingest touches 5–15 pages; resist creating pages for ideas that only appear once. - Wire the cross-links. Every claim that comes from the source cites it as
(see [[wiki/sources/<slug>]]). Every entity / concept mentioned by name on more than one page links to its dedicated page. - Flag contradictions; do not silently overwrite. When new material disagrees with an existing page, append a
> ⚠ contradicted by [[wiki/sources/<slug>]] (YYYY-MM-DD)callout to the older page and note the conflict in the log. - Refresh
wiki/index.mdwith one-line summaries for any new pages. - 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/<slug>.mdwith valid frontmatter and asources: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.mdlists every new page under the right category with a one-line summary. - [ ]
wiki/log.mdhas the ingest entry with the exact filename heading format (sogrep "^## \[" wiki/log.mdkeeps working). - [ ] Any contradiction between the new source and an older page is annotated, not silently overwritten.
- [ ] No file under
raw/was modified.
Tools
wiki_list_sources, wiki_read_source, wiki_search, wiki_read_page, wiki_write_page. Always include the operation issue's wikiId and spaceSlug.
04 同仓库更多 Skills
terminal-bench-loop
Run a single Terminal-Bench problem through Paperclip in a bounded, human-in-the-loop improvement cycle until the smoke passes, the board rejects the next fix, the iteration budget is exhausted, or a real blocker is named. Each iteration runs a bounded smoke against an isolated Paperclip App worktree, captures artifacts, diagnoses the exact stop point with `/diagnose-why-work-stopped`, requests board confirmation before any product fix, then reruns against the same worktree. Use whenever an issue asks to "run Terminal-Bench in a loop", "drive Terminal-Bench until it passes", "loop fix-git through Paperclip", or otherwise points at a Terminal-Bench task and asks for bounded iteration with diagnosis.
para-memory-files
File-based memory system using Tiago Forte's PARA method. Use this skill whenever you need to store, retrieve, update, or organize knowledge across sessions. Covers three memory layers: (1) Knowledge graph in PARA folders with atomic YAML facts, (2) Daily notes as raw timeline, (3) Tacit knowledge about user patterns. Also handles planning files, memory decay, weekly synthesis, and recall via qmd. Trigger on any memory operation: saving facts, writing daily notes, creating entities, running weekly synthesis, recalling past context, or managing plans.
paperclip
Interact with the Paperclip control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, set up or manage routines (recurring scheduled tasks), or call any Paperclip API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for Paperclip coordination.
paperclip-dev
Develop and operate a local Paperclip instance — start and stop servers, pull updates from master, run builds and tests, manage worktrees, back up databases, and diagnose problems. Use whenever you need to work on the Paperclip codebase itself or keep a running instance healthy.
paperclip-create-plugin
Create and develop external Paperclip plugins with the CLI-first workflow. Use when scaffolding a new plugin, working on a local plugin against a running Paperclip instance, or updating plugin authoring docs. Covers `paperclipai plugin init`, the local install loop via `paperclipai plugin install <path>`, worker/UI rebuild and reload semantics, and the required success checklist.
paperclip-create-agent
Create new agents in Paperclip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hire request.