agentleFS
Sign inStart free
GabrieleDattileGabrieleDattile/agent-superpowers/skills/scraping/firecrawl-onboard/SKILL.md

firecrawl-build-onboarding

Skill1 starsChanged 15 days agoMITView on GitHub

Get Firecrawl credentials and SDK setup into a project. Use when an application

  • Reads credentials

7 other projects use a version of this, 7 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use firecrawl-interact, firecrawl-company-directories and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • RudraDudhat2509Skill

    firecrawl-interact

    Control and interact with a live browser session on any scraped page — click buttons, fill forms, navigate flows, and extract data using natural language prompts or code. Use when the user needs to interact with a webpage beyond simple scraping: logging into a site, submitting forms, clicking through pagination, handling infinite scroll, navigating multi-step checkout or wizard flows, or when a regular scrape failed because content is behind JavaScript interaction. Also useful for authenticated scraping via profiles. Triggers on "interact", "click", "fill out the form", "log in to", "sign in", "submit", "paginated", "next page", "infinite scroll", "interact with the page", "navigate to", "open a session", or "scrape failed".

    Also in 6 projects that use this

  • firecrawlSkill

    firecrawl-company-directories

    Extract structured company lists with Firecrawl from any page or site that lists companies: accelerator batches, VC portfolios, member and sponsor lists, marketplaces and app directories, YC, Crunchbase, Product Hunt or G2. Use when the user wants those companies as a CSV, JSON, CRM-ready list or research table, even without an explicit request to scrape.

    Also in 3 projects that use this

  • firecrawlSkill

    firecrawl-competitive-intel

    Monitor competitor pricing, features, changelogs, dashboards, and product changes with Firecrawl. Use for recurring competitive intelligence, pricing tier extraction, feature change tracking, or structured competitor alerts.

    Also in 3 projects that use this

  • BBTB2Skill

    firecrawl-parse

    Use this skill whenever the user is working with the Firecrawl API /parse endpoint. Triggers include: uploading local files (PDF, DOCX, XLSX, HTML) to Firecrawl, parsing documents with Firecrawl, extracting markdown or structured JSON from files using Firecrawl, choosing between /parse and /scrape, configuring PDF parsing modes (fast/auto/ocr), setting output formats, enabling zero data retention, or any question about Firecrawl document parsing. Also triggers when the user says 'parse this file with Firecrawl', 'use Firecrawl to extract', or 'Firecrawl /parse'.

    Also in 5 projects that use this

  • UtkarshDubeyGITSkill

    firecrawl-website-design-clone

    Extract any website's design system into an agent-ready DESIGN.md using Firecrawl scrape evidence. Use when the user wants colors, fonts, spacing, components, layout patterns, or brand/UI guidance from a website so AI agents can create new websites, clone a look, or build pages inspired by that design.

    Also in 3 projects that use this

  • parcadeiSkill

    firecrawl-scrape

    Scrape web pages and extract content via Firecrawl MCP

    Also in 6 projects that use this

  • +3 more from firecrawl

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 10 are common, 0 are distinctive, and 3 are very specific to this project.

  • 10

    Common

    Most of the 7 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

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

    line 44
  2. Common:

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

    line 48
  3. Common:

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

    line 66
  4. Very specific:

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

    line 68
  5. Very specific:

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

    line 79
  6. Common:

    If the project is self-hosted, also set:

    line 85
  7. Common:

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

    line 111
  8. Common:

    ask what Firecrawl should do in the product

    line 125
  9. Common:

    read the source-of-truth page for the project language before writing code

    line 127
  10. Common:

    add the SDK or REST call in code

    line 128
  11. Common:

    run a smoke test that proves one real Firecrawl request succeeds

    line 129
  12. Common:

    use the endpoint-specific skills in this repo for implementation guidance

    line 130
  13. Very specific:

    if you also need live web tooling during the current task, the CLI skills are already installed — use firecrawl/cli

    line 131

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.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):

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free