paperclip-distill
Paperclip Distill transforms project, issue, comment, and document activity from Paperclip into structured wiki pages that tell the story of what happened, what was decided, and what matters next. It produces executive standups and project indexes designed for readers unfamiliar with the source material, emphasizing interpretation and context over raw issue lists or dated status dumps.
Paperclip Distill converts Paperclip project activity into wiki-insightful project standups and index pages.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-28
Paperclip Distill converts Paperclip project activity into wiki-insightful project standups and index pages. Paperclip Distill transforms project, issue, comment, and document activity from Paperclip into structured wiki pages that tell the story of what happened, what was decided, and what matters next. It produces executive standups and project indexes designed for readers unfamiliar with the source material, emphasizing interpretation and context over raw issue lists or dated status dumps.
Use it when
- Yes.
- Paperclip Distill creates narrative project history and index pages that synthesize Paperclip source bundles into durable wiki knowledge.
Verify before relying
Read SKILL.md below before installing (1 file). Open directory: indexed for reading, not audited.
Install
paperclipai/paperclip/paperclip-distill · repository language: TypeScript
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How does paperclip-distill convert paperclip activity to wiki pages?
Paperclip Distill transforms project, issue, comment, and document activity from Paperclip into structured wiki pages that tell the story of what happened, what was decided, and what matters next. Rather than dumping raw issues, it produces narrative-driven documentation emphasizing interpretation and context for readers unfamiliar with the source material.
Can paperclip-distill distill paperclip issues into project standup?
Yes. Paperclip Distill generates executive project standups from either cursor-window snapshots or backfilled historical data. These standups extract decisions, risks, and blockers from your Paperclip source material and present them in readable, actionable form rather than as unprocessed status lists.
What output does paperclip-distill create from project history?
Paperclip Distill creates narrative project history and index pages that synthesize Paperclip source bundles into durable wiki knowledge bases. It produces project pages designed to be understood without access to the original issues, emphasizing what was decided and why it matters.
Does paperclip-distill work with cursor-window or backfill data?
Paperclip Distill supports both cursor-window snapshots for real-time standup generation and backfill operations to populate wiki knowledge bases from historical Paperclip project data. This flexibility lets you distill either current activity or reconstruct project context from archived source bundles.
How does paperclip-distill handle risks and blockers?
Paperclip Distill distills project decisions, risks, and blockers directly from Paperclip into readable wiki pages. It extracts these signals from comments and documents, surfacing them as structured insights rather than leaving them buried in raw issue threads.
What license does paperclip-distill use?
Paperclip Distill is released under the MIT license, allowing free use, modification, and distribution in both open-source and commercial projects with minimal restrictions.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
Paperclip Distill
Distill Paperclip project, issue, comment, and document activity into durable wiki pages. The success criterion is wiki-insightful, not procedural: a reader who has never seen Paperclip should learn what the project is, what was decided, what is at risk, and what the current state is — without scanning a list of ## [YYYY-MM-DD] headers.
When this skill is needed
- Cursor-window distillation: the routine fed you a bounded source bundle of recent Paperclip activity for one project or root issue.
- Backfill: the user asked to seed the wiki with the historical activity of a project or root issue. Source window may be wide.
- Manual
distill-paperclip-nowrequest from the UI.
If the operation issue is operationType: "ingest" (raw file) or operationType: "query", this is the wrong skill — use wiki-ingest or wiki-query.
Destination space
In Phase 1, every Paperclip
(truncated - see the full file via the links below)
File tree — 1 file
packages/plugins/plugin-llm-wiki/skills/paperclip-distill/SKILL.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Convert Paperclip project activity into durable, wiki-insightful documentation”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
wiki-ingest automates the transformation of a single source document into a structured wiki by creating and linking source, entity, concept, and synthesis pages. It reads your space's conventions, flags contradictions with existing content, and maintains a log of all ingestions. The skill ensures every claim traces back to its origin and all cross-references stay current.
wiki-ingest transforms a single source document into a set of durable wiki pages organized across entities, concepts, and synthesis sections. It reads existing space conventions and content to avoid duplication, flags contradictions rather than silently overwriting, and maintains full cross-linking and citation trails back to the original source.
LLM Wiki Maintainer helps you keep a company wiki organized and current using dedicated plugin tools. It handles source ingestion, page updates, index maintenance, and structural validation while enforcing citation discipline and immutable raw sources.
Wiki Query pulls answers from wiki pages and raw sources, citing each fact as it goes. When synthesis is needed, it offers to file a new page rather than answering silently. If the wiki can't answer, it says so plainly and suggests a concrete next step.
Keeps your wiki's index synchronized with its actual contents by walking the directory structure, spotting orphaned pages in the log, and reconciling deletions. Produces a clean, sorted index with one-line summaries per page—no dates or metadata clutter—and records all changes in the log for audit trails.
This skill keeps your wiki's index accurate and current by walking the actual file structure, comparing against recent log activity, and rebuilding entries in scannable one-line format. It reconciles missing pages, drops deleted entries, and preserves custom categories—without touching page content itself.
More skills wiki-lint (MIT) · Wiki Lint (MIT) · Wiki Query (MIT)