- 01
/plugin marketplace add firecrawl/skills - 02
/plugin install firecrawl@firecrawl-skills
First contact with Firecrawl: it signs you in, gets the key that lets your code call the service, and puts it where the project keeps its other settings.
WHEN TO USE
USE FOR
- Sign into or create a Firecrawl account so a new project has an API key.
- Save a Firecrawl key into a project's environment file for the first time.
- Choose the first SDK or REST path when adding Firecrawl to a project.
- Point an existing project at a self-hosted Firecrawl instance instead of the cloud one.
This is a saved copy of the skill's SKILL.md instructions. It may differ from the upstream file or the version you install.
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 --browserThis 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.comThen 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?
| Task | Reference |
|---|---|
Run the browser auth flow and save FIRECRAWL_API_KEY | references/auth-flow.md |
| Install the right SDK | references/sdk-installation.md |
Put credentials into .env or project config | references/project-setup.md |
| Choose the right endpoint after setup | firecrawl-build |
| Need live web tooling during this task | The CLI skills are already installed from the same command |
| Start implementation from a known URL | firecrawl-build-scrape |
| Start implementation from a query | firecrawl-build-search |
Docs (Source of Truth)
Read the source-of-truth page for your project language for SDK usage, schemas, and examples:
- Node / TypeScript: docs.firecrawl.dev/agent-source-of-truth/node
- Python: docs.firecrawl.dev/agent-source-of-truth/python
- Rust: docs.firecrawl.dev/agent-source-of-truth/rust
- Java: docs.firecrawl.dev/agent-source-of-truth/java
- Elixir: docs.firecrawl.dev/agent-source-of-truth/elixir
- cURL / REST: docs.firecrawl.dev/agent-source-of-truth/curl
After Setup
Once the key is present:
- decide whether this is a fresh project or an existing codebase
- ask what Firecrawl should do in the product
- pick the narrowest endpoint that matches that behavior
- read the source-of-truth page for the project language before writing code
- add the SDK or REST call in code
- run a smoke test that proves one real Firecrawl request succeeds
- use the endpoint-specific skills in this repo for implementation guidance
- if you also need live web tooling during the current task, the CLI skills are already installed — use
firecrawl/cli
Account or credentials required
1 FOR YOU- 01Get a Firecrawl API key
Sign up or sign in to Firecrawl (via the skill's own browser auth flow, or npx firecrawl-cli@latest init --all --browser) to obtain a Firecrawl API key, then add it to the project's .env before any SDK call can run.
You set:
FIRECRAWL_API_KEY
- Setup details
- The README mentions source builds, cloning, containers, hosting, OAuth, service accounts, or cloud projects.
This skill ships inside the Firecrawl Skills plugin. Listed package contents include an MCP server. Installed components and skill versions may vary by AI tool.
Install as a Claude Code plugin
Typed inside the agent's own prompt, not in a terminal. This skill uses files kept elsewhere in its plugin, so install the whole plugin — on its own the skill would be missing them.
The repository is licensed under ISC — use, modification, and redistribution are allowed under that license’s terms.
View the repository’s license file on GitHub →