firecrawl
The front door to Firecrawl's web tools: say what you want off the internet in plain words, and it picks the right tool for the job and runs it.
Firecrawl's own command-line program for pulling pages off the web, and the instructions that teach a coding assistant to drive it.
Firecrawl is a web service that fetches pages and hands back clean text. This package is the terminal program that calls it, plus 13 sets of instructions that put that program in reach of whichever editor you write code in.
One init command installs the program, signs you in, and fits the instructions to every editor it finds on the machine — Cursor, Claude Code, Windsurf — rather than to one of them.
The 13 split five ways:
So most of them are about reaching a page at all, and the index skills cover the questions a page search answers badly.
Firecrawl's instructions come in three segments:
firecrawl setup skills fetches the first, firecrawl setup workflows the third.
Showing all 13 skills
For when the thing you want is somewhere on the internet and you do not know the address. One of these three is the catch-all entry point: given a request in plain words it decides which of the rest to start, so an assistant that has been told nothing specific begins here.
The front door to Firecrawl's web tools: say what you want off the internet in plain words, and it picks the right tool for the job and runs it.
You know the site but not which page on it — this pulls up the full list of its page addresses and lets you search that list for the one you want.
Search the web by asking your real question, and get back not just links and excerpts but, if you want, the full text of every page it found.
Once an address is in hand, these turn it into words: the one page you named, every page under a section of a site, or a named set of fields filled in from however many pages that takes.
Set it loose on a website and a few minutes later it comes back with the specific facts you asked for, gathered from however many pages it had to visit.
Instead of opening a site's pages one by one, this collects a whole section in a single run and hands back all the text together.
Give it a web address and it hands back that page's text, tidied up and saved to a file — including pages that only fill themselves in once a browser loads them.
Two cases a plain fetch cannot settle. A site that shows nothing until somebody logs in, clicks or scrolls through to the next lot. And a site whose value is in how it changes, so something has to keep looking and say when it does.
Some pages give up nothing until someone clicks. This one works the page the way a person would — logging in, filling in a form, moving to the next page — until what you wanted is on screen.
Keeps checking a page, a whole site, or even the open web on a schedule you set, and emails you the moment something you care about changes or shows up.
These two finish with files rather than with words in the conversation: a whole site saved for reading with no internet, and a document you already have — a PDF, a spreadsheet — turned into something plain.
A copy of a website on your own computer: every page saved as a file you can open when you're offline, with screenshots if you ask for them.
Takes a document already sitting on your computer — a PDF, a Word file, a spreadsheet — and turns it into plain readable text, or just answers a question about what's inside.
Three ways round the open web: a directory of ready-made workflows and data sources, an index of public code, issues and documentation for programming questions, and a paper index weighted to biomedical and life-science research.
Before reading a website page by page, this checks Firecrawl's catalogue of ready-made data sources for one that already covers that site, and gets the information back as tidy, organised data instead.
Answers programming questions from the original source — the bug report where a problem was filed, the merged change that fixed it, the official page that says how something works — rather than from a blog post describing it.
Finds the research papers that answer a question — mostly medical and life-science journals and preprints, plus computer science, physics and maths — and brings back the neighbouring papers around the best match, not just one.
Every command goes through a Firecrawl account: sign in through the browser the first time, or put a key in FIRECRAWL_API_KEY. Pointed at a Firecrawl you run yourself with --api-url, it skips the sign-in entirely. Every command spends credits from that account; an agent job can be capped with --max-credits, and fails rather than go over.
One setup step changes settings rather than adding files:
INSTALL
npx -y firecrawl-cli@latest init --all --browser