Firecrawl Onboarding
Get Firecrawl credentials and SDK setup into a project — API key into .env, SDK choice, and docs for a new integration
- What
- Get Firecrawl credentials and SDK setup into a project — API key into .env, SDK choice, and docs for a new integration
- Cost
- Free
- Needs
- a Firecrawl account and API key (FIRECRAWL_API_KEY) — hosted plans are paid; the skill stores it in .env and never displays it
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — an official Firecrawl onboarding skill: it gets Firecrawl credentials and SDK setup into a project — adding `FIRECRAWL_API_KEY` to `.env`, choosing the first SDK, and pointing to the right docs for a new integration. It includes its own browser auth flow, so it does not depend on a separate website-onboarding skill. Companion to the scrape, search, and interact skills — install this one first when starting a fresh Firecrawl integration. By @firecrawl, listed here with credit to its creator. Honest caveats: setup guidance only — you still need a Firecrawl account and API key (hosted plans are paid); the skill handles the key as a declared input and never displays it. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a Firecrawl account and API key (FIRECRAWL_API_KEY) — hosted plans are paid; the skill stores it in .env and never displays it Install "Firecrawl Onboarding" for me. Get Firecrawl credentials and SDK setup into a project — API key into .env, SDK choice, and docs for a new integration Repository: https://github.com/firecrawl/skills/blob/main/skills/build/firecrawl-build-onboarding/SKILL.md 1. Fetch the SKILL.md file for the firecrawl-firecrawl-build-onboarding skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "firecrawl-firecrawl-build-onboarding". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.