← Search

πŸ’³ Firecrawl Demo Walkthrough
Business πŸ§ͺ Install ran in our test sandbox Β· Nov 11, 2026 πŸ“Œ Pinned version: commit 94cc912
Install test only, on the date shown. This does not guarantee the code is safe.
πŸ”Ž Install prompt analysis Β· 2026-10-13 : uses API keys or tokens
βš™ Needs: a Firecrawl API key (hosted paid service…

πŸ’³ Firecrawl Demo Walkthrough

Walk through a product's key flows with the Firecrawl browser β€” structured UX/product walkthrough, friction and recommendations

At a glance
What
Walk through a product's key flows with the Firecrawl browser β€” structured UX/product walkthrough, friction and recommendations
Cost
Free
Needs
a Firecrawl API key (hosted paid service, usage-based credits); the product URL to walk through
Install
Copy the installer prompt below into your Muse β€” your agent does the rest.

Version:

Quick answer

Firecrawl Demo Walkthrough is a free Muse skill, a walkthrough guide, not a marketing demo. Onboarding first, inferring URL, flow focus, format, at most 1 to 3 questions if blocked, then navigating key flows with the Firecrawl browser: homepage, signup, onboarding, pricing, docs, dev experience, dashboard, support, snapshotting each step, delivering a walkthrough, screen journeys, impression, patterns, friction, recommendations, pages.

⌁

Install

Copy the install package below, then paste it into MuseπŸ§ͺ Install ran in our test sandbox Β· Nov 11, 2026πŸ“Œ Pinned version: commit 94cc912

Step 0 β€” before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Firecrawl API key (hosted paid service, usage-based credits); the product URL to walk through Install "Firecrawl Demo Walkthrough" for me. Give my agent the product walkthrough workflow: onboarding interview (product URL, flow focus, output format β€” at most 1–3 questions if blocked), navigate key flows with the Firecrawl browser with snapshots per step, parallelize per zone where appropriate, deliver the structured walkthrough (flow journeys, friction, recommendations, pages visited, rerun inputs) β€” with guardrails: no real credentials, purchases, or irreversible actions without my explicit instruction Repository: https://raw.githubusercontent.com/firecrawl/firecrawl-workflows/94cc91229d6cedc0613f140d3d013b150bc8e1b0/skills/firecrawl-demo-walkthrough/SKILL.md Pinned version: install the code at commit 94cc91229d6cedc0613f140d3d013b150bc8e1b0 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the firecrawl-firecrawl-workflows-firecrawl-demo-walkthrough skill from the repository into a temporary folder 2. Safety check: review the SKILL.md 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 into the agent's skills directory, in a folder named "firecrawl-firecrawl-workflows-firecrawl-demo-walkthrough". 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. get a Firecrawl API key, provide the product URL). 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.

πŸ”’ Security, provenance and what this touches
🧭 What this touches
  • It works with an API key or a token that you provide.
Install prompt analysis Β· 2026-10-13
πŸ”’ Security and provenance
πŸ“Œ Pinned version: commit 94cc912 Β· 2026-10-13
πŸ§ͺ Install ran in our test sandbox Β· Nov 11, 2026
πŸ‘ Observed during the install test Β· Nov 11, 2026 : no network contact
πŸ”Ž Install prompt analysis Β· 2026-10-13 : uses API keys or tokens
What the scan found β€” excerpts from the install prompt
  • uses API keys or tokens β€” Prerequisites: a Firecrawl API key (hosted paid service, usage-based credits); the product URL to walk through Β· PrΓ©requis : une clΓ© API Firecrawl (service hΓ©bergΓ© payant, crΓ©dits Γ  l'usage) ; l'URL du produit Γ  parcourir
πŸ”Ž Last checked Β· Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing β†’

βœ“

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
94cc912 Β· 2026-10-13
Sandbox install test
Install ran in our test sandbox Β· Nov 11, 2026
Creator identity
Not verified
Fingerprint watch
Last checked Β· Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : uses API keys or tokens

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.