Book a call
← All skills

Scraping · Web

Firecrawl Scrape

Page-level extraction as a product feature: markdown, HTML, links, screenshots and structured output from a URL you already have — plus how fresh that result actually is, which is the part that bites three months later.

Skill name
firecrawl-build-scrape
Triggers on
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.
Read time
2 min · 2 files · free to use and edit
Download full skill

This skill ships 2 files. The references are where the method lives — SKILL.md on its own will point at files you do not have, so take the archive rather than the markdown.

  • SKILL.md
  • references/freshness-and-liveness.md

Prefer just the instructions? Download SKILL.md alone.

Use it in your assistant

Claude Code — drop the file in your skills folder and it loads on the next session. Use ~/.claude/skills for every project, or .claude/skills inside a repo to keep it to that project.

mkdir -p ~/.claude/skills
curl -L https://growsteady.io/skills/firecrawl-build-scrape/archive | tar xz -C ~/.claude/skills

Claude apps (web and desktop) — Settings → Capabilities → Skills → add a skill. Extract the archive and upload the whole firecrawl-build-scrape folder, references included (zip it if an archive is asked for).

No install— paste the file into a Claude Project's custom instructions with “Copy as prompt”. Same behaviour, scoped to that project. Note that a paste carries the instructions only: this skill's references do not come with it, so use a real install if you want the full method.

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

← All skills