A content-research agent that keeps the source clean

Use the website-to-markdown skill or recipe when the source is a page or site, and the YouTube transcript recipe when the source is a video. Send the output to Notion or a markdown store, keep the source URL and do not treat the extraction as a full-site crawl.

RAG quality starts with extraction quality. Navigation, cookie banners, duplicate blocks and truncated transcripts all become context noise. The files here produce a bounded markdown result and keep the source identifiable.

Method

  1. Choose the source type: a website, a single page or a YouTube video.

  2. Pick the markdown recipe or the transcript recipe. Check the input schema before the run.

  3. Send the output to Notion or a file store. Preserve the source URL and the extraction date.

  4. Clean the markdown before chunking. Remove navigation, repeated headers and empty sections.

Recipes for this job

MCP servers for this job

Skills for this job

Guardrails

  • A page extraction is not a full crawl. A site-wide job needs a crawler and a crawl policy.
  • A transcript can be auto-generated and may contain errors.
  • Do not republish third-party content without checking copyright and the source terms.

Questions

Can this agent crawl an entire website?

The recipe handles a bounded page or URL input. A full-site crawl needs a crawler, a scope limit and a policy for depth and rate. Do not treat one page extraction as a complete site archive.

Are YouTube transcripts always accurate?

No. Auto-generated captions can contain errors. Treat a transcript as source material and keep the video URL for verification.

Where should the markdown go?

Notion works for a reviewable knowledge base; a file store works for a RAG pipeline. Either way, keep the source URL and the extraction date with the document.