Teste sites ao vivo com Firecrawl QA

O que esta skill faz

A skill combina map, browser e scrape do Firecrawl para testar um site publicado. O relatório pode cobrir navegação, formulários, conteúdo, estados de erro, responsividade e observações de desempenho.

Quando usar

• Executar QA exploratório antes de um lançamento
• Testar formulários e suas validações
• Verificar navegação, rotas e links
• Observar o site em tamanhos desktop, tablet e mobile
• Documentar bugs com severidade e passos de reprodução

Como usar

1. Informe a URL, o foco do teste e as restrições de acesso
2. Configure FIRECRAWL_API_KEY e credenciais autorizadas quando necessárias
3. Mapeie as páginas e execute os fluxos relevantes no browser
4. Registre URL, evidência, severidade e passos para cada problema
5. Revise o repositório quando disponível para contextualizar, sem alterar o diagnóstico observado

O que revisar antes de instalar

• Observações de desempenho não equivalem necessariamente a uma medição laboratorial completa
• Fluxos protegidos exigem credenciais e autorização válidas
• O relatório cobre apenas páginas, estados e tamanhos efetivamente testados

SKILL.md

---
name: firecrawl-qa
description: 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.
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.