/firecrawl-qa
Firecrawl API key for hosted Firecrawl requests.
$ npx -y skills add firecrawl/firecrawl-workflows --skill firecrawl-qa --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/firecrawl-qa
Context preview
The summary Claude sees to decide when to auto-load this skill.
Firecrawl API key for hosted Firecrawl requests.
SKILL.md
firecrawl-qa.SKILL.mdname: 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: trueFirecrawl 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
# 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.
Read more
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: trueFirecrawl 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
# 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.
Source of truth for Firecrawl workflow skills — outcome-focused skills for AI coding agents: research reports, SEO audits, QA reports, knowledge bases, lead lists, and agent-ready website design systems.

