New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Firecrawl App Integration

by firecrawl in firecrawl/firecrawl

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

ISCAuto-check: notesData & Analytics

Install Firecrawl App Integration

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

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

GitHub CLI
$ gh skill install firecrawl/firecrawl firecrawl-build --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 .claude/skills/firecrawl-build && 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
GitHub stars
190k
Token cost
~2.1k tokens
SKILL.md length
732 words
Files
7 (incl. references)
Skills in repo
5
Repo updated
First seen
Licence
ISC

At a glance

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

  • Works in 3 steps: Decide whether this is a fresh project… → Ask what web data the product needs and… → If this is an existing project, inspect…
  • Building a feature that needs live web search inside an app
  • SKILL.md covers Use This When, Quick Start, Required Intake and What Do You Need?, plus 3 more sections
  • Calls npx; needs FIRECRAWL_API_KEY

What it does

This skill is for building Firecrawl into a product, not for one-off lookups during a session, which belong to the separate firecrawl/cli skill. It applies whenever a feature needs data from the web, even if Firecrawl is never named: live search results, page content from known URLs, structured fields, or clicks and form fills after a page loads.

The agent first decides whether it is working in a fresh or an existing project and asks what web data the product needs and how. It then chooses the narrowest endpoint: scrape for a known URL, search when there is only a query, interact when scraping has to continue into navigation. Separate research-paper and developer indexes are noted for literature and documentation lookups. References cover authentication and environment setup, SDK installation, integration patterns and verification.

When your agent uses it

  • Building a feature that needs live web search inside an app
  • Scraping known pages into an application workflow
  • Letting a backend agent click through a site after loading it
  • Choosing which Firecrawl endpoint fits a requirement

Example prompts

  • “Add a summarize-this-URL feature to our Next.js app using Firecrawl.”
  • “Our agent needs competitor pricing from the web. Wire that into the backend.”
  • “Which Firecrawl endpoint should I use to log in and download invoices?”

Requirements

  • A Firecrawl API key (FIRECRAWL_API_KEY)

Workflow steps

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

  1. Decide whether this is a fresh project or an existing project.
  2. Ask what web data the product needs and what Firecrawl should do in the product.
  3. If this is an existing project, inspect the repo before choosing SDK, REST, file locations, or env handling.

What it can do on your machine

Read from SKILL.md and the folder at commit f9f2e3d. 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:

    • 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

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

Context cost

Firecrawl App Integration loads about 2.1k tokens when it runs, and up to ~4k if it reads all its reference files. Until then it costs about 180 tokens; SKILL.md has 732 words of instructions outside code blocks.

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

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:12
    wl API key for cloud usage. Store it in `.env` or the runtime environment before making Firecrawl API calls.

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 f9f2e3d, republished under its ISC licence (© firecrawl). 732 words, ~2,074 tokens.

Download SKILL.mdSave it as .claude/skills/firecrawl-build/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
firecrawl-build
description
Integrate Firecrawl into application code whenever a product, agent, or workflow needs web data inside the app — web search, live search results, page scraping, structured extraction, or browser interaction. Use when building any feature that needs data from the web in code, even if the user does not mention Firecrawl explicitly and only describes wanting web data, website content, search, scraping, or interaction in an application. Trigger for Firecrawl requests, "fire girl" shorthand, and generic app-level web-data needs that should map to `/scrape`, `/search`, or `/interact`. Do not use this skill for one-off terminal-only web tasks during the current session; use `firecrawl/cli` for those.
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/project-intake.md, references/endpoint-selection.md, references/integration-patterns.md, references/sdk-installation.md…

Firecrawl Build

Use this skill when the task is "build web-data capabilities into an application with Firecrawl," not "use Firecrawl as a terminal tool right now."

Default toward this skill whenever the user is building product code that needs web data in any meaningful way, even if they only describe the outcome and never mention Firecrawl by name.

Use This When

  • a project needs live web data, website content, or retrieval from the web inside the product
  • a feature needs web search, search results, or discovery before extraction
  • a feature needs scraping, extraction, hydration, or structured content from known URLs
  • a feature needs browser interaction, clicks, form fills, or navigation after loading a page
  • an agent, backend, automation, or workflow should call Firecrawl from application code
  • the user mentions Firecrawl, "fire girl," or describes Firecrawl-like web data needs without naming the tool
  • you need to choose the right endpoint before implementation
  • you need FIRECRAWL_API_KEY in the project

