Agent skill · writing content · jeremylongshore
firecrawl-core-workflow-a
Implement current Firecrawl v2 scrape and crawl flows with bounded discovery, pagination, content validation, and durable receipts. Use when collecting one page or a governed site corpus. Trigger with "Firecrawl scrape", "crawl this site", or "build a Firecrawl corpus".
Why this skill is useful
Provides specific commands and workflows for scraping and crawling websites into LLM-ready markdown that the AI wouldn't reliably generate on its own.
What it needs
Requires @mendable/firecrawl-js installed locally. Requires firecrawl account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Firecrawl Scrape and Crawl Workflow Overview Use scrape for one URL and crawl for recursive discovery. Keep the authorization basis, scope, cost ceiling, result completeness, and storage decision explicit. Prerequisites The target repository or integration path and the requested operator outcome. The source authorization, data classification, and environment policy. Current Firecrawl documentation, credentials only when needed, and an owner for approvals. Current Contract The current Node client is Firecrawl from the firecrawl package; Python uses Firecrawl from firecrawl-py. Use scrape for a single URL, crawl as the waiter, startCrawl for asynchronous submission, getCrawlStatus for status and pagination, and cancelCrawl for cancellation. REST uses the /v2 routes and Bearer authentication. Authentication For authenticated Cloud operations, inject FIRECRAWLAPIKEY from an approved secret manager. REST requests use Authorization: Bearer with the key. Never print, commit, transmit, or place a key in a URL. Keyless access is suitable only where the current documentation explicitly allows it and the workload accepts its limits; production workflows should make identity and team ownership explicit. Instructions 1. Confirm the target is authorized, normalize its origin, and document allowed paths, excluded paths, subdomain/external-link policy, desired formats, and freshness. 2. Create the client from FIRECRAWLAPIKEY for authenticated work. Keep the key in a secret manager and never place it in source, arguments, logs, or generated examples. 3. For one page, call scrape with only the required formats and options. Validate the returned document, metadata.sourceURL, metadata.statusCode, and required content fields. 4. For a site, set an explicit crawl limit and path/depth policy. Use crawl when blocking is acceptable or startCrawl when another worker owns status and cancellation. 5. Retrieve every required result page. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/firecrawl-core-workflow-a--00a2c1