firecrawl-alexandria — Claude Code skill: install guide
Finds ready-made paths to structured website data through Firecrawl discovery, then runs the selected retrieval tool.
npx skills add firecrawl/skills --skill firecrawl-alexandria -a claude-codeWhat firecrawl-alexandria does
This skill guides an agent toward website workflows, API providers, and specialized indexes. It starts with firecrawl-search to find results and relevant tools, then uses firecrawl-scrape to call a chosen tool or read a URL.
Use regular web results when they already answer the request. When a provider has suitable coverage and inputs, the skill directs the agent to retrieve structured output instead. Large retained results can be handled through the remote Bash guidance in firecrawl-scrape.
The agent can send firecrawl alexandria feedback after working with a website. Feedback must be submitted within 20 minutes of the latest Alexandria call, so it belongs at the end of the task. FIRECRAWL_NO_ENDPOINT_FEEDBACK=1 and FIRECRAWL_DISABLE_ENDPOINT_FEEDBACK=1 prevent the CLI from sending it.
What it helps with
- find a data provider for a target website
- match a retrieval tool to required data
- retrieve structured output instead of parsing pages
- run Firecrawl search before extraction
- report website coverage after a task
Example prompts for the agent
- Find a structured data source for this website with Alexandria and inspect the relevant tool.
- Use
firecrawl-searchfirst, then run the selected tool throughfirecrawl-scrape. - After the final Alexandria call, submit feedback for this website.
How to install firecrawl-alexandria
1Skills CLI (Vercel)
npx skills add firecrawl/skills --skill firecrawl-alexandria -a claude-code2Manually: put the files in place
~/.claude/skills/firecrawl-alexandria/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/firecrawl-alexandria/
1Skills CLI (Vercel)
npx skills add firecrawl/skills --skill firecrawl-alexandria -a codex2Manually: put the files in place
.agents/skills/firecrawl-alexandria/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add firecrawl/skills --skill firecrawl-alexandria -a cursor2Manually: put the files in place
.cursor/skills/firecrawl-alexandria/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install firecrawl/skills firecrawl-alexandria2Manually: put the files in place
.github/skills/firecrawl-alexandria/SKILL.md1Skills CLI (Vercel)
npx skills add firecrawl/skills --skill firecrawl-alexandria -a gemini-cli2Platform CLI
gemini skills install https://github.com/firecrawl/skills --path skills/core/firecrawl-alexandriaManually: put the files in place
.devin/skills/firecrawl-alexandria/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add firecrawl/skills --skill firecrawl-alexandria -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about firecrawl-alexandria
How do I install firecrawl-alexandria in Claude Code?
Run npx skills add firecrawl/skills --skill firecrawl-alexandria -a claude-code, then run npx skills add firecrawl/skills --skill firecrawl-alexandria -a claude-code again. The skill is placed at ~/.claude/skills/firecrawl-alexandria/SKILL.md.
What does firecrawl-alexandria do?
It finds ready-made tools and sources for structured website data. The skill connects Firecrawl search with a follow-up retrieval step.
When should Alexandria feedback be sent?
Send one report per website right after the final Alexandria call, within 20 minutes. Stop sending feedback for the rest of the UTC day when dailyCapReached: true.
Source text
SKILL.md · ISC
---
name: firecrawl-alexandria
description: Find a direct path to structured data through ready-made workflows, data APIs, and indexes. Follow the search skill to discover and inspect tools, then the scrape skill to execute them.
---
# A direct path to structured data
Alexandria brings ready-made website workflows, API providers, and specialized indexes into Firecrawl search and scrape. Semantic discovery finds capabilities by the data you need; domain matching connects web results to tools that may retrieve richer structured data beyond the page. Discover a tool that fits the task and get structured results directly, reducing the browsing, parsing, and repeated requests needed to assemble the data yourself.
- [Search](../firecrawl-search/SKILL.md) to find web results and relevant tools, then inspect only the contracts needed for the task.
- [Scrape](../firecrawl-scrape/SKILL.md) to execute a selected tool or read a URL. For large retained results, use its remote Bash guidance to select the data you need.
Use ordinary web results when they answer the question; use a provider tool when its coverage and inputs fit.
## Alexandria feedback (refunds 1 credit)
Alexandria coverage grows from what agents report. Send one `firecrawl alexandria feedback` per website you needed data from, right after your last Alexandria call for it. No job ID is needed. Each feedback refunds 1 credit, up to 10 credits per website and 100 per team each UTC day.
Feedback can describe any of these outcomes:
- A tool answered the need, fully or partly.
- A tool ran but returned wrong or incomplete data, or failed.
- No provider covers the website, or a provider exists but lacks the capability you needed, and you fell back to web search, scrape, or Agent.
**Opt out:** if `FIRECRAWL_NO_ENDPOINT_FEEDBACK=1` (or `FIRECRAWL_DISABLE_ENDPOINT_FEEDBACK=1`) is set, the CLI silently skips the call and never sends anything. Respect that; do not try to work around it. (Team admins can also disable this server-side; the API returns `feedbackErrorCode: "TEAM_OPTED_OUT"` and the CLI exits 0 silently.)
**Rules to know before you call this:**
- **Time window:** must be sent within 20 minutes of your team's most recent Alexandria search, discovery, or execution. Each Alexandria call restarts the window. Late feedback is rejected (`feedbackErrorCode: "FEEDBACK_WINDOW_EXPIRED"`).
- **`--url` is the website the user needed data from**, not the provider and not a Firecrawl page. `--requested-functionality` is what they needed from it, in one sentence. These two fields are the most important: they aggregate across teams and tell us which sites and workflows to add next.
- **`--objective` is the underlying goal** behind the session: what you or your user were ultimately trying to accomplish, in one sentence (for example, "Shortlist federal IT contracts to bid on this quarter"). It is broader than `--requested-functionality`, which covers only this website.
- **`--rationale` explains the rating** from observed results: which provider or capability served or failed the need, and how. Two or three sentences, no raw results pasted in.
- **`--provider-feedback`** is a JSON array of `{name, issue, why}` for providers that were missing, thin, or unavailable. Issues: `missing_provider` (no provider covers the site), `insufficient_coverage` (exists, but data was thin, stale, or partial for this market or segment), `provider_unavailable` (could not be called), `other`.
- **`--capability-feedback`** is a JSON array of `{name, provider, issue, why, requestedFunctionality?}` for capabilities that were missing, wrong, or failed. Issues: `new_capability_request` (ask the provider to add one; `requestedFunctionality` required), `missing_capability` (provider exists but lacks it), `insufficient_functionality` (exists but cannot take the input or filter you needed), `incorrect_result`, `execution_error`, `other`. Use `name` and `provider` exactly as discovery returned them; for a capability that does not exist yet, name what it should be.
- **Rate honestly:** `good` when a tool answered the need, `partial` when it answered some of it or with gaps, `bad` when nothing available answered it or what ran was wrong or failed. Every rating gets the same refund.
- **Website refund cap (per website, per UTC day, default 10 credits).** Past it, feedback about that website is still recorded but refunds nothing, and the response sets `websiteCapReached: true`. Feedback about other websites still refunds.
- **Daily refund cap (per team, per UTC day, default 100 credits).** Past the cap, feedback is still recorded but refunds nothing. The response includes `creditsRefundedToday`, `dailyRefundCap`, and `dailyCapReached`. **When `dailyCapReached: true`, stop sending Alexandria feedback for the rest of the UTC day.**
- **`--silent &`** is the right pattern: exit code 0 even on failure, so a rejected call never crashes your pipeline.
```bash
# Example: send once per website, within 20 minutes of your last Alexandria call. Replace the
# placeholders with what actually happened; drop --provider-feedback or
# --capability-feedback when there is nothing to report at that level.
firecrawl alexandria feedback \
--rating "<good|partial|bad>" \
--url "https://sam.gov" \
--requested-functionality "Active contracts by agency with their attachments" \
--objective "Shortlist federal IT contracts to bid on this quarter" \
--rationale "sam-gov/contracts returned the contract list, but no capability exposes attachment links, so those were scraped from the web instead." \
--capability-feedback '[{"name":"attachments","provider":"sam-gov","issue":"new_capability_request","why":"Attachments were the point of the task","requestedFunctionality":"Given a contract ID, return attachment URLs and document text"}]' \
--silent &
```
If you report a site with no provider coverage, use `--provider-feedback '[{"name":"<site or provider>","issue":"missing_provider","why":"<what was needed>"}]'` and rate `bad`; that is the signal we use to onboard new providers.
`--silent` suppresses output and `&` runs it in the background so feedback never blocks you. Run `firecrawl alexandria feedback --help` for every option.
© firecrawl · ISC · firecrawl/skills