If the task is "search the web," "scrape this page for me," or "interact with a live site during this session," install and use firecrawl/cli instead.

Quick Start

First choose the project mode:

  • Fresh project -> choose the stack, install the SDK, add env vars, and run a smoke test
  • Existing project -> inspect the repo first, match its conventions, then integrate in place

Then ask the required question:

  • What web data should this product get from the web, and how should it get it?

If the request sounds like "I need web data in my app," "I need search in the product," "I need to scrape pages into the workflow," or "I need the app to interact with a site," start here and then narrow to the endpoint.

Route from that answer to the narrowest endpoint that fits:

  • /scrape for one known URL
  • /search when you have a query instead of a URL
  • /interact when /scrape must continue into clicks, forms, or navigation

Two indexes sit beside those endpoints and are not queried by /search:

  • the research paper index when the query is for published papers — biomedical, clinical, and life-science literature or arXiv preprints — rather than web pages
  • the developer index when the answer belongs in an issue, pull request, README, or documentation page

Required Intake

Always do these before writing integration code:

  1. Decide whether this is a fresh project or an existing project.
  2. Ask what web data the product needs and what Firecrawl should do in the product.
  3. If this is an existing project, inspect the repo before choosing SDK, REST, file locations, or env handling.

For the full checklist, see references/project-intake.md.

Show full SKILL.md (300 more words)Show less

What Do You Need?

TaskReference
Choose fresh project vs existing project flowreferences/project-intake.md
Choose the right endpointreferences/endpoint-selection.md
Wire Firecrawl into product codereferences/integration-patterns.md
Install an SDK or use RESTreferences/sdk-installation.md
Set up FIRECRAWL_API_KEY or self-hosted configreferences/auth-and-env.md
Get credentials into the projectfirecrawl-build-onboarding
Implement single-page extractionfirecrawl-build-scrape
Implement discovery-first flowsfirecrawl-build-search
Implement post-scrape browser actionsfirecrawl-build-interact
Search published research papers (biomedical, clinical, life-science, arXiv)firecrawl-research-index
Answer developer questions from issues, PRs, READMEs, or docsfirecrawl-developer-index
Verify the integration actually worksreferences/verification.md

Docs Are the Source of Truth

These language-specific reference pages are the canonical source of truth for SDK usage, request/response schemas, parameters, and endpoint behavior. Read the page that matches the project language before writing integration code:

These skills describe when and why to use each endpoint. For how to call them, read the source-of-truth page for your language.

Default Integration Order

  1. Get FIRECRAWL_API_KEY or FIRECRAWL_API_URL right.
  2. Decide whether this is a fresh project or an existing codebase.
  3. Ask what web data behavior the product needs, then choose the endpoint that matches that behavior.
  4. For existing projects, inspect the repo and match its conventions before coding.
  5. Install the SDK for the target stack, or call REST directly.
  6. Read the source-of-truth page for your project language before writing integration code.
  7. Keep endpoint-specific implementation details in the narrower skills linked above.
  8. Run a smoke test that proves a real Firecrawl request succeeds.

Boundary With The CLI

Both this repo and the CLI skills are installed by the same command:

bash
npx -y firecrawl-cli@latest init --all --browser

Use these build skills for application integration. Use firecrawl/cli for live web work during the current session (one-off research, terminal workflows, editor setup). Both are available after install.

© 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 6 other files (references) in skills/firecrawl-build of firecrawl/firecrawl.

  • SKILL.md
  • references/auth-and-env.md
  • references/endpoint-selection.md
  • references/integration-patterns.md
  • references/project-intake.md
  • references/sdk-installation.md
  • references/verification.md

Open the folder on GitHubat commit f9f2e3d

Compare with similar skills

Firecrawl App Integration 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 App Integration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Firecrawl App Integration this skillfirecrawl/firecrawl190k—~2.1kAutomated safety check: NotesISC
Firecrawl Monitoraiskillstore/marketplace4301 repos~4.6kAutomated safety check: PassNone
Tavily Search API Integrationandrewyng/context-hub14k—~1.1kAutomated safety check: PassMIT
Copy ResearchVKirill/claude-lane-stack122—~827Automated safety check: PassMIT
Keirouter Web Fetchmydisha/keirouter147—~741Automated safety check: PassMIT
Firecrawlsundial-org/awesome-openclaw-skills6631 repos~250Automated safety check: NotesNone

