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.
Works with
--- name: firecrawl-build-onboarding description: 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. license: ISC --- # 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](references/auth-flow.md) | | **Install the right SDK** | [references/sdk-installation.md](references/sdk-installation.md) | | **Put credentials into `.env` or project config** | [references/project-setup.md](references/project-setup.md) | | **Choose the right endpoint after setup** | [firecrawl-build](../firecrawl-build/SKILL.md) | | **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](../firecrawl-build-scrape/SKILL.md) | | **Start implementation from a query** | [firecrawl-build-search](../firecrawl-build-search/SKILL.md) | ## 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](https://docs.firecrawl.dev/agent-source-of-truth/node) - **Python**: [docs.firecrawl.dev/agent-source-of-truth/python](https://docs.firecrawl.dev/agent-source-of-truth/python) - **Rust**: [docs.firecrawl.dev/agent-source-of-truth/rust](https://docs.firecrawl.dev/agent-source-of-truth/rust) - **Java**: [docs.firecrawl.dev/agent-source-of-truth/java](https://docs.firecrawl.dev/agent-source-of-truth/java) - **Elixir**: [docs.firecrawl.dev/agent-source-of-truth/elixir](https://docs.firecrawl.dev/agent-source-of-truth/elixir) - **cURL / REST**: [docs.firecrawl.dev/agent-source-of-truth/curl](https://docs.firecrawl.dev/agent-source-of-truth/curl) ## 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`
More Project Management skills
email-sequence
coreyhaines31/marketingskills
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.
onboard
pbakaus/impeccable
Designs and improves onboarding flows, empty states, and first-run experiences to help users reach value quickly. Use when the user mentions onboarding, first-time users, empty states, activation, getting started, or new user flows.
harden
pbakaus/impeccable
Make interfaces production-ready: error handling, empty states, onboarding flows, i18n, text overflow, and edge case management. Use when the user asks to harden, make production-ready, handle edge cases, add error states, design empty states, improve onboarding, or fix overflow and i18n issues.

