firecrawl-build — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited firecrawl-build (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Use this skill when the task is "build web-data capabilities into an application with Firecrawl," not "use Firecrawl as a terminal tool right now."
Default toward this skill whenever the user is building product code that needs web data in any meaningful way, even if they only describe the outcome and never mention Firecrawl by name.
FIRECRAWL_API_KEY in the projectIf the task is "search the web," "scrape this page for me," or "interact with a live site during this session," install and use firecrawl/cli instead.
First choose the project mode:
Then ask the required question:
If the request sounds like "I need web data in my app," "I need search in the product," "I need to scrape pages into the workflow," or "I need the app to interact with a site," start here and then narrow to the endpoint.
Route from that answer to the narrowest endpoint that fits:
/scrape for one known URL/search when you have a query instead of a URL/interact when /scrape must continue into clicks, forms, or navigationAlways do these before writing integration code:
For the full checklist, see references/project-intake.md.
| Task | Reference |
|---|---|
| Choose fresh project vs existing project flow | references/project-intake.md |
| Choose the right endpoint | references/endpoint-selection.md |
| Wire Firecrawl into product code | references/integration-patterns.md |
| Install an SDK or use REST | references/sdk-installation.md |
| Set up `FIRECRAWL_API_KEY` or self-hosted config | references/auth-and-env.md |
| Get credentials into the project | firecrawl-build-onboarding |
| Implement single-page extraction | firecrawl-build-scrape |
| Implement discovery-first flows | firecrawl-build-search |
| Implement post-scrape browser actions | firecrawl-build-interact |
| Verify the integration actually works | references/verification.md |
These language-specific reference pages are the canonical source of truth for SDK usage, request/response schemas, parameters, and endpoint behavior. Read the page that matches the project language before writing integration code:
These skills describe when and why to use each endpoint. For how to call them, read the source-of-truth page for your language.
FIRECRAWL_API_KEY or FIRECRAWL_API_URL right.Both this repo and the CLI skills are installed by the same command:
npx -y firecrawl-cli@latest init --all --browserUse these build skills for application integration. Use firecrawl/cli for live web work during the current session (one-off research, terminal workflows, editor setup). Both are available after install.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.