firecrawl/cli

firecrawl-alexandria

Find a direct path to structured data through ready-made workflows, data APIs, and indexes.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/firecrawl/cli --skill firecrawl-alexandria

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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 to find web results and relevant tools, then inspect only the contracts needed for the task.
  • Scrape 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.

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
firecrawl
공식

firecrawl

Any live-web task via the Firecrawl CLI — including ordinary web research: searching the web, reading or extracting pages, gathering sources, discovering site URLs, bulk extraction, downloading a site, change alerts, or pages needing clicks/login — web only; local files route to firecrawl-parse. For US legal or regulatory questions use gov; for papers use firecrawl-research-index; for library, API, error, or bug questions use firecrawl-developer-index.

누적 설치 수
10.5만
GitHub Stars
694
업데이트
11월 19일
firecrawl
공식

firecrawl-search

Find web sources with query-relevant page excerpts and optional full-page content, and discover workflows, data APIs, and indexes. Use for web research or finding structured records, listings, transcripts, and datasets. Supports semantic tool discovery, domain matching, and progressive catalogue browsing.

누적 설치 수
8.5만
GitHub Stars
694
업데이트
11월 19일
firecrawl
공식

firecrawl-scrape

Read a known webpage or execute a discovered workflow or data-provider capability. Use for page content or structured results once the URL or tool is selected.

누적 설치 수
8.5만
GitHub Stars
694
업데이트
11월 19일
firecrawl
공식

firecrawl-agent

Autonomously navigate websites and extract structured data across pages. Use when the task requires navigation or no suitable ready-made workflow or data provider covers it.

누적 설치 수
8.2만
GitHub Stars
694
업데이트
11월 19일