Source Intake

Use this skill to turn an inbound source into durable project context without losing provenance or over-propagating weak ideas. It is source-type neutral: use it for social media, articles, books, PDFs, videos after transcription or perception, product pages, meeting snippets, email excerpts, screenshots, repo notes, or user-provided source material.

The goal is not a polished summary. The goal is a source-backed capture, a clear value judgment, and only the justified downstream updates.

Choose The Owner

Store the capture under the project that owns the source or follow-up.

Use an existing project intake surface when one exists. If there is no project convention, use:

<project>/captures/source-captures/YYYY-MM-DD-short-slug.md
<project>/captures/entity-propagation/YYYY-MM-DD-short-slug.md

If a platform-specific readback skill exists for a source, such as a social-media, email, browser, repository, calendar, or document connector workflow, use that focused skill first to retrieve the source accurately. Return here when the fetched source needs capture, interpretation, propagation, routing, or durable follow-up.