Firecrawl Dashboard Reporting
Pull KPIs and date-range metrics from analytics dashboards you can legitimately access, without manual copy-paste from each tool.
Overview
Firecrawl Dashboard Reporting is an agent skill most often used in Grow (also Operate monitoring) that extracts structured metrics from authenticated web dashboards via Firecrawl browser.
Install
npx skills add https://github.com/firecrawl/firecrawl-workflows --skill firecrawl-dashboard-reportingWhat is this skill?
- Firecrawl browser flow for authenticated dashboards with date-range setup and tab/section navigation
- Parallel sub-agent pattern for multiple dashboards when appropriate
- Onboarding asks at most 1–3 questions only when URLs, auth, or range are unclear
- Structured metrics extraction from KPI cards, tables, and export buttons when allowed
- Stops and asks for re-auth when sessions expire—no bypass of access controls
- At most 1–3 onboarding questions when blocked
Adoption & trust: 11.6k installs on skills.sh; 29 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your metrics live in several browser-only dashboards and you waste time clicking through date pickers and tables to compile one summary.
Who is it for?
Solo builders who already have dashboard access and want agent-driven KPI pulls with explicit auth handling.
Skip if: Teams that need guaranteed API-level accuracy, bulk historical warehouse exports, or scraping dashboards they do not own or cannot log into.
When should I use this skill?
User needs dashboard reporting, cross-platform metric summaries, authenticated analytics extraction, date-range reports, or structured metrics from web dashboards.
What do I get? / Deliverables
You get a structured cross-dashboard metric summary for the chosen date range, ready to paste into reports or downstream spreadsheets.
- Structured metrics summary for configured date range
- Per-dashboard KPI and table extractions
- Notes on auth or access gaps
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Dashboard reporting is the canonical grow/analytics job—cross-platform metric summaries for solo builders tracking traction after ship. Extracts visible KPI cards, tables, and labels from web analytics UIs—the core analytics subphase deliverable.
Where it fits
Compile Stripe, PostHog, and ads dashboards into one weekly traction snapshot.
Pull error-rate and usage KPIs from an internal ops dashboard after a deploy.
Summarize campaign dashboard metrics for a launch retrospective.
How it compares
Browser-assisted dashboard extraction workflow—not a native Google Analytics or Mixpanel API integration skill.
Common Questions / FAQ
Who is firecrawl-dashboard-reporting for?
Indie founders and solo operators who legitimately use web-based analytics or internal metric dashboards and want an agent to compile visible KPIs into one structured report.
When should I use firecrawl-dashboard-reporting?
Use it during Grow for weekly metrics reviews, during Operate when checking production usage dashboards, or before investor updates when you need date-range summaries from tools that lack a simple export.
Is firecrawl-dashboard-reporting safe to install?
It requires a Firecrawl API key and drives a real browser against URLs you supply; review the Security Audits panel on this page and only point it at accounts and dashboards you are authorized to access.
SKILL.md
READMESKILL.md - Firecrawl Dashboard Reporting
# Firecrawl Dashboard Reporting Use this to extract visible metrics from dashboards the user can legitimately access. ## Onboarding Interview Infer dashboard URLs, metrics, date range, and output format from context. If dashboard targets are clear and accessible, proceed immediately. Ask at most 1-3 concise questions only if blocked, such as the dashboard URLs, auth/profile requirement, or date range. ## Firecrawl Collection Plan Use Firecrawl browser for authenticated dashboards and UI interaction: - open each dashboard - set or verify date range - extract visible KPI cards, tables, and labels - click tabs, expand sections, and scroll tables - use export/download buttons only when appropriate and allowed If login has expired, ask the user to re-authenticate rather than attempting to bypass access controls. ## Parallel Work If appropriate, use sub-agents or equivalent parallel task runners. Split by dashboard platform or metric category. Each researcher should return metrics, units, period, source URL, and caveats. ## Final Deliverable ```markdown # Dashboard Report ## Summary [Highlights, alerts, trends] ## Metrics By Dashboard [Platform, metric, value, unit, change, period] ## Tables Or Exports [Captured tables/files and what they contain] ## Notes And Caveats [Auth issues, chart-only data, unavailable metrics] ## Rerun Inputs workflow: firecrawl-dashboard-reporting dashboards: [urls] date_range: [range] metrics: [list] output: [json/markdown] ``` ## JSON Shape Use `reportedAt`, `dateRange`, `dashboards[]`, `metrics[]`, `tables[]`, `exports[]`, and `summary`. ## Quality Bar - Extract actual numbers, not just chart labels. - Note when a chart cannot be read precisely. - Preserve date ranges and source URLs.