Agent skill

Firecrawl Build Onboarding

by firecrawl in firecrawl/firecrawl

Gets Firecrawl working in a project: signs you in through the browser, saves FIRECRAWL_API_KEY to .env and picks the first SDK or REST path.

ISCAuto-check: notesBackend & APIs

Install Firecrawl Build Onboarding

skills CLI
$ npx skills add firecrawl/firecrawl --skill firecrawl-build-onboarding -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install firecrawl/firecrawl firecrawl-build-onboarding --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/firecrawl/firecrawl.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/firecrawl-build-onboarding .claude/skills/firecrawl-build-onboarding && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
firecrawl-build-onboarding
GitHub stars
190k
Used in
1 other repo
Token cost
~1.4k tokens
SKILL.md length
497 words
Files
4 (incl. references)
Skills in repo
5
Repo updated
First seen
Licence
ISC

At a glance

Gets Firecrawl working in a project: signs you in through the browser, saves FIRECRAWL_API_KEY to .env and picks the first SDK or REST path.

  • Works in 8 steps: decide whether this is a fresh project… → ask what Firecrawl should do in the… → pick the narrowest endpoint that matches… → …
  • Adding Firecrawl to an application for the first time
  • SKILL.md covers Install, Use This When, Quick Start and What Do You Need?, plus 2 more sections
  • Calls stripe and npx; needs FIRECRAWL_API_KEY and FIRECRAWL_API_API_KEY

What it does

This companion to the Firecrawl build skills covers the setup step for application code. A single install command adds the Firecrawl CLI, the CLI skills and the build skills, and opens a browser sign-in so you can log in or create an account. If you already have a key it goes into .env, and self-hosted deployments also set FIRECRAWL_API_URL.

Projects that already use Stripe Projects can pull the key from there instead, and the skill notes a naming detail: the key only lands in FIRECRAWL_API_KEY when the name flag is set, and the extra base URL variable the CLI writes should be ignored for hosted accounts. Upgrading to a paid plan is left to you because it charges your card. After setup, the agent integrates Firecrawl into a fresh or existing project and runs a smoke test.

When your agent uses it

  • Adding Firecrawl to an application for the first time
  • Getting a FIRECRAWL_API_KEY into a project's .env
  • Choosing the first Firecrawl SDK for a stack

Example prompts

  • “Set up Firecrawl in this project and add the key to .env.”
  • “We already use Stripe Projects. Pull the Firecrawl key from there.”
  • “Which Firecrawl SDK should our Python backend start with?”

Requirements

  • A Firecrawl account or API key
  • Node.js to run npx firecrawl-cli

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  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

What it can do on your machine

Read from SKILL.md and the folder at commit e5df790. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • stripe
    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • docs.firecrawl.dev

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • FIRECRAWL_API_KEY
    • FIRECRAWL_API_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Firecrawl Build Onboarding loads about 1.4k tokens when it runs, and up to ~1.9k if it reads all its reference files. Until then it costs about 104 tokens; SKILL.md has 497 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~104
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:3
    , when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choo
  • NoteMentions a .env fileSKILL.md:43
    - the user wants Firecrawl wired into `.env`
  • NoteMentions a .env fileSKILL.md:60
    ser already has an API key, place it in `.env`:
  • NoteMentions a .env fileSKILL.md:84
    | **Put credentials into `.env` or project config** | [references/project-setup.md](references/project-setup.md) |

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from firecrawl/firecrawl at commit e5df790, republished under its ISC licence (© firecrawl). 497 words, ~1,380 tokens.

