agentsclimarketplace
Sign in

Firecrawl build onboarding

Skill aiskillstore/marketplace/skills/firecrawl/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.From its SKILL.md

Install
npx -y skills add aiskillstore/marketplace --skill firecrawl-build-onboarding

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

What its file declares

Copied from the file, not written here

The file declares its own license as ISC. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

4.5 KB, 899 tokens by cl100k_base, as published. Nobody here has run it

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.

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

What ships with it: 4 files

65.0 KB alongside SKILL.md

references/

Gives 0 of the 12 instructions most codebase onboarding skills give in 899 tokens

Counted across 307 of the 325 authors here whose files we hold, read 2026-09-06

  • Focus first session on one successful outcomein 34 of 307, across 15 files
  • Show progress and celebrate completionsin 32 of 307, across 13 files
  • Prefer interactive doing over tutorialsin 32 of 307, across 13 files
  • Remove every step between signup and core valuein 32 of 307, across 13 files
  • Keep checklists to 3-7 items ordered by valuein 32 of 307, across 13 files
  • Read product marketing context before asking questionsin 28 of 307, across 13 files
  • Focus fixes on the biggest funnel drop-offsin 22 of 307, across 7 files
  • Define activation as the action most correlated with retentionin 20 of 307, across 6 files
  • Give one clear next action at every stepin 19 of 307, across 8 files
  • Understand product context and current state before recommendingin 15 of 307, across 3 files
  • Limit guided tours to five dismissable stepsin 15 of 307, across 6 files
  • Trace one request from entry to responsein 14 of 307, across 8 files

Said here and by no other author read

  • place FIRECRAWL_API_KEY in .env
  • set FIRECRAWL_API_URL for self-hosted projects
  • use the browser auth flow for sign-up
  • decide fresh project versus existing codebase
  • inspect the repo before integrating into existing projects
  • install the SDK for fresh projects

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.