firecrawl-qa — Claude Code skill: QA a live website
Drives a deployed site with the Firecrawl browser and writes up what broke: links, forms, mobile layout, console errors. Built for pre-launch passes and post-deploy checks.
npx skills add firecrawl/firecrawl-workflows --skill firecrawl-qa -a claude-codeWhat firecrawl-qa does
The skill tests a deployed site and hands back one QA report. Three Firecrawl pieces do the work: map lists the pages, browser clicks through navigation, fills forms and switches viewports, scrape pulls page content and links.
Testing splits across parallel runners, with separate sets for a full pass, forms, navigation, responsive checks and performance. Each tester returns severity, URL, description, evidence and reproduction steps; findings are deduplicated before anything reaches the report. You get a health score, the pages tested, issues sorted into critical, major and minor, plus a Rerun Inputs block so the same run can be repeated with the same focus.
A FIRECRAWL_API_KEY is required — requests go to hosted Firecrawl, so without it nothing runs. Testers only report what they reproduced, which means a hunch about a slow page stays out of the report until there is evidence behind it. For protected flows, plan on supplying credentials up front.
What it helps with
- check links and routing before a release
- exercise forms: submit, validate, break
- spot layout breaks on mobile and tablet
- gather console errors and load timings into one report
- re-check production right after a deploy
Example prompts for the agent
- Run
firecrawl-qaagainst staging, focus on forms and validation. - Check responsive layout with
firecrawl-qa: desktop, tablet, mobile. firecrawl-qaon prod after deploy, short report on console errors only.
How to install firecrawl-qa
1Skills CLI (Vercel)
npx skills add firecrawl/firecrawl-workflows --skill firecrawl-qa -a claude-code2Manually: put the files in place
~/.claude/skills/firecrawl-qa/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/firecrawl-qa/
1Skills CLI (Vercel)
npx skills add firecrawl/firecrawl-workflows --skill firecrawl-qa -a codex2Manually: put the files in place
.agents/skills/firecrawl-qa/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add firecrawl/firecrawl-workflows --skill firecrawl-qa -a cursor2Manually: put the files in place
.cursor/skills/firecrawl-qa/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install firecrawl/firecrawl-workflows firecrawl-qa2Manually: put the files in place
.github/skills/firecrawl-qa/SKILL.md1Skills CLI (Vercel)
npx skills add firecrawl/firecrawl-workflows --skill firecrawl-qa -a gemini-cli2Platform CLI
gemini skills install https://github.com/firecrawl/firecrawl-workflows --path skills/firecrawl-qaManually: put the files in place
.devin/skills/firecrawl-qa/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add firecrawl/firecrawl-workflows --skill firecrawl-qa -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about firecrawl-qa
How do I install firecrawl-qa in Claude Code?
Run npx skills add firecrawl/firecrawl-workflows --skill firecrawl-qa -a claude-code. The skill file lands at ~/.claude/skills/firecrawl-qa/SKILL.md.
What does firecrawl-qa do?
It walks a live site with Firecrawl tooling and returns a QA report covering broken links, form behaviour, mobile layout, page load and console errors.
What do I need for it to work?
FIRECRAWL_API_KEY is required, since requests go to hosted Firecrawl. Without the key no tester starts.
Source text
SKILL.md · ISC
---
name: firecrawl-qa
description: "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."
license: ISC
metadata:
author: firecrawl
version: "0.1.0"
homepage: https://www.firecrawl.dev
source: https://github.com/firecrawl/firecrawl-workflows
inputs:
- name: FIRECRAWL_API_KEY
description: Firecrawl API key for hosted Firecrawl requests.
required: true
---
# Firecrawl QA
Use this to test a live site and return a unified QA report.
## Onboarding Interview
Infer the URL, QA focus, and output format from context. If the target URL is clear, proceed immediately.
Ask at most 1-3 concise questions only if blocked, such as the URL, the focus area, or credentials/constraints for protected flows.
## Firecrawl Collection Plan
Use Firecrawl map to discover pages. Use Firecrawl browser for interactions, forms, navigation, and responsive/manual checks when available. Use scrape for page content and link extraction.
## Parallel Work
If appropriate, use sub-agents or equivalent parallel task runners:
- Full: Navigation and Links, Forms and Interactions, Content and Visual, Error States.
- Forms: Form Discovery, Happy Path, Edge Cases, Validation.
- Navigation: Sitemap, Nav Testing, Link Checker, Routing.
- Responsive: Desktop, Tablet, Mobile, Interaction.
- Performance: Page Load, Asset Audit, Content Efficiency, Comparison.
Each tester should return severity, URL, description, evidence, and reproduction steps.
## Final Deliverable
```markdown
# QA Report: [Site]
## Summary
- Health score: [x/10]
- Pages tested: [count]
- Issues found: [critical/major/minor]
## Critical Issues
[C-1] URL | Description | Steps to reproduce | Expected vs actual
## Major Issues
[M-1] URL | Description | Steps to reproduce
## Minor Issues
[m-1] URL | Description
## Positive Observations
[What works well]
## Pages Tested
[URLs]
## Agent/Test Summary
[Who tested what]
## Rerun Inputs
workflow: firecrawl-qa
url: [url]
focus: [full/forms/navigation/responsive/performance]
```
## Quality Bar
- Include reproduction steps for functional issues.
- Do not report speculative bugs without evidence.
- Deduplicate findings across testers.
© firecrawl · ISC · firecrawl/firecrawl-workflows
