Developer Index skill documents four id prefixes; a fifth (web:) is the majority of unscoped results
维护者通常 1 天内回复
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 68/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- typescript
- 领域
- cli, documentation
调研方向
首先定位 firecrawl-developer-index skill、开发者功能文档、API 参考以及 firecrawl developer CLI 入口点。将其中记录的类型行为与此 issue 中的复现结果和 CLI 输出进行比较。完成的标准是，受影响的指导文档和界面能够准确解释或阻止 web: 结果，并且已使用所提供的命令验证文档中描述的行为。
由索引模型根据 Issue 内容生成。
描述
The firecrawl-developer-index skill (and docs.firecrawl.dev/features/developer) both state
that the artifact kind is the id prefix, and enumerate four: doc:, issue:, pull_request:,
readme:.
In practice a fifth prefix, web:, is returned, and on unscoped queries it is frequently the
majority of results. It does not appear in the skill file, the feature docs, or the API reference.
Reproduction (keyless, no API key needed)
curl -s -X POST https://api.firecrawl.dev/v2/search/developer \
-H "Content-Type: application/json" \
-d '{"query":"drizzle orm mysql connection pool exhausted","k":8}' \
| python3 -c "import sys,json,collections; d=json.load(sys.stdin); print(collections.Counter(r['id'].split(':')[0] for r in d['results']))"
Measured 2026-08-28 against api.firecrawl.dev/v2:
| Request | Prefix distribution |
|---|---|
unscoped, k=8 |
{'issue': 3, 'doc': 2, 'web': 3} |
unscoped, k=8, different query |
{'issue': 3, 'doc': 2, 'web': 3} |
same query + types:["doc","issue","pull_request","readme"] |
{'issue': 4, 'doc': 3, 'pull_request': 1} — no web: |
types:["web"] |
400 {"code":"BAD_REQUEST","error":"unknown type: web (expected doc, issue, pull_request, readme)"} |
So web: can be excluded, but only by naming all four valid types explicitly. It cannot be
requested, and it is not documented.
Why this matters for agent behaviour
Three things in the shipped guidance combine badly:
- The skill tells the agent the kind is one of four prefixes.
- The skill's stated bar is "quote the passage, cite the url" as a primary source.
- The skill says "Scope last, not first — search the whole index, then narrow."
Following (3) produces the unscoped call, which returns majority web: — ordinary web pages.
The agent then satisfies (2) by quoting one, believing per (1) that it is a curated artifact.
The net effect is that the recommended first move is the one most likely to return
non-primary sources, with nothing in the guidance to flag it.
Also worth noting: the CLI surface cannot mitigate this. On [email protected],
firecrawl developer exposes only --limit, -o, --json, --pretty, -k, and its help says
to put scoping intent in the query text. There is no --types, so a CLI user cannot exclude
web: at all. A live CLI run returned {issue: 3, doc: 2, web: 3}.
Suggested fix (any one of these would close it)
- Document
web:as a possible prefix in the skill file, the feature page, and the API reference,
and say plainly that it is an open web page rather than a curated index artifact; or - have the skill recommend sending all four
typesby default, rather than "scope last"; or - add a
--typesflag to the CLIdevelopercommand so the CLI surface can exclude it too; or - exclude
web:from/search/developerand leave it to/search.
Happy to send the raw responses if useful.
One more control, added after drafting
The distribution is identical authenticated and keyless, so this is not an auth-tier artifact:
| surface | prefixes |
|---|---|
| authenticated CLI, unscoped | {issue: 3, doc: 2, web: 3} |
| keyless HTTP, same query, unscoped | {issue: 3, doc: 2, web: 3} |
keyless HTTP, same query, + types |
{issue: 4, doc: 3, pull_request: 1} |
The variable is types, not the key. A different query returned {issue: 4, doc: 4} on both
surfaces, so web: is query-dependent rather than always present.
- 主要语言
- TypeScript
- 星标
- 651
- 派生
- 113
- 平均合并
- 18 小时 12 分钟
- 30 天内合并 PR
- 47
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
firecrawl/cli 的其他 Issue
-
Trailing slash on cloud API URL disables keyless mode可能已有人在做 @danielgaskins 于 27 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 74/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
bug(search): documented --pretty option is rejected可能已有人在做 @ayushcodes13 于 70 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
firecrawl CLI fails with HTTP 404 through HTTP proxy (bundled axios < 1.16.1, no CONNECT tunneling for HTTPS)可能已有人在做 @tbontb-iaq 于 82 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 88/100
firecrawl/cli#160 · 1 个 reaction ·
维护者通常 1 天内回复
相似的 Issue
-
area:workflow bug ready-for-human
难度 1/5 1 小时以内 新手友好度 78/100
fil-donadoni/tolaria#6108 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
apache/rocketmq-dashboard#7234 ·
维护者通常 3 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
vitest-dev/vitest#11656 ·
维护者通常 1 天内回复
-
e2e-failure ready-to-code
难度 2/5 1-3 小时 新手友好度 68/100
redhat-developer/rhdh-plugin-export-overlays#4460 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
ehmpathy/rhachet-roles-bhrain#655 ·
维护者通常 1 天内回复