Firecrawl Workflows: 16 outcome-oriented skills that produce reports

Who it's for

Use this set when you want an AI coding Agent to hand back a finished Firecrawl workflow artifact, not just call the low-level crawl API. Official text calls this the source of truth for Firecrawl workflow skills, covering research reports, SEO audits, QA reports, knowledge bases, lead rosters, and site design systems an Agent can use. There are 16 workflow skills. It fits people who already have a clear deliverable and can accept the Agent visiting public pages. The page does not write secret variable names; do not invent them. When credentials are needed, follow the skill notes after install. If what you want to change is the CLI skill family (including research/developer indexes), official text points to firecrawl/cli, not a change in this repo.

First try in 3 minutes

Use only the official preferred install, the full catalog (which includes these workflows):

npx skills add firecrawl/skills

The same page says installing directly from this repository also works and provides the same 16 workflows:

npx skills add firecrawl/firecrawl-workflows

The first time, use the first command. Do not splice the two into one, and do not invent a catalog. Continuous integration mirrors this repo’s skills/ into firecrawl/skills; that is the promoted install entry, not an alternate spelling of the second command.

After install, do a low-risk check first. Have the Agent say: if the goal is a short research report, which kind of workflow it will use, which URLs you supplied it will visit, and whether it will write files. Have it repeat “plan only, no crawl yet”. After you confirm the URLs are real and allowed, permit execution. Success is the Agent organizing steps by workflow skills, not inventing undocumented short skill names. Do not start with a lead roster or a whole-site design system on the first try; those have larger side effects.

Use cases

Case 1: Research report or knowledge base. Give the Agent a topic and the URLs you allow it to crawl; require a research report or structured knowledge base via the workflow. For people who need public pages folded into one readable packet. The page gives no report template, so layout follows the actual output. Before running, confirm it will not crawl addresses you did not provide.

Case 2: QA report or SEO audit. Hand the Agent live pages and require a quality check or SEO audit via the workflow. For post-launch checks of public pages, not code changes. An audit visits the target site; confirm the domain first. The page places QA reports and SEO audits side by side in the outcome list, but gives no item checklist; do not invent required coverage. Lead rosters and site design systems are in the same list; evidence only goes as far as “these are output types among the 16 workflows”, with no step-by-step operations.

Boundaries

Preferred install is npx skills add firecrawl/skills. This repo’s command provides the same 16 skills when you do not go through the catalog. Workflows are written in this repo; changes to the CLI skill family point to:

https://github.com/firecrawl/cli

Catalog repo:

https://github.com/firecrawl/skills

Do not invent secret variables or short skill names. No client is named, so do not infer exclusive support. Crawling and writing reports both have side effects; confirm first. Repository page:

https://github.com/firecrawl/firecrawl-workflows