firecrawl-browser
Cloud browser automation for pages requiring clicks, forms, login, and pagination.
Works with
1
total installs
1
this week
256
GitHub stars
0
upvotes
Install Skill
Run in your terminal
1
installs
1
this week
256
stars
What it does
Supports interactive workflows: click elements, fill forms, navigate multi-step flows, handle pagination and infinite scroll
Persistent profiles survive session close, enabling login-then-work patterns where authentication state is retained across reconnects
Core commands include open , snapshot -i (element discovery with @ref IDs), click , fill , type , scrape , scroll , wait , and eval for JavaScript
Installation Guide
How to use firecrawl-browser on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your machine
- ›Node.js 16+ with npm — verify with
node --version - ›Active project directory where you want to add
firecrawl-browser
Run the install command
Execute the skills CLI command in your project's root directory to begin installation:
Fetches firecrawl-browser from firecrawl/cli and configures it for Cursor.
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate firecrawl-browser. Access via /firecrawl-browser in your agent's command palette.
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Documentation
firecrawl interact (formerly browser)
The
browsercommand is deprecated. Usescrape+interactinstead. Interact lets you scrape a page and then click, fill forms, and navigate without managing sessions manually.
Interact with scraped pages in a live browser session. Scrape a page first, then use natural language prompts or code to click, fill forms, navigate, and extract data.
When to use
- Content requires interaction: clicks, form fills, pagination, login
scrapefailed because content is behind JavaScript interaction- You need to navigate a multi-step flow
- Last resort in the workflow escalation pattern: search → scrape → map → crawl → interact
- Never use interact for web searches — use
searchinstead
Quick start
# 1. Scrape a page (scrape ID is saved automatically)
firecrawl scrape "<url>"
# 2. Interact with the page using natural language
firecrawl interact --prompt "Click the login button"
firecrawl interact --prompt "Fill in the email field with [email protected]"
firecrawl interact --prompt "Extract the pricing table"
# 3. Or use code for precise control
firecrawl interact --code "agent-browser click @e5" --language bash
firecrawl interact --code "agent-browser snapshot -i" --language bash
# 4. Stop the session when done
firecrawl interact stop
Options
| Option | Description |
|---|---|
--prompt <text> |
Natural language instruction (use this OR --code) |
--code <code> |
Code to execute in the browser session |
--language <lang> |
Language for code: bash, python, node |
--timeout <seconds> |
Execution timeout (default: 30, max: 300) |
--scrape-id <id> |
Target a specific scrape (default: last scrape) |
-o, --output <path> |
Output file path |
Profiles
Use --profile on the scrape to persist browser state (cookies, localStorage) across scrapes:
# Session 1: Login and save state
firecrawl scrape "https://app.example.com/login" --profile my-app
firecrawl interact --prompt "Fill in email with [email protected] and click login"
# Session 2: Come back authenticated
firecrawl scrape "https://app.example.com/dashboard" --profile my-app
firecrawl interact --prompt "Extract the dashboard data"
Read-only reconnect (no writes to profile state):
firecrawl scrape "https://app.example.com" --profile my-app --no-save-changes
Tips
- Always scrape first —
interactrequires a scrape ID from a previousfirecrawl scrapecall - The scrape ID is saved automatically, so you don't need
--scrape-idfor subsequent interact calls - Use
firecrawl interact stopto free resources when done - For parallel work, scrape multiple pages and interact with each using
--scrape-id
See also
- firecrawl-scrape — try scrape first, escalate to interact only when needed
- firecrawl-search — for web searches (never use interact for searching)
- firecrawl-agent — AI-powered extraction (less manual control)
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
- 1Install product management skill
- 2Start with user story generation for known feature
- 3Progress to competitive analysis: research 2-3 competitors
- 4Use for roadmap prioritization: apply RICE/ICE scoring
- 5Draft stakeholder communications and refine based on feedback
- 6Build template library for recurring PM tasks
- 7Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Related Skills
cmux-browser
44manaflow-ai/cmux
grill-me
386mattpocock/skills
premortem
197parcadei/continuous-claude-v3
deslop
118cursor/plugins
framer-motion
98pproenca/dot-skills
write-a-prd
91mattpocock/skills
Reviews
- LLi Johnson★★★★★Dec 28, 2024
Useful defaults in firecrawl-browser — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- KKiara Kim★★★★★Dec 28, 2024
firecrawl-browser has been reliable in day-to-day use. Documentation quality is above average for community skills.
- NNia Chen★★★★★Dec 20, 2024
We added firecrawl-browser from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- IIra Wang★★★★★Dec 16, 2024
We added firecrawl-browser from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- KKaira Flores★★★★★Dec 12, 2024
Keeps context tight: firecrawl-browser is the kind of skill you can hand to a new teammate without a long onboarding doc.
- CChaitanya Patil★★★★★Dec 8, 2024
Useful defaults in firecrawl-browser — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- PPiyush G★★★★★Nov 27, 2024
firecrawl-browser is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- DDiya Jackson★★★★★Nov 19, 2024
firecrawl-browser is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- HHenry Farah★★★★★Nov 15, 2024
Solid pick for teams standardizing on skills: firecrawl-browser is focused, and the summary matches what you get after install.
- CCarlos Brown★★★★★Nov 11, 2024
firecrawl-browser reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 64
Discussion
Comments — not star reviews- No comments yet — start the thread.