Download SKILL.mdSave it as .claude/skills/firecrawl-build-onboarding/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
firecrawl-build-onboarding
description
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.
license
ISC
metadata.author
firecrawl
metadata.version
0.1.0
metadata.homepage
https://www.firecrawl.dev
metadata.source
https://github.com/firecrawl/skills
references
references/auth-flow.md, references/sdk-installation.md, references/project-setup.md

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 (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
Show full SKILL.md (205 more words)Show less

What Do You Need?

TaskReference
Run the browser auth flow and save FIRECRAWL_API_KEYreferences/auth-flow.md
Provision the key through Stripe Projectsdocs.firecrawl.dev/integrations/stripe-projects
Install the right SDKreferences/sdk-installation.md
Put credentials into .env or project configreferences/project-setup.md
Choose the right endpoint after setupfirecrawl-build
Need live web tooling during this taskThe CLI skills are already installed from the same command
Start implementation from a known URLfirecrawl-build-scrape
Start implementation from a queryfirecrawl-build-search

Docs (Source of Truth)

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

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

© firecrawl, ISC. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in skills/firecrawl-build-onboarding of firecrawl/firecrawl.

  • SKILL.md
  • references/auth-flow.md
  • references/project-setup.md
  • references/sdk-installation.md

Open the folder on GitHubat commit e5df790

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in firecrawl/firecrawl, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Firecrawl Build Onboarding next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Firecrawl Build Onboarding compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Firecrawl Build Onboarding this skillfirecrawl/firecrawl190k1 repos~1.4kAutomated safety check: NotesISC
OneCLI Gatewaynanocoai/nanoclaw31k—~856Automated safety check: PassMIT
Firecrawl CI Integrationjeremylongshore/tons-of-skills-marketplace2.8k—~1.1kAutomated safety check: PassMIT
Printing Press Librarymvanhorn/printing-press-library2.1k—~4.8kAutomated safety check: PassNone
Dinero Currency Patternsdinerojs/dinero.js6.8k—~650Automated safety check: PassMIT
Apify Integration Developmentapify/agent-skills2.4k—~3.4kAutomated safety check: PassNone

Similar skills

  • OneCLI Gateway

    nanocoai/nanoclaw

    Explains how to call external APIs through the OneCLI proxy, which injects stored credentials into outgoing HTTPS requests so the agent never handles keys.

    31k GitHub stars~856 tokensUpdated 3 days ago
    Backend & APIsAuto-check passed
  • Firecrawl CI Integration

    jeremylongshore/tons-of-skills-marketplace

    Build deterministic CI gates for a Firecrawl v2 integration using synthetic fixtures, pinned schemas, secret scanning, and an optional protected smoke test.

    2.8k GitHub stars~1.1k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Printing Press Library

    mvanhorn/printing-press-library

    A skill your agent uses when looking for a CLI, API wrapper, scraper, data-source tool, automation tool, or focused agent skill for a task; searches the Printing Press Library and installs matching…

    2.1k GitHub stars~4.8k tokensUpdated today
    Backend & APIsAuto-check passed
  • Dinero Currency Patterns

    dinerojs/dinero.js

    Currency handling patterns for the Dinero.js money library. An agent skill from dinerojs/dinero.js.

    6.8k GitHub stars~650 tokensUpdated 4 days ago
    Backend & APIsAuto-check passed
  • Official

    Guides designing and building an official Apify integration for a company's product: workflow-automation apps, AI agent plugins, AI framework packages or direct API clients.

    2.4k GitHub stars~3.4k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Noodle Use

    wilfredinni/noodle

    Teach agents to create, organize, maintain, evaluate, import, convert, and automate noodle terminal REST client collections using supported CLI commands plus YAML and dotenv files.

    365 GitHub stars~8.5k tokensUpdated 2 days ago
    Backend & APIsAuto-check: notes

More from firecrawl/firecrawl

  • Adds Firecrawl's /scrape endpoint to application code to pull markdown, HTML, links, screenshots or structured data from a single known URL.

    190k GitHub starsUsed in 1 repo~944 tokens
    Auto-check passed
  • Firecrawl App Integration

    firecrawl/firecrawl

    Adds web search, scraping, structured extraction and browser interaction to application code using Firecrawl's scrape, search and interact endpoints.

    190k GitHub stars~2.1k tokensUpdated today
    Auto-check: notes
  • Guides adding Firecrawl's /interact endpoint to product code for pages that need clicks, forms, pagination or logged-in flows beyond plain scraping.

    190k GitHub starsUsed in 1 repo~731 tokens
    Auto-check passed
  • Firecrawl Search Integration

    firecrawl/firecrawl

    Guidance for adding Firecrawl's /search endpoint to product code and agent workflows when a feature starts from a query rather than a URL.

    190k GitHub starsUsed in 1 repo~1.1k tokens
    Auto-check passed

Works with

Questions about Firecrawl Build Onboarding

What does Firecrawl Build Onboarding do?

Gets Firecrawl working in a project: signs you in through the browser, saves FIRECRAWL_API_KEY to .env and picks the first SDK or REST path. This companion to the Firecrawl build skills covers the setup step for application code. A single install command adds the Firecrawl CLI, the CLI skills and the build skills, and opens a browser sign-in so you can log in or create an account.

When should I use Firecrawl Build Onboarding?

Firecrawl Build Onboarding fits situations like: adding Firecrawl to an application for the first time; getting a FIRECRAWL_API_KEY into a project's .env; choosing the first Firecrawl SDK for a stack.

How do I install Firecrawl Build Onboarding in Claude Code?

Run `npx skills add firecrawl/firecrawl --skill firecrawl-build-onboarding -a claude-code`. Or copy the skill folder (skills/firecrawl-build-onboarding in firecrawl/firecrawl) into .claude/skills/firecrawl-build-onboarding in your project. Claude Code loads it when a task matches its description.

How do I install Firecrawl Build Onboarding in Codex?

Run `npx skills add firecrawl/firecrawl --skill firecrawl-build-onboarding -a codex`. Or copy the skill folder (skills/firecrawl-build-onboarding in firecrawl/firecrawl) into .agents/skills/firecrawl-build-onboarding in your project. Codex loads it when a task matches its description.

Can I use Firecrawl Build Onboarding in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add firecrawl/firecrawl --skill firecrawl-build-onboarding -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/firecrawl-build-onboarding, .gemini/skills/firecrawl-build-onboarding, .github/skills/firecrawl-build-onboarding and .opencode/skills/firecrawl-build-onboarding in your project.

What does Firecrawl Build Onboarding need to run?

Going by SKILL.md and its folder, Firecrawl Build Onboarding needs the command-line tools its instructions call (stripe and npx) and credentials named FIRECRAWL_API_KEY and FIRECRAWL_API_API_KEY. Our summary lists: A Firecrawl account or API key; Node.js to run npx firecrawl-cli.

Does Firecrawl Build Onboarding access the network?

SKILL.md names 1 domain. As links in the text: docs.firecrawl.dev. This is read from the text; nothing was executed.

Is Firecrawl Build Onboarding safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Firecrawl Build Onboarding use?

Firecrawl Build Onboarding is published under the ISC licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Firecrawl Build Onboarding use?

About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 472 tokens, read only when the agent opens those files.

What are the alternatives to Firecrawl Build Onboarding?

Skills that share tags, products or a category with Firecrawl Build Onboarding: OneCLI Gateway (nanocoai/nanoclaw, 31k stars), Firecrawl CI Integration (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Printing Press Library (mvanhorn/printing-press-library, 2.1k stars) and Dinero Currency Patterns (dinerojs/dinero.js, 6.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Firecrawl Build Onboarding?

firecrawl (a GitHub organization) maintains it in firecrawl/firecrawl, which has 189,703 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 9, 2026.

Source: firecrawl/firecrawl on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.