firecrawl-build-onboarding
Get Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.
- License 许可
- ISC
- 最近更新
- 2026-11-15
- Stars
- ★ 6
- Forks
- 0
01 前言 Front Matter
- name
- firecrawl-build-onboarding
- inputs
- [ { "name": "FIRECRAWL_API_KEY", "required": true, "description": "Firecrawl API key used for hosted Firecrawl API requests." }, { "name": "FIRECRAWL_API_URL", "required": false, "description": "Optional base URL for self-hosted Firecrawl deployments." } ]
- license
- ISC
- metadata
- { "author": "firecrawl", "source": "https://github.com/firecrawl/skills", "version": "0.1.0", "homepage": "https://www.firecrawl.dev" }
- references
- [ "references/auth-flow.md", "references/sdk-installation.md", "references/project-setup.md" ]
- description
- Get Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.
02 资源文件 1
- 参考文档skill-report.json63.1 KB
03 SKILL.md 正文
Firecrawl Build Onboarding
Use this skill for the application-integration path from Firecrawl's onboarding flow.
Install
If you haven't installed yet, one command sets up both the CLI tools (for live web work) and the build skills (for app integration):
npx -y firecrawl-cli@latest init --all --browser
This installs the Firecrawl CLI, the CLI skills, and these build skills
together. It also opens browser auth so the human can sign in or create
an account. No separate npx skills add step is needed.
Use This When
- a project needs
FIRECRAWL_API_KEY - the user wants Firecrawl wired into
.env - you are adding Firecrawl to an app for the first time
- you need to choose the first SDK or REST path
If the human still needs to sign up, sign in, or authorize access in the browser, use the auth flow reference in this skill.
Quick Start
If the user already has an API key, place it in .env:
FIRECRAWL_API_KEY=fc-...
If the project is self-hosted, also set:
FIRECRAWL_API_URL=https://your-firecrawl-instance.example.com
Then decide which integration path applies:
- Fresh project -> choose the target stack, install the SDK, add the first Firecrawl call, and run a smoke test
- Existing project -> inspect the repo first, then integrate Firecrawl where the project already handles third-party APIs and env vars
What Do You Need?
| Task | Reference |
|---|---|
Run the browser auth flow and save FIRECRAWL_API_KEY |
references/auth-flow.md |
| Install the right SDK | references/sdk-installation.md |
Put credentials into .env or project config |
references/project-setup.md |
| Choose the right endpoint after setup | firecrawl-build |
| Need live web tooling during this task | The CLI skills are already installed from the same command |
| Start implementation from a known URL | firecrawl-build-scrape |
| Start implementation from a query | firecrawl-build-search |
Docs (Source of Truth)
Read the source-of-truth page for your project language for SDK usage, schemas, and examples:
- Node / TypeScript: docs.firecrawl.dev/agent-source-of-truth/node
- Python: docs.firecrawl.dev/agent-source-of-truth/python
- Rust: docs.firecrawl.dev/agent-source-of-truth/rust
- Java: docs.firecrawl.dev/agent-source-of-truth/java
- Elixir: docs.firecrawl.dev/agent-source-of-truth/elixir
- cURL / REST: docs.firecrawl.dev/agent-source-of-truth/curl
After Setup
Once the key is present:
- decide whether this is a fresh project or an existing codebase
- ask what Firecrawl should do in the product
- pick the narrowest endpoint that matches that behavior
- read the source-of-truth page for the project language before writing code
- add the SDK or REST call in code
- run a smoke test that proves one real Firecrawl request succeeds
- use the endpoint-specific skills in this repo for implementation guidance
- if you also need live web tooling during the current task, the CLI skills are already installed — use
firecrawl/cli
04 同仓库更多 Skills
serpmaven
Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.
revnu-landing-page-audit
Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: "audit my landing page", "why isn't this page converting", "review my homepage", "my ads get clicks but no signups", "people bounce from the pricing page", "CRO review", "improve conversion rate", "is my hero section clear", "roast my landing page", "rewrite my headline", "what's wrong with this page", "landing page feedback", "make the signup page convert better". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.
revnu-growth-context
Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents/revnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says "set up our marketing context", "who is our ideal customer", "write our ICP", "describe the product for marketing", "positioning doc", "what's our brand voice", "remember this about our customers", "log what we tried", "what have we learned from marketing", "we changed pricing, update the context", "update our growth notes", "summarize the business for the agent", "import my product-marketing.md", "start a growth doc", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.
revnu-get-listed
Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: "best X" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says "get us listed", "which directories should we submit to", "how do we get into best-of lists", "why does ChatGPT recommend competitors and not us", "get mentioned in AI answers", "submit to awesome lists", "get on G2", "where are our competitors listed", "pitch listicle authors", "find backlink opportunities", "launch directories", "get into roundups", "Product Hunt alternatives", "where should we be listed", "get cited by Perplexity". Never submits, pays or posts without a yes. Works without a Revnu account.
revnu-ai-readiness-audit
Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks "is my site ready for AI search", "audit my site for AI answers", "AEO audit", "GEO audit", "why doesn't ChatGPT quote our pricing", "make our pages citable by AI", "do I need llms.txt", "does schema help with ChatGPT", "check our structured data", "is our content visible without JavaScript", "AI SEO audit", "optimize our homepage for AI answers", "LLM SEO check", "why does AI get our product wrong", "fix our site for AI Overviews". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.
proxy-troubleshooting
Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.