π³ Firecrawl Dashboard Reporting
Extract visible metrics from authenticated dashboards into dated reports with period, units and caveats
- What
- Extract visible metrics from authenticated dashboards into dated reports with period, units and caveats
- Cost
- Free
- Needs
- a Firecrawl API key (the hosted service is paid β usage-based credits; set it via the secure vault or an environment variable, never in chat); legitimate access to the dashboards you want reported on
- Install
- Copy the installer prompt below into your Muse β your agent does the rest.
π³ Requires a Firecrawl API key β the hosted service is paid (usage-based credits). Curated by Skill Harbor β a dashboard-reporting workflow: give it an authenticated dashboard you have legitimate access to, and it extracts the visible metrics into a dated report with the reporting period, units and explicit caveats about what was captured. By @firecrawl, listed here with credit to its creator. Honest caveats: it reads only what the dashboard shows through your own authenticated session β if the session expires, re-authenticate; never bypass access controls, and confirm you have the right to extract and share the metrics before doing so. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a Firecrawl API key (the hosted service is paid β usage-based credits; set it via the secure vault or an environment variable, never in chat); legitimate access to the dashboards you want reported on Install "Firecrawl Dashboard Reporting" for me. Extract visible metrics from authenticated dashboards into dated reports with period, units and caveats Repository: https://github.com/firecrawl/firecrawl-workflows/blob/main/skills/firecrawl-dashboard-reporting/SKILL.md 1. Fetch the SKILL.md file for the firecrawl-firecrawl-dashboard-reporting skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "firecrawl-firecrawl-dashboard-reporting". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat β credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you β no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the sellerβs own page, usually Stripe.
What does the β next to a creatorβs name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself β always check a build before installing it.