AutoGineer
Generated banner for Firecrawl Build Onboarding
Generated logo for Firecrawl Build Onboarding

Firecrawl Build Onboarding

FirecrawlOfficialCreated by firecrawl

  • Skill
  • Tool integration
  • Software development
  • ISC
  • Low risk
Download ZIP

From the author

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.
— the description by firecrawl

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The Firecrawl Build Onboarding skill provides a structured path for integrating Firecrawl into new or existing software projects. It handles the essential setup steps, including browser-based authentication to retrieve API keys, environment variable configuration, and guidance on selecting the appropriate SDK for various programming languages. Designed to streamline the developer experience, it ensures that credentials are managed securely and that the project is ready for Firecrawl API interactions.

What it does

  • Facilitates browser-based authentication to obtain a Firecrawl API key.
  • Configures environment variables like FIRECRAWL_API_KEY and FIRECRAWL_API_URL.
  • Provides guidance on selecting and installing the correct SDK for your project language.
  • Supports both hosted Firecrawl services and self-hosted deployments.
  • Integrates with existing project structures and secret management practices.
  • Offers a clear path for smoke testing initial API requests.

When to use it

  • When you need to add Firecrawl capabilities to a project for the first time.
  • When a project requires a valid FIRECRAWL_API_KEY to function.
  • When you need to configure environment variables for local or production development.
  • When you are setting up a new project and need to choose the right SDK or REST integration path.

Advantages

  • Simplifies the complex task of initial API authentication and setup.
  • Ensures secure credential handling by promoting environment variable usage.
  • Provides a unified approach for multiple programming languages.
  • Reduces manual configuration errors during the integration process.

Usage examples

“I need to set up Firecrawl in my new Node.js project.”
The agent will guide you through the CLI initialization, trigger the browser auth flow to obtain your API key, and help you configure your .env file.
“How do I add my Firecrawl API key to my existing Python project?”
The agent will verify your current environment setup and provide instructions to securely add the FIRECRAWL_API_KEY to your configuration.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/firecrawl/firecrawl-build-onboarding/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip firecrawl-build-onboarding.zip -d .agents/skills

Documentation by firecrawl

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?

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

Files

ATTRIBUTION.md

Attribution

This folder is an unmodified copy of the Agent Skill "firecrawl-build-onboarding", distributed by AutoGineer (https://autogineer.com/agent-skills).

The skill's own files are unmodified copies. AutoGineer is not affiliated with or endorsed by the author or the publisher.

Files added by AutoGineer

  • ATTRIBUTION.md: this file, written by AutoGineer

  • LICENSE: copied from LICENSE

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs network access, Needs an API key, Needs Python, Needs Node.js

Security

What our scanner noticed· Low risk

  • Instructions that use the network

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
firecrawl
Publisher
Firecrawl (Official)
Source
firecrawl/skills · skills/build/firecrawl-build-onboarding · commit 458d9d0
Licence
ISC License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by firecrawl or Firecrawl.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download firecrawl-build-onboarding.zip