Walk through a product's key flows with Firecrawl browser and produce a structured UX/product walkthrough. Use for signup, onboarding, pricing, docs, dashboard, product demo prep, UX teardown, and first-run experience analysis.
All-time #736Trending #9665First seen May 15, 2026
The skill is a specialized tool for generating UX walkthroughs by navigating and scraping websites via Firecrawl. It contains explicit safety guidelines to prevent accidental submission of credentials or irreversible actions and uses standard API key management for its primary service.
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude CodeNot declared
CursorNot declared
CodexNot declared
GitHub CopilotNot declared
WindsurfNot declared
Gemini CLINot declared
ClineNot declared
OpenCodeNot declared
Repository health
Stars156
LicenseLICENSE
Default branchmain
Open issues2
Status
Active
Skill metadata
Parsed from SKILL.md frontmatter.
Version0.1.0
LicenseISC
More metadata
author
firecrawl
version
0.1.0
homepage
https://www.firecrawl.dev
source
https://github.com/firecrawl/firecrawl-workflows
Package contents
Files included with this skill beyond the listing page.
skill mdSKILL.md2,217 B
docsSUMMARY.md261 B
History
First seen on skills.sh
First recorded snapshot · 31,100 installs
SKILL.md
Firecrawl Demo Walkthrough
Use this to document a product experience step by step.
Onboarding Interview
Infer the product URL, flow focus, and output format from context. If the URL is clear, proceed immediately.
Ask at most 1-3 concise questions only if blocked, such as the URL, desired flow focus, or credentials/constraints for protected areas.
Firecrawl Collection Plan
Use Firecrawl browser to open the product and navigate key flows. Snapshot at each step, scrape pages when useful, and document what the user sees and can do.
Do not submit real credentials, purchases, or irreversible actions unless the user explicitly instructs and has permission.
Parallel Work
If appropriate, use sub-agents or equivalent parallel task runners:
Homepage and Marketing
Signup and Onboarding
Pricing and Plans
Docs and Developer Experience
Dashboard and Core Product
Help and Support
Each walker should return screens visited, actions taken, observations, friction, and source URLs.
Final Deliverable
# Product Walkthrough: [Product]
## Product Overview
[What the product does]
## Flow Walkthroughs
### [Flow Name]
1. [Screen/Page] - what appears and what action is available
2. [Next Screen] - what changes
## Key Findings
[First impression, standout patterns, friction points]
## Recommendations
[UX/product improvements]
## Pages Visited
[URLs]
## Rerun Inputs
workflow: firecrawl-demo-walkthrough
url: [url]
focus: [full/signup/pricing/docs/dashboard]
Quality Bar
Be specific about screens, CTAs, forms, and transitions.