firecrawl-qa
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.
- Installs
- 31.4K
- Last 24h
- +23
- Trending rank
- #5194
- Security
- Warn
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/firecrawl/firecrawl-workflows --skill firecrawl-qa- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads firecrawl-qa automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
Security audits
Independent scans of the skill's instructions and bundled files.
SKILL.md
The instructions your agent reads when the skill is triggered.
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
# 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.
FAQ
What does the firecrawl-qa skill do?
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.
How do I install firecrawl-qa?
Run npx skills add https://github.com/firecrawl/firecrawl-workflows --skill firecrawl-qa in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/firecrawl-qa/ (personal) or .claude/skills/firecrawl-qa/ (project).
Which AI agents can use firecrawl-qa?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is firecrawl-qa safe to install?
Security partners have reviewed it: Gen Agent Trust Hub passed; Socket passed; Snyk flagged items to review. As with any skill, read the SKILL.md and bundled scripts before installing.
Who maintains firecrawl-qa?
It is published by firecrawl in firecrawl/firecrawl-workflows, and it is an official skill from the maker of the technology it covers. It has 31,395 recorded installs.
More from firecrawl/firecrawl-workflows
firecrawl-deep-research
firecrawl/firecrawl-workflows
Produce an intensive, cited analytical report: executive summary, multi-angle findings, contrarian views, open questions, and full sources. Use only when the user needs rigorous synthesis of a complex topic (scientific, technical, policy, or market-analytical) that cannot be answered with a short search, and wants a formal written report, not a recommendation list. Do not use for product picks, top-N lists, quick lookups, or routine "find out about X" tasks. If the request does not clearly need this kind of report, do not use this skill. Do not use for a literature review over published papers. This skill collects evidence from the open web. A request for the literature on a biomedical, clinical, life-science, or other scientific topic — papers, studies, trials, preprints — belongs to firecrawl-research-papers, which queries Firecrawl's paper index (PubMed, bioRxiv, medRxiv, arXiv) instead of searching websites.
firecrawl-research-papers
firecrawl/firecrawl-workflows
Find and synthesize research papers, whitepapers, PDFs, technical reports, and academic sources with Firecrawl Research, using semantic paper search, related-paper expansion, and in-body verification over Firecrawl's paper index — largely biomedical and life-science literature from PubMed, bioRxiv, and medRxiv, plus arXiv preprints in CS, physics, and math. Use when the user wants a literature review, systematic review, survey of studies, paper summary, research landscape, or sourced synthesis from scholarly and industry publications, including clinical, drug, gene, disease, epidemiology, and public-health topics. Prefer this over a general web-research workflow whenever the evidence base is published papers rather than web pages.
firecrawl-website-design-clone
firecrawl/firecrawl-workflows
Extract an existing website's visual system into DESIGN.md, or collect its existing logo, colors, fonts and homepage messaging for a document. Use for reference-based UI implementation, documenting design patterns, or matching a presentation to a company's website. Excludes inventing a new brand or brand positioning.
firecrawl-workflows
firecrawl/firecrawl-workflows
Run focused Firecrawl workflows for research, documentation lookup, SEO audits, QA, lead discovery and enrichment, business contacts, current jobs, fantasy decisions, brand assets, knowledge bases and website design systems. Use when the user wants a sourced answer or deliverable from a workflow rather than raw extraction or product-code integration.
firecrawl-knowledge-base
firecrawl/firecrawl-workflows
Build a knowledge base from web content with Firecrawl. Use for local reference docs, RAG-ready chunks, fine-tuning datasets, documentation mirrors, topic corpora, or LLM-ready markdown organized from web sources.
firecrawl-market-research
firecrawl/firecrawl-workflows
Research markets and companies with Firecrawl using current, cited figures: market size, growth, trends, financials and earnings. Use when the user asks for market research, an industry overview or a comparison of companies by the numbers, since these figures change faster than training data.
Popular testing & qa skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
grilling
mattpocock/skills
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
migrate-to-shoehorn
mattpocock/skills
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
run-train
lllllllama/rigorpilot-skills
Rigor Train skill for deep learning research repositories. Use when a documented or selected training command should be run conservatively for startup verification, short-run verification, full kickoff, or resume, with command, config, seed, log, checkpoint, status, and metric evidence written to standardized trainoutputs/. Do not use for environment setup, exploratory sweeps, speculative idea implementation, or end-to-end orchestration.
test-driven-development
obra/superpowers
Use when implementing any feature or bugfix, before writing implementation code
finishing-a-development-branch
obra/superpowers
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work