AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

firecrawl-build-scrape

Integrate Firecrawl `/scrape` into product code for single-page extraction. Use when an app already has a URL and needs markdown, HTML, links, screenshots, metadata, or structured page output. Prefer this skill over broader crawl patterns when the feature is page-level.

Original source
firecrawl
License
ISC
Pinned revision
2bf714d9f45e85085036a533ceb943c8577aef2b

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read firecrawl--firecrawl-build-scrape at revision 2bf714d9f45e85085036a533ceb943c8577aef2b, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 2

SKILL.md

Firecrawl Build Scrape

Use this when the application already has the URL and needs content from one page.

Use This When

  • the feature starts from a known URL
  • you need page content for retrieval, summarization, enrichment, or monitoring
  • you want the default extraction primitive before considering /interact

Default Recommendations

  • Return markdown unless the feature truly needs another format.
  • Use onlyMainContent for article-like pages where nav and chrome add noise.
  • Add waits or other rendering options only when the page needs them.

Freshness and Liveness

  • Firecrawl reuses recently indexed content, which is what makes repeat reads of the same URL fast. Set maxAge (milliseconds) to bound how old a reused copy may be, or maxAge: 0 to skip index reuse for a freshness-critical read.
  • Read metadata.cacheState and metadata.cachedAt to see what you actually got.
  • A successful scrape reports what the page returned. Whether the thing the page describes is still active is a source-specific judgment your code makes.
  • See references/freshness-and-liveness.md for the tradeoff, the metadata, and the decision rule.

Common Product Patterns

  • knowledge ingestion from known URLs
  • enrichment from a company, product, or docs page
  • pricing, changelog, and documentation extraction
  • page-level quality checks or monitoring

Escalation Rules

Implementation Notes

  • Keep the integration narrow: one feature, one URL, one extraction contract.
  • Treat /scrape as the default primitive for downstream LLM or indexing pipelines.
  • Request richer formats only when the consumer needs them, such as links, screenshots, or branding data.

Docs (Source of Truth)

Read the source-of-truth page for your project language before writing integration code:

See Also