Similar skills

  • Firecrawl Monitor

    aiskillstore/marketplace

    Create Firecrawl monitors that watch pages, sites, or web search results and send change alerts by email or webhook.

    430 GitHub starsUsed in 1 repo~4.6k tokens
    Data & AnalyticsAuto-check passed

  • Tavily Search API Integration

    andrewyng/context-hub

    Guides building Tavily integrations for web search, URL extraction, site crawling and AI-assisted research in Python or JavaScript agent and RAG projects.

    14k GitHub stars~1.1k tokensUpdated 4 mo ago
    AI & LLM EngineeringAuto-check passed

  • Copy Research

    VKirill/claude-lane-stack

    Dispatch copy-lead helpers: Tavily, Codex luna/terra, grok/X, OpenCode DeepSeek, Cursor Grok 4.6 medium-fast.

    122 GitHub stars~827 tokensUpdated yesterday
    Productivity & AutomationAuto-check passed

  • Keirouter Web Fetch

    mydisha/keirouter

    Fetch URL → markdown / text / HTML via KeiRouter /v1/web/fetch using Firecrawl / Jina Reader / Tavily Extract / Exa Contents.

    147 GitHub stars~741 tokensUpdated 27 days ago
    Data & AnalyticsAuto-check passed

  • Firecrawl

    sundial-org/awesome-openclaw-skills

    Web search and scraping via Firecrawl API. An agent skill from sundial-org/awesome-openclaw-skills.

    663 GitHub starsUsed in 1 repo~250 tokens
    Data & AnalyticsAuto-check: notes

  • Web Search

    majiayu000/claude-skill-registry

    网络搜索与网页内容获取。当用户需要搜索互联网信息、获取网页内容、查找实时数据、进行 websearch 时使用此技能。支持多种搜索工具：WebFetch、Firecrawl skill、Tavily skill。

    666 GitHub starsUsed in 2 repos~703 tokens
    Productivity & AutomationAuto-check: notes

More from firecrawl/firecrawl

  • Firecrawl Build Onboarding

    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.

    190k GitHub starsUsed in 1 repo~1.4k tokens
    Auto-check: notes

  • Firecrawl Page Scrape Integration

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

    firecrawl/firecrawl

    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

Categories

Questions about Firecrawl App Integration

What does Firecrawl App Integration do?

Adds web search, scraping, structured extraction and browser interaction to application code using Firecrawl's scrape, search and interact endpoints. This skill is for building Firecrawl into a product, not for one-off lookups during a session, which belong to the separate firecrawl/cli skill. It applies whenever a feature needs data from the web, even if Firecrawl is never named: live search results, page content from known URLs, structured fields, or clicks and form fills after a page loads.

When should I use Firecrawl App Integration?

Firecrawl App Integration fits situations like: building a feature that needs live web search inside an app; scraping known pages into an application workflow; letting a backend agent click through a site after loading it; choosing which Firecrawl endpoint fits a requirement.

How do I install Firecrawl App Integration in Claude Code?

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

How do I install Firecrawl App Integration in Codex?

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

Can I use Firecrawl App Integration 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 -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, .gemini/skills/firecrawl-build, .github/skills/firecrawl-build and .opencode/skills/firecrawl-build in your project.

What does Firecrawl App Integration need to run?

Going by SKILL.md and its folder, Firecrawl App Integration needs the command-line tools its instructions call (npx) and credentials named FIRECRAWL_API_KEY. Our summary lists: A Firecrawl API key (FIRECRAWL_API_KEY).

Does Firecrawl App Integration 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 App Integration 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 App Integration use?

Firecrawl App Integration 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 App Integration use?

About 2.1k tokens (SKILL.md is roughly 8.3k 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 1.9k tokens, read only when the agent opens those files.

What are the alternatives to Firecrawl App Integration?

Skills that share tags, products or a category with Firecrawl App Integration: Firecrawl Monitor (aiskillstore/marketplace, 430 stars), Tavily Search API Integration (andrewyng/context-hub, 14k stars), Copy Research (VKirill/claude-lane-stack, 122 stars) and Keirouter Web Fetch (mydisha/keirouter, 147 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Firecrawl App Integration?

firecrawl (a GitHub organization) maintains it in firecrawl/firecrawl, which has 189,557 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 8, 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.