Repository navigation
[QUESTION] What's the difference between the firecrawl-interact skill and the firecrawl-instruct skill? Will they conflict if I have both installed? #95
Description
- Install/init firecrawl with
firecrawl init --global --agent claude-codeand observe the following skills are installed inC:\Users\username\.claude\skills:
firecrawl
firecrawl-agent
firecrawl-build-interact
firecrawl-build-onboarding
firecrawl-build-scrape
firecrawl-build-search
firecrawl-crawl
firecrawl-download
firecrawl-interact
firecrawl-map
firecrawl-scrape
firecrawl-search- Install the firecrawl plugin in the
claude-plugins-officialmarketplace. - Navigate to
C:\Users\username\.claude\plugins\cache\claude-plugins-official\firecrawl\1.0.8\skills - Observe the following skills exist in that folder:
firecrawl-agent
firecrawl-cli
firecrawl-crawl
firecrawl-download
firecrawl-instruct
firecrawl-map
firecrawl-scrape
firecrawl-search- Cross reference the created skills with
firecrawl initand theclaude-plugins-officialfirecrawl plugin. You'll notice that there are two extra skills installed with the official plugin:
firecrawl-cli
firecrawl-instructI think that firecrawl-cli is the same exact skill as the firecrawl skill from firecrawl init.
firecrawl-interact and firecrawl-instruct seem to generally be the same skill, but with a different name.
Comparison of firecrawl-interact and firecrawl-instruct
Here's the YAML front matter for both:
---
name: firecrawl-interact
description: |
Control and interact with a live browser session on any scraped page — click buttons, fill forms, navigate flows, and extract data using natural language prompts or code. Use when the user needs to interact with a webpage beyond simple scraping: logging into a site, submitting forms, clicking through pagination, handling infinite scroll, navigating multi-step checkout or wizard flows, or when a regular scrape failed because content is behind JavaScript interaction. Also useful for authenticated scraping via profiles. Triggers on "interact", "click", "fill out the form", "log in to", "sign in", "submit", "paginated", "next page", "infinite scroll", "interact with the page", "navigate to", "open a session", or "scrape failed".
allowed-tools:
- Bash(firecrawl *)
- Bash(npx firecrawl *)
------
name: firecrawl-instruct
description: |
Control and interact with a live browser session on any scraped page — click buttons, fill forms, navigate flows, and extract data using natural language prompts or code. Replaces the old firecrawl-browser command. Use when the user needs to interact with a webpage beyond simple scraping: logging into a site, submitting forms, clicking through pagination, handling infinite scroll, navigating multi-step checkout or wizard flows, or when a regular scrape failed because content is behind JavaScript interaction. Also useful for authenticated scraping via profiles. Triggers on "browser", "instruct", "click", "fill out the form", "log in to", "sign in", "submit", "paginated", "next page", "infinite scroll", "interact with the page", "navigate to", "open a session", or "scrape failed".
allowed-tools:
- Bash(firecrawl *)
- Bash(npx firecrawl *)
---Which skill is the most recently updated? Will these skills conflict if I have both installed?
Any clarification would be greatly appreciated.
Activity
RichardBray commentedon Jun 24, 2026
Apologies for the late reply, and thanks for the detailed write-up.
firecrawl-interactis the current name.firecrawl-instructwas a short-lived intermediate name.You're seeing
firecrawl-instructbecause theclaude-plugins-officialmarketplace plugin is pinned to v1.0.8, a stale snapshot from before the April rename. Same story for thefirecrawl-clivsfirecrawldifference you noticed: drift between the pinned plugin and whatfirecrawl initinstalls from currentmain.Will they conflict? Not in a breaking way. They have different
name:values, so Claude Code treats them as two separate skills, and neither overwrites the other. But they're functionally identical (same description, same trigger words, same underlyingfirecrawlCLI commands), so with both installed you get two near-duplicate skills competing to match the same requests.For now I'd keep the one from
firecrawl init(firecrawl-interact) and remove the duplicate.