firecrawl-developer-index
Skill252 starsChanged 12 days agoMITView on GitHub
Investigate library/API implementation, bugs, and version discrepancies using public repository code, issues, and pull requests. Use when official documentation alone is insufficient.
We split this skill into the rules it gives an agent
4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this workflow when the question requires repository code, issue discussions or pull requests, rather than an answer from official …
- Very specific: line 14
Use firecrawl_developer_search through the Firecrawl MCP connection.
- Very specific: line 21
Use firecrawl_scrape on a source URL when the passage lacks the needed context.
- Very specific: line 22
Use firecrawl_search when the relevant source is outside the index or the index does not resolve the question.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Developer research
Use this workflow when the question requires repository code, issue discussions
or pull requests, rather than an answer from official documentation alone. Use
read-docs for documented setup, usage, migrations and compatibility. A supplied
issue or repository can be investigated directly; a documentation search is not
a prerequisite.
Use firecrawl_developer_search through the Firecrawl MCP connection. If it is
deferred, discover it with the host's tool search. Include the library, version,
and exact error or symbol when known. Read the matched passages and source URLs.
Developer searches are billed per request.
Distinguish official documentation from issues, proposals, and merged pull
requests. A merged fix does not establish that it shipped in the user's version.
Use firecrawl_scrape on a source URL when the passage lacks the needed context.
Use firecrawl_search when the relevant source is outside the index or the index
does not resolve the question.
Answer from the retrieved evidence, cite the relevant sources, and state any unverified version or release boundary. Respect the user's source and tool choices. Report connection or authentication errors.
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- firecrawl/cli★ 676same name
- firecrawl/skills★ 142same name
- kschiavo-beep/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- brand-identitySkill
- business-contact-researchSkill
- designSkill
- enrich-leadSkill
- fantasy-sportsSkill
- find-leadsSkill
- firecrawl-deep-researchSkill
- firecrawl-research-indexSkill
- firecrawlSkill
- job-postingsSkill
- read-docsSkill
- seo-auditSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.