Firecrawl Build Onboarding

When to use this skill

Use Firecrawl Build Onboarding when an AI agent needs a reusable SKILL.md workflow for this job: Get Firecrawl credentials and SDK setup into a project. Use when an application needs FIRECRAWLAPIKEY, 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.

When not to use it

Skip Firecrawl Build Onboarding when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

1. Personal install: create ~/.claude/skills/firecrawl-build-onboarding/SKILL.md (and any bundled scripts) so Claude Code, Claude Desktop, and compatible agents can load it in every project.
2. Project install: commit the same folder at .claude/skills/firecrawl-build-onboarding/ so teammates get the skill with the repo.
3. Restart the agent session after copying files so it re-scans the skills directory, then ask for the task in words that match the skill description.

Full install guide for Claude, Cursor, and Codex

What this skill does

# 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):

```bash 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](https://docs.firecrawl.dev/integrations/stripe-projects) (a `.projects/` directory, or `stripe projects status` succeeds), the key can come from there instead of the browser flow:

```bash 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`:

```dotenv FIRECRAWL_API_KEY=fc-... ```

If the project is self-hosted, also set:

```dotenv 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](references/auth-flow.md) | | **Provision the key through Stripe Projects** | [docs.firecrawl.dev/integrations/stripe-projects](https://docs.firecrawl.dev/integrations/stripe-projects) | | **Install the right SDK** | [references/sdk-installation.md](references/sdk-installation.md) | | **Put credentials into `.env` or project config** | [references/project-setup.md](references/project-setup.md) | | **Choose the right endpoint after setup** | [firecrawl-build](../firecrawl-build/SKILL.md) | | **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](../firecrawl-build-scrape/SKILL.md) | | **Start implementation from a query** | [firecrawl-build-search](../firecrawl-build-search/SKILL.md) |

## 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](https://docs.firecrawl.dev/agent-source-of-truth/node) - **Python**: [docs.firecrawl.dev/agent-source-of-truth/python](https://docs.firecrawl.dev/agent-source-of-truth/python) - **Rust**: [docs.firecrawl.dev/agent-source-of-truth/rust](https://docs.firecrawl.dev/agent-source-of-truth/rust) - **Java**: [docs.firecrawl.dev/agent-source-of-truth/java](https://docs.firecrawl.dev/agent-source-of-truth/java) - **Elixir**: [docs.firecrawl.dev/agent-source-of-truth/elixir](https://docs.firecrawl.dev/agent-source-of-truth/elixir) - **cURL / REST**: [docs.firecrawl.dev/agent-source-of-truth/curl](https://docs.firecrawl.dev/agent-source-of-truth/curl)

## After Setup

Once the key is present:

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

Intended uses

• Use Firecrawl Build Onboarding when this documented workflow matches the task.