Paperclip Source Capture

Run a creator's source-capture loop directly against their LLM Wiki space:

Raw dump (raw/, no task)  ->  guided ingest (structured wiki/ pages, no maintainer)  ->  reused via wiki-ask

This skill captures and ingests only. It never publishes, schedules, posts, or anonymizes. Anonymization happens later, at publish time, in the agent that drafts the public artifact.

Why this skill (and not the default wiki flow)

The wiki's default file-upload path creates a per-file ingest operation issue and hands it to the shared Wiki Maintainer agent. That leaves task trace and can't be tuned per creator. This skill instead writes straight to the space through the no-task plugin routes (verified below), so the operator owns the loop end to end and the Maintainer is never invoked.

Relationship to the company wiki-ask / wiki-contribute skills (worker-agent path):

• wiki-contribute deposits to the default space and walks away for the Maintainer to curate. This skill is the operator equivalent aimed at a creator's own space, and it does the ingest itself.
• wiki-ask is how a downstream agent (e.g. a post writer) later reads the space. Reference it by name; it lives in the company skill library.

References