firecrawl-build

Integrate Firecrawl web scraping, search, and browser interaction into application code.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/leonardoacosta/agents --skill firecrawl-build-leonardoacosta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: firecrawl-build
Source: https://github.com/leonardoacosta/agents/tree/main/skills/firecrawl-build
Command: npx skills add https://github.com/leonardoacosta/agents --skill firecrawl-build-leonardoacosta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Adding live web data to a product requires choosing the right Firecrawl endpoint, installing the correct SDK, configuring API credentials, and verifying the integration actually works. This Skill guides that entire integration process so web search, scraping, and browser interaction land correctly inside application code rather than as ad-hoc terminal calls. ## Core Features & Use Cases - Endpoint Selection: Routes product requirements to the narrowest Firecrawl endpoint — /scrape for known URLs, /search for query-driven discovery, /interact for clicks, forms, and navigation after scraping. - Project Intake & SDK Setup: Distinguishes fresh projects from existing codebases, inspects repo conventions, and installs the matching SDK (@mendable/firecrawl-js, firecrawl-py) or REST calls. - Auth & Verification: Configures FIRECRAWL_API_KEY and optional self-hosted FIRECRAWL_API_URL, then runs a smoke test proving a real Firecrawl request succeeds through the actual integration path. - Use Case: A developer building a competitor-monitoring feature describes needing pricing data from websites inside their app. The Skill inspects the repo, selects /scrape, installs the SDK, wires credentials into .env, and verifies a live request. ## Quick Start Ask the agent to integrate Firecrawl into your application so the product can scrape pages, search the web, or interact with sites from code.

Frequently Asked Questions about firecrawl-build

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate Firecrawl into my application code?

Classify the project as fresh or existing, ask what web data the product needs, then route to the matching endpoint: /scrape for known URLs, /search for query-driven discovery, or /interact for browser actions. Install the SDK for your stack, set FIRECRAWL_API_KEY, and run a smoke test.

Which Firecrawl endpoint should I use: scrape, search, or interact?

Use /scrape when you already have the URL, /search when the feature starts with a query and must discover sources, and /interact only when the page must be clicked, typed into, or navigated after scraping. Default priority is scrape, then search, then interact.

What SDK do I install for Firecrawl in Node or Python?

For JavaScript/TypeScript install @mendable/firecrawl-js via npm; for Python install firecrawl-py via pip. For other languages or minimal dependency footprints, call the Firecrawl REST API directly using the language-specific source-of-truth docs.

Can I use Firecrawl with a self-hosted deployment?

Yes, set FIRECRAWL_API_URL to your self-hosted instance URL alongside FIRECRAWL_API_KEY. Only set FIRECRAWL_API_URL when the project is not using the hosted api.firecrawl.dev service.

When should I use the Firecrawl CLI instead of build integration?

Use the firecrawl/cli skill for one-off terminal tasks during the current session, such as searching the web or scraping a page interactively. Use this build skill only when web data capabilities must live inside application code as a product feature.

Why does my Firecrawl integration fail after setup?

Common causes are missing or hardcoded API keys, wrong base URL, SDK installation issues, or incorrect endpoint choice. Verify credentials load from .env or the secret store, then run a minimal real request through the actual integration path to isolate the failure.