paperclip-distill

Distills Paperclip project activity into wiki standup pages, decisions logs, and history notes.

Updated Jul 14, 2026
One-click install
npx skills add https://github.com/Douglas-v/strategic-ai-paperclip-lab --skill paperclip-distill-douglas-v
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paperclip-distill
Source: https://github.com/Douglas-v/strategic-ai-paperclip-lab/tree/main/paperclip/packages/plugins/plugin-llm-wiki/skills/paperclip-distill
Command: npx skills add https://github.com/Douglas-v/strategic-ai-paperclip-lab --skill paperclip-distill-douglas-v

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Raw Paperclip activity (issues, comments, documents) arrives as procedural status churn, and deterministic templating produces datestamp-heavy pages that read like issue dumps rather than durable knowledge. This Skill turns cursor-window, distill, and backfill operations into wiki-insightful project pages that explain what a project is, what was decided, and what is at risk. ## Core Features & Use Cases - Project Standup Generation: Writes wiki/projects/<slug>/standup.md with an executive readout, what changed, decisions, blockers, and next actions. - Durable Project Pages: Maintains index.md, optional decisions.md and history.md organized by workstreams and phases rather than dates, patching existing pages instead of rewriting them. - Audit Trail Separation: Appends datestamped entries to wiki/log.md and refreshes wiki/index.md, keeping operational metadata out of narrative pages. - Use Case: A backfill operation supplies a wide source bundle for a project new to the wiki; the Skill reads every issue and comment, synthesizes the project's purpose and key decisions, and seeds the standup, project page, and log entries. ## Quick Start Distill the Paperclip activity bundle from this operation issue into the default wiki space and update the project standup, index page, and log.

Frequently Asked Questions about paperclip-distill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn Paperclip activity into a wiki project page?

Read the full source bundle, then write a standup page with an executive readout, grouped changes, decisions, blockers, and next actions. Follow with the project index page organized by workstreams, and append a datestamped entry to the wiki log.

When should I use paperclip-distill instead of wiki-ingest or wiki-query?

Use it only for operation issues with operationType distill or backfill carrying a Paperclip source bundle. Operations of type ingest (raw files) or query belong to the wiki-ingest and wiki-query skills respectively.

Can Paperclip attachments or work products be distilled into wiki pages?

No. Assets, attachments, and work products are metadata-only under the current asset gate. Never fetch asset content URLs or dereference work-product links; only issue descriptions, comment bodies, and document bodies are allowed source text.

What happens when a Paperclip bundle has no meaningful signal?

Do not write a project page. Append a low-signal skip entry to the wiki log naming the cursor window, close the operation issue with a no-durable-change comment, and leave the source hash unchanged.

Why does the distilled wiki page avoid date-based section headers?

Datestamp headers belong in the wiki log, which is the audit trail. Project pages are durable knowledge organized by concepts, workstreams, and decisions, with a single current_as_of timestamp in the frontmatter.