firecrawl-qa Skill for Claude: What It Does and How to Install It
Makes your agent test a live website with a Firecrawl browser and write up what is broken, with steps to reproduce.
- Installs
- 31.5K
- on skills.sh
- Stars
- 214
- on GitHub
- Updated
- Nov 2026
- last repo commit
This skill makes your agent test a live site and return one QA report. It maps the site's pages, uses a Firecrawl browser for forms, navigation and responsive checks, and scrapes pages for content and links.
You can focus on full, forms, navigation, responsive or performance. The report groups issues as critical, major or minor with steps to reproduce. It needs a Firecrawl API key and the Firecrawl CLI.
Good for
- Developers running a pre-launch check on a deployed site
- QA engineers who want a first-pass bug report
- Site owners confirming a release works
Install firecrawl-qa
Claude Code
- 1
Copy this prompt.
Install the firecrawl-qa skill in Claude Code. Run this command: /plugin marketplace add firecrawl/firecrawl-workflows /plugin install firecrawl-workflows@firecrawl-workflows Then check that it loaded and tell me how to use it.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
Pick one route. The plugin routes install the whole firecrawl-workflows plugin: 16 skills (counted from the skills list in its plugin.json), and the repo tree has no hooks, agents or MCP config files. The skills-only routes install just firecrawl-qa. The skill drives the Firecrawl CLI and needs a Firecrawl API key. Install the Firecrawl CLI first, since the skill runs firecrawl commands: npm install -g firecrawl-cli (Firecrawl CLI docs), or npx -y firecrawl-cli@latest init -y --browser to install it, sign in and add the shared skills in one step. Then run firecrawl login or export FIRECRAWL_API_KEY. Who pays: the Firecrawl account that owns the key. Every call uses credits; a new account starts on the free plan with 1,000 credits a month and no card. Per Firecrawl's billing docs: map 1 credit per call; scrape 1 credit per page; Interact (browser sessions) 2 to 7 credits per browser minute.
Built from the package data we hold. Not yet tested by us. Source.
What's in the skill
When it loads
Test a live website with Firecrawl browser and write up what's broken: links, forms, mobile layout, performance and console errors. Use for pre-launch checks, bug hunts or confirming a deployed site works.
Sections in SKILL.md
- Onboarding Interview
- Firecrawl Collection Plan
- Parallel Work
- Final Deliverable
- Summary
- Critical Issues
- Major Issues
- Minor Issues
- Positive Observations
- Pages Tested
- Agent/Test Summary
- Rerun Inputs
- Quality Bar
Key facts
- Installs on skills.sh
- 31,495 (Nov 2, 2026)
- Last repo commit
- Nov 1, 2026
- What it includes
- 1 file: SKILL.md (bundles no scripts)
What it includes
Uses Firecrawl map to find the site's pages
Content and link extraction use scrape.
Network ·
Discover pagesNavigation and Links, Forms and Interactions, Content and Visual, Error States
Four tester roles when your agent supports sub-agents.
Network ·
Full focusForm Discovery, Happy Path, Edge Cases, Validation
Interacts with forms in a browser. Tell the agent which test data and credentials to use.
Network ·
Forms focusSitemap, Nav Testing, Link Checker, Routing
Four tester roles named in SKILL.md.
Network ·
Navigation focusDesktop, Tablet, Mobile, Interaction
Four tester roles named in SKILL.md.
Network ·
Responsive focusPage Load, Asset Audit, Content Efficiency, Comparison
Four tester roles named in SKILL.md.
Network ·
Performance focusSummary with health score out of 10, then critical, major and minor issues
Also lists positive observations, pages tested, who tested what and rerun inputs. It asks for reproduction steps and no speculative bugs.
Read ·
QA report
From the official docs
Permissions
Medium risk
It drives a browser through the live site you name, including its forms. Test on a staging copy or with test data where you can.
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
The Forms focus interacts with live forms
SKILL.md lists Happy Path and Edge Cases checks and does not say what happens to submitted data. Use a staging site or test data. github.com
Protected flows need credentials from you
SKILL.md says to ask for credentials or constraints. Use a test account and avoid your own. github.com
It spends your Firecrawl credits
Every call is billed in credits to the account behind the key. Per Firecrawl's billing docs: map 1 credit per call; scrape 1 credit per page; Interact (browser sessions) 2 to 7 credits per browser minute. A free account has 1,000 credits a month, so a large run can use it up. docs.firecrawl.dev
Security advisories
No published security advisories as of Nov 2, 2026.
Technical details
| Turning on read-only | No read-only mode is documented in SKILL.md. Use version control for files it writes. |
|---|---|
| Talks to | Firecrawl hosted service. The live site you test |
| Sign-in and keys | SKILL.md declares FIRECRAWL_API_KEY as a required input and asks you for credentials for protected flows. It does not say where either is kept. |
| Scopes |
|
Questions
What does the firecrawl-qa skill do?
It makes your agent test a live website and write a QA report. It checks links, forms, mobile layout, performance and console errors and lists issues by severity with reproduction steps.
How do I install it in Claude Code or Codex?
Use the install box at the top of this page. Each client has a plugin route and skills CLI commands. Install the Firecrawl CLI first (npm install -g firecrawl-cli, per its docs), then run firecrawl login or set FIRECRAWL_API_KEY.
Who pays for it?
You do, through the Firecrawl account that owns your API key. Firecrawl bills in credits, and a new account starts on the free plan with 1,000 credits a month and no card. Per its billing docs: map 1 credit per call; scrape 1 credit per page; Interact (browser sessions) 2 to 7 credits per browser minute. Check your balance with firecrawl credit-usage.
Can it test pages behind a login?
SKILL.md says to ask you for credentials or constraints for protected flows. Use a test account, and tell the agent what it may and may not submit.
Will it submit forms on my live site?
Its Forms focus lists Happy Path and Edge Cases checks, which means form interaction in a browser. SKILL.md does not say what happens to submitted data, so point it at a staging site or use test data.
What does the health score mean?
The report template has a Health score of x/10 in its summary. SKILL.md gives no formula for it.
Is it safe to install?
It is a single SKILL.md file and bundles no scripts. When it runs, your agent drives a browser on the site you name through Firecrawl. Run it on a staging copy where you can.
Information
updated Nov 2, 2026
- Repository
- firecrawl/firecrawl-workflows
- Folder
skills/firecrawl-qa
Sources
Docs, issue trackers and discussions this page is built from.
Show all 8Hide
- firecrawl-qa SKILL.md · github.com
- firecrawl-workflows README · github.com
- firecrawl-workflows plugin.json · github.com
- firecrawl-workflows marketplace.json · github.com
- firecrawl-workflows Codex plugin.json · github.com
- Firecrawl CLI docs · docs.firecrawl.dev
- Firecrawl billing and credits · docs.firecrawl.dev
- firecrawl/cli README · github.com