MCP.Market

firecrawl-build-interact skill

by firecrawl·firecrawl/firecrawl·202k stars·AGPL-3.0

Integrate Firecrawl `/interact` into product code for dynamic pages and browser actions after scraping. Use when a feature needs clicks, form fills, pagination, authentication-aware flows, or other multi-step interactions that plain `/scrape` cannot complete.

A100/100content scan

Is the firecrawl-build-interact skill safe?

Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-10-25.

No findings.

Install the firecrawl-build-interact skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/firecrawl/firecrawl.git /tmp/firecrawl
mkdir -p ~/.claude/skills
cp -r /tmp/firecrawl/skills/firecrawl-build-interact ~/.claude/skills/firecrawl-build-interact
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

Firecrawl Build Interact

Use this when /scrape is not enough because the feature needs to act on the page.

Use This When

  • content appears only after clicks, typing, or navigation
  • the feature needs forms, pagination, filters, or multi-step flows
  • the product must stay in the same browser context after scraping

Default Recommendations

  • Start with /scrape, then escalate to /interact.
  • Keep /interact scoped to the smallest browser workflow that unlocks the data.
  • Use persistent profiles only when the feature truly needs authenticated state across sessions.

Common Product Patterns

  • search forms and faceted filters
  • paginated result sets
  • login-gated dashboards or tools
  • flows where the page must be explored before extraction is complete

Implementation Notes

  • /interact is the right tool when the page must be manipulated, not just read.
  • Keep prompts or action code specific to the product flow.
  • If the use case is fully open-ended browser automation, evaluate whether a browser sandbox is a better product fit.

Escalation Rules

  • If the page can be read directly, stay on firecrawl-build-scrape.

Docs (Source of Truth)

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

  • Node / TypeScript: docs.firecrawl.dev/agent-source-of-truth/node
  • Python: docs.firecrawl.dev/agent-source-of-truth/python
  • Rust: docs.firecrawl.dev/agent-source-of-truth/rust
  • Java: docs.firecrawl.dev/agent-source-of-truth/java
  • Elixir: docs.firecrawl.dev/agent-source-of-truth/elixir
  • cURL / REST: docs.firecrawl.dev/agent-source-of-truth/curl

See Also

  • firecrawl-build
  • firecrawl-build-scrape
  • firecrawl-build-search

More skills from firecrawl/firecrawl

  • Afirecrawl-buildIntegrate Firecrawl into application code whenever a product, agent, or workflow needs web data inside the app — web search, live search results, page scraping, structured extraction, or browser interaction. Use when building any feature that needs data from the web in code, even if the user does not mention Firecrawl explicitly and only describes wanting web data, website content, search, scraping, or interaction in an application. Trigger for Firecrawl requests, "fire girl" shorthand, and generic app-level web-data needs that should map to `/scrape`, `/search`, or `/interact`. Do not use this skill for one-off terminal-only web tasks during the current session; use `firecrawl/cli` for those.
  • Afirecrawl-build-onboardingGet Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.
  • Afirecrawl-build-scrapeIntegrate 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.
  • Afirecrawl-build-searchIntegrate Firecrawl `/search` into product code and agent workflows. Use when an app needs discovery before extraction, when the feature starts with a query instead of a URL, or when the system should search the web and optionally hydrate result content.

All agent skills → · MCP servers