Firecrawl Build Onboarding

OrganizationPopular

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.

Overview

Publisher	firecrawl
Repository	`firecrawl`
Skill name	`firecrawl-build-onboarding`
Stars	181.6K
Forks	9.8K
Bundled files	3
License	ISC
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
3 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by firecrawl on GitHub. Read the source before you install it.

Installation

Install the Firecrawl Build Onboarding AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/firecrawl/firecrawl.git /tmp/firecrawl
mkdir -p .claude/skills
cp -r /tmp/firecrawl/skills/firecrawl-build-onboarding .claude/skills/firecrawl-build-onboarding

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Firecrawl Build Onboarding in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Firecrawl Build Onboarding on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Firecrawl Build Onboarding is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

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

dotenv
FIRECRAWL_API_KEY=fc-...

If the project is self-hosted, also set:

dotenv
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

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Firecrawl Build Onboarding AI skill do?

Why use Firecrawl Build Onboarding on TypingMind?

Because you install it once and use it with any model. Firecrawl Build Onboarding is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Firecrawl Build Onboarding in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/firecrawl/firecrawl/tree/main/skills/firecrawl-build-onboarding. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Firecrawl Build Onboarding?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Firecrawl Build Onboarding?

As many as you like. As long as a model supports skills, you can use Firecrawl Build Onboarding with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Firecrawl Build Onboarding AI skill free?

Yes. It is published on GitHub by firecrawl under the ISC license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Receiving Code Review

obra

CommunityPopular

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative…

Requesting Code Review

obra

CommunityPopular

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Systematic Debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Test Driven Development

obra

CommunityPopular

Use when implementing any feature or bugfix, before writing implementation code

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Firecrawl Build Onboarding

Install

Use This When

Quick Start

What Do You Need?

Docs (Source of Truth)

After Setup

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now