agentleFS
Sign inStart free
GabrieleDattileGabrieleDattile/agent-superpowers/skills/scraping/firecrawl-interact/SKILL.md

firecrawl-build-interact

Skill1 starsChanged 15 days agoMITView on GitHub

Integrate Firecrawl `/interact` into product code for dynamic pages and

  • Reads credentials

8 other projects use a version of this, 8 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use firecrawl-interact, firecrawl-crawl and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • RudraDudhat2509Skill

    firecrawl-interact

    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".

    Also in 4 projects that use this

  • get-proofpilotSkill

    firecrawl-crawl

    Bulk extract content from an entire website or site section. Use this skill when the user wants to crawl a site, extract all pages from a docs section, bulk-scrape multiple pages following links, or says "crawl", "get all the pages", "extract everything under /docs", "bulk extract", or needs content from many pages on the same site. Handles depth limits, path filtering, and concurrent extraction.

    Also in 4 projects that use this

  • noahsilve123Skill

    firecrawl-research-index

    Find the papers that answer a research query with Firecrawl Research, using semantic search, semantic and structural expansion, and in-body verification. Always use this skill for any literature-finding / paper-retrieval task — single-paper lookups or full multi-paper sets.

    Also in 3 projects that use this

  • get-proofpilotSkill

    firecrawl-search

    Web search with full page content extraction. Use this skill whenever the user asks to search the web, find articles, research a topic, look something up, find recent news, discover sources, or says "search for", "find me", "look up", "what are people saying about", or "find articles about". Returns real search results with optional full-page markdown — not just snippets. Provides capabilities beyond Claude's built-in WebSearch.

    Also in 4 projects that use this

  • parcadeiSkill

    firecrawl-scrape

    Scrape web pages and extract content via Firecrawl MCP

    Also in 4 projects that use this

  • BBTB2Skill

    firecrawl-parse

    Use this skill whenever the user is working with the Firecrawl API /parse endpoint. Triggers include: uploading local files (PDF, DOCX, XLSX, HTML) to Firecrawl, parsing documents with Firecrawl, extracting markdown or structured JSON from files using Firecrawl, choosing between /parse and /scrape, configuring PDF parsing modes (fast/auto/ocr), setting output formats, enabling zero data retention, or any question about Firecrawl document parsing. Also triggers when the user says 'parse this file with Firecrawl', 'use Firecrawl to extract', or 'Firecrawl /parse'.

    Also in 3 projects that use this

  • +3 more from get-proofpilot

The file

We split this skill into the rules it gives an agent

9 rules. 6 are common, 0 are distinctive, and 3 are very specific to this project.

  • 6

    Common

    Most of the 8 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this when /scrape is not enough because the feature needs to act on the page.

    line 39
  2. Very specific:

    Start with /scrape, then escalate to /interact.

    line 49
  3. Very specific:

    Keep /interact scoped to the smallest browser workflow that unlocks the data.

    line 50
  4. Common:

    Use persistent profiles only when the feature truly needs authenticated state across sessions.

    line 51
  5. Common:

    search forms and faceted filters

    line 55
  6. Common:

    Keep prompts or action code specific to the product flow.

    line 63
  7. Common:

    If the use case is fully open-ended browser automation, evaluate whether a browser sandbox is a better product fit.

    line 64
  8. Common:

    If the page can be read directly, stay on firecrawl-build-scrape.

    line 68
  9. Common:

    Read the source-of-truth page for your project language before writing integration code:

    line 72

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Firecrawl Build Interact

Use this when /scrape is not enough because the feature needs to act on the page.

Use This When

  • content appears only after clicks, typing, or navigation
  • the feature needs forms, pagination, filters, or multi-step flows
  • the product must stay in the same browser context after scraping

Default Recommendations

  • Start with /scrape, then escalate to /interact.
  • Keep /interact scoped to the smallest browser workflow that unlocks the data.
  • Use persistent profiles only when the feature truly needs authenticated state across sessions.

Common Product Patterns

  • search forms and faceted filters
  • paginated result sets
  • login-gated dashboards or tools
  • flows where the page must be explored before extraction is complete

Implementation Notes

  • /interact is the right tool when the page must be manipulated, not just read.
  • Keep prompts or action code specific to the product flow.
  • If the use case is fully open-ended browser automation, evaluate whether a browser sandbox is a better product fit.

Escalation Rules

  • If the page can be read directly, stay on firecrawl-build-scrape.

Docs (Source of Truth)

Read the source-of-truth page for your project language before writing integration code:

See Also

  • firecrawl-build
  • firecrawl-build-scrape
  • firecrawl-build-search

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free