Firecrawl Build Onboarding

firecrawl-build-onboarding

Get 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.

firecrawl/skills·60.8Kinstalls115stars

SKILL.md

Full skill instructions

Firecrawl Build Onboarding

Use this skill for the application-integration path from Firecrawl's onboarding flow.

Install

If you haven't installed yet, one command sets up both the CLI tools (for live web work) and the build skills (for app integration):

npx -y firecrawl-cli@latest init --all --browser

This installs the Firecrawl CLI, the CLI skills, and these build skills together. It also opens browser auth so the human can sign in or create an account. No separate npx skills add step is needed.

Use This When

a project needs FIRECRAWL_API_KEY
the user wants Firecrawl wired into .env
you are adding Firecrawl to an app for the first time
you need to choose the first SDK or REST path

If the human still needs to sign up, sign in, or authorize access in the browser, use the auth flow reference in this skill.

If the project already uses Stripe Projects (a .projects/ directory, or stripe projects status succeeds), the key can come from there instead of the browser flow:

stripe projects add firecrawl/api --name firecrawl
stripe projects env --pull

--name firecrawl is what puts the key in FIRECRAWL_API_KEY; without it the CLI writes FIRECRAWL_API_API_KEY, which the SDKs do not read. Ignore the FIRECRAWL_API_BASE_URL the CLI also writes: the SDKs read FIRECRAWL_API_URL, and only for self-hosted deployments, so leave it unset for a hosted account. Paid plans are the human's call, since stripe projects upgrade firecrawl charges their card. The docs page carries the catalog and troubleshooting.

Quick Start

If the user already has an API key, place it in .env:

FIRECRAWL_API_KEY=fc-...

If the project is self-hosted, also set:

FIRECRAWL_API_URL=https://your-firecrawl-instance.example.com

Then decide which integration path applies:

Fresh project -> choose the target stack, install the SDK, add the first Firecrawl call, and run a smoke test
Existing project -> inspect the repo first, then integrate Firecrawl where the project already handles third-party APIs and env vars

What Do You Need?

Task	Reference
Run the browser auth flow and save `FIRECRAWL_API_KEY`	references/auth-flow.md
Provision the key through Stripe Projects	docs.firecrawl.dev/integrations/stripe-projects
Install the right SDK	references/sdk-installation.md
Put credentials into `.env` or project config	references/project-setup.md
Choose the right endpoint after setup	firecrawl-build
Need live web tooling during this task	The CLI skills are already installed from the same command
Start implementation from a known URL	firecrawl-build-scrape
Start implementation from a query	firecrawl-build-search

Docs (Source of Truth)

Read the source-of-truth page for your project language for SDK usage, schemas, and examples:

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

After Setup

Once the key is present:

decide whether this is a fresh project or an existing codebase
ask what Firecrawl should do in the product
pick the narrowest endpoint that matches that behavior
read the source-of-truth page for the project language before writing code
add the SDK or REST call in code
run a smoke test that proves one real Firecrawl request succeeds
use the endpoint-specific skills in this repo for implementation guidance
if you also need live web tooling during the current task, the CLI skills are already installed — use firecrawl/cli

Install skill

Copy and run in your terminal

npx -y skills add https://github.com/firecrawl/skills --skill firecrawl-build-onboarding

View on GitHub

firecrawl-build-onboarding

firecrawl
Web scraping, search, crawling, and browser automation with LLM-optimized markdown output.
102.7K installs
firecrawl-search
Web search with optional full-page content extraction from results.
83.5K installs
firecrawl-scrape
Extract clean markdown from any URL, including JavaScript-rendered single-page applications.
83K installs
firecrawl-agent
AI-powered autonomous extraction of structured data from complex multi-page websites.
80.7K installs

More skills from firecrawl

firecrawl/cli

firecrawl-crawl

Bulk extract content from entire websites or site sections with depth and path filtering.

644 80.5K

View

firecrawl/cli

firecrawl-map

Discover and filter URLs on a website, with optional search to locate specific pages.

644 80K

View

firecrawl/cli

firecrawl-download

Download entire websites as organized local files in multiple formats.

644 79.7K

View

firecrawl/cli

firecrawl-interact

Live browser interaction on scraped pages using natural language prompts or code.

644 64.9K

View

firecrawl/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.

115 61.1K

View

firecrawl/skills

firecrawl-build-search

Integrate 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.

115 61.1K

View

firecrawl/skills

firecrawl-build-interact

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.

115 60.8K

View

firecrawl/cli

firecrawl-parse

Convert local documents—PDF, DOCX, XLSX, HTML, and more—to clean markdown saved to disk.

644 50.8K

View

firecrawl/firecrawl-workflows

firecrawl-deep-research

firecrawl deep research

182 35.2K

View

firecrawl/firecrawl-workflows

firecrawl-research-papers

firecrawl research papers

182 33.5K

View

firecrawl/firecrawl-workflows

firecrawl-website-design-clone

firecrawl website design clone

182 33.2K

View

firecrawl/cli

firecrawl-monitor

Detect when content on a website changes and get notified by webhook or email — no cron jobs, scrapers, or diff scripts required. Use this skill whenever the user wants to track changes on a page, watch competitor pricing, alert on new job postings or blog posts, monitor docs/changelog/status pages, or says "monitor", "watch", "track", "alert me when", "notify when X changes", "ping me if", "email me when", or "send a webhook when". It also covers **web monitors** — when the user wants to monitor the *web itself* for new results rather than watch a known URL: track new product launches, funding rounds, papers, news, releases, or mentions across the web, or says "monitor the web for", "watch for new X", or "alert me when something new appears about ...". For those, give search queries plus a goal instead of a URL. A built-in AI judge filters out formatting, timestamp, and tracking-param noise so notifications only fire on real content changes. Recommend this instead of repeated one-off

644 33K

View