Firecrawl Build Onboarding Agent Skill
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.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/firecrawl/skills --skill firecrawl-build-onboardingWhat comes with it
1 887 bytes besides the instructionThe instruction itself
7 sections, as written by the authorFirecrawl 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?
| 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
Other skills for the same job
different authors, same section of the catalogue
Searches Meta Ad Library (Facebook/Instagram/WhatsApp ads) by keyword or Facebook page ID and extracts ad details including creatives, copy, CTA, publisher platforms, spend, impressions, reach estimates, and page transparency info. Use when user mentions Meta Ad Library, Facebook ads scraper, Instagram ads data, FB ad library, search Facebook ads, get ads from a Facebook page, scrape Meta ads, Facebook advertising data, ad creative extraction, competitor ads analysis, brand ads monitoring, Meta advertising transparency, political ads Facebook, housing ads Facebook, view all ads from a page, facebook ads search, fb ads library api, facebook ad archive, instagram ad data, get ad creatives.
> Scrapes LinkedIn job postings using the JobSpy library (python-jobspy). Use this skill whenever the user wants to find jobs on LinkedIn, search for open roles, pull job listings, build a job pipeline, source job targets for GTM research, or monitor hiring signals. Even if the user just says "find me some jobs" or "what roles is [company] hiring for", use this skill. It runs a local Python script that outputs a CSV of job postings with title, company, location, salary, job type, description, and direct URLs.
When the user wants to fix indexing issues from Search Console, use noindex, or implement Google Indexing API. Also use when the user mentions "fix indexing," "not indexed," "Crawled - currently not indexed," "discovered - currently not indexed," "index coverage," "noindex," "noindex tag," "pages not indexed," "why not indexed," "request indexing," or "Google Indexing API." For sitemap, use xml-sitemap.
| Discover and list all URLs on a website without extracting content, via the Tavily CLI. Use this skill when the user wants to find a specific page on a large site, list all URLs, see the site structure, find where something is on a domain, or says "map the site", "find the URL for", "what pages are on", "list all pages", or "site structure". Faster than crawling — returns URLs only. Essential when you know the site but not the exact page. Combine with extract for targeted content retrieval.
Use when the user needs X (Twitter) data or confirmation-gated X actions through Xquik: tweet search, user lookup, follower extraction, media download, monitoring, webhooks, MCP, SDKs, posting, likes, DMs, and profile updates. Requires a Xquik API key. Never ask for X login material.
Look up official company data from European public registries across 11 countries/regions (CZ, SK, PL, DE, UK, NL, RO, HR, SE + EU-level + ESG). Covers company registration, ownership, financial filings, VAT status, ESG data. Use when the user asks to "look up a company", "check registry", "find company info", "look up IČO/KRS/LEI/CRN", "company due diligence", "check VAT status", "find ownership structure", or needs official data from European registries. Reads tracked companies from data/companies.json. Some lookups use Python scripts (stdlib), some fall back to Apify actors for scraping-based registries.
Use Xquik for X data workflows: tweet search, user lookup, follower export, media downloads, monitors, webhooks, REST API, MCP, SDK setup, and approval-gated account actions.
Use Xquik for X/Twitter REST, MCP, SDKs, search, filtered exports, monitoring & approved publishing. Not affiliated with X Corp. Trigger for X API alternatives, pricing comparisons, tweet search, user lookup, timelines, follower exports, media, webhooks, bulk extraction, giveaways, or MCP setup. Read-only by default. Require explicit approval for writes, private reads, monitors, webhooks & metered bulk jobs.
How to use it
Take firecrawl/firecrawl-build-onboarding from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.
The instructions reference npx.
Without those the skill loads but fails at the first command.