paperclip-distill

Distill Paperclip project activity into durable wiki standups, decisions, and history pages.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/adamtpang/summon.company --skill paperclip-distill-adamtpang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paperclip-distill
Source: https://github.com/adamtpang/summon.company/tree/main/packages/plugins/plugin-llm-wiki/skills/paperclip-distill
Command: npx skills add https://github.com/adamtpang/summon.company --skill paperclip-distill-adamtpang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Raw Paperclip activity (issues, comments, documents) arrives as procedural status churn that tells a reader nothing about what a project is, what was decided, or what is at risk. This Skill turns bounded source bundles into wiki-insightful project pages instead of datestamped issue dumps. ## 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 as patches that accumulate decisions over time rather than rewriting them. - Asset Safety Gate: Treats Paperclip attachments and work products as metadata-only, never dereferencing asset URLs or fetching /api/assets/:id/content. - Use Case: A cursor-window operation issue arrives with a bundle of recent Paperclip activity for one project; the Skill reads the full bundle, patches the existing project pages, refreshes wiki/index.md, and appends a dated entry to wiki/log.md. ## Quick Start Distill the Paperclip source bundle from this operation issue into the default wiki space, updating the project standup and index pages and logging the cursor window.

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 issue 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. Patch the existing project index rather than rewriting it, and cite issues by identifier like PAP-3179 as evidence.

What is the difference between Paperclip distill, ingest, and query operations?

Distill handles cursor-window, backfill, and manual distill-now operations that produce wiki pages. Operation issues with operationType ingest (raw files) or query belong to the wiki-ingest or wiki-query skills instead.

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

No. Assets, attachments, and work products are metadata-only under the asset gate. The skill never fetches /api/assets/:id/content or dereferences work-product URLs; such requests are deferred to a separate extraction policy.

What happens when a Paperclip bundle has no durable signal?

No project page is written. The skill appends a low-signal skip entry to wiki/log.md naming the cursor window, closes the operation issue with a no-durable-change comment, and does not bump the source hash.

Why should datestamped sections stay out of Paperclip project pages?

Datestamp headers like ## [YYYY-MM-DD] belong in wiki/log.md as the audit trail. Project pages are durable knowledge organized by concepts, workstreams, and decisions, with a single current_as_of value in frontmatter.