// Use when an operation issue asks you to answer a question from the LLM Wiki — `operationType: "query"` and a question in the issue body. Answer with citations to wiki pages and raw sources, and offer to file durable synthesis back into `wiki/synthesis/` so the work compounds instead of disappearing into a chat thread.
Write the Discord release announcement for a stable Paperclip release. Companion to `release-changelog` — that skill produces the file at `releases/vYYYY.MDD.P.md`; this one turns that file into a single copy-pasteable Discord post in dotta's voice and attaches it as the `discord_announcement` document on the release issue.
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.
Use when an operation issue is an index refresh — typically the hourly index-refresh routine. Rebuild `wiki/index.md` so each entry has a tight, scannable one-line summary and the catalog tracks the actual contents of `wiki/`. Resolve drift between the index and recent log activity, but do not edit page content.
Use when an operation issue is a Paperclip cursor-window, distill, or backfill — `operationType: "distill"` or `"backfill"` and the body references a Paperclip source bundle for a project or root issue. Turn raw Paperclip activity into a wiki-insightful project page, decisions log, and history note. This skill exists specifically to replace the stiff, datestamp-heavy templated output that the deterministic distiller produces.
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.
Use when an operation issue is a lint or health-check (`operationType: "lint"`) — typically the nightly lint routine or a manual "Run lint" from the UI. Audit the wiki for contradictions, orphans, weak provenance, broken links, and missing concept pages, and return a triage list — do not auto-fix.
| name | wiki-query |
| description | Use when an operation issue asks you to answer a question from the LLM Wiki — `operationType: "query"` and a question in the issue body. Answer with citations to wiki pages and raw sources, and offer to file durable synthesis back into `wiki/synthesis/` so the work compounds instead of disappearing into a chat thread. |
Answer a question from what the wiki actually contains, with citations.
operationType: "query" and the question in the body.wikiId, spaceSlug, and space root.wiki/index.md first — it is the navigation aid. Identify candidate pages.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.raw/ precisely so you can verify before answering. Use wiki_read_source.(see [[wiki/concepts/managed-resources]]) or (see raw/<filename>).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.wiki/synthesis/.Before closing the operation issue:
wiki/index.md lists it and wiki/log.md has a query | filed synthesis entry.raw/ was modified.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.