Firecrawl Qa

by firecrawl94cc91229d6cISC185 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 6 weeks ago

QA test a live website with Firecrawl browser and scrape evidence. Use when the user wants exploratory QA, form testing, navigation/link checks, responsive checks, performance observations, bug reports, or a pre-launch quality review.

Instructions onlySoftware Development
AI-generated overview

Runs exploratory QA on a live website with Firecrawl and produces a unified QA report.

What it does
This skill guides an agent through testing a live website using Firecrawl's map, browser, and scrape capabilities. It covers navigation and link checks, form and interaction testing, responsive checks, performance observations, and error states, optionally split across parallel sub-agents. It produces a structured markdown QA report with a health score, issues by severity, reproduction steps, positive observations, pages tested, and rerun inputs.
When to use it
Use it when the user wants exploratory QA of a live site, form testing, navigation or link checks, responsive checks, performance observations, bug reports, or a pre-launch quality review.
Requirements
Requires a Firecrawl API key (FIRECRAWL_API_KEY) for hosted Firecrawl requests and network access to the target site. It ships no scripts; it is instructions only. Credentials may also be needed for protected flows.

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 Inputsworkflow: firecrawl-qaurl: [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 and attribution

Source:firecrawl/firecrawl-workflowsinskills/firecrawl-qaat commit94cc912

License: ISC

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Firecrawl Qa Agent Skill | SourceWeft