firecrawl-developer-index

Search GitHub issues, pull requests, READMEs, and documentation via the Firecrawl developer index.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/leonardoacosta/agents --skill firecrawl-developer-index-leonardoacosta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: firecrawl-developer-index
Source: https://github.com/leonardoacosta/agents/tree/main/skills/firecrawl-developer-index
Command: npx skills add https://github.com/leonardoacosta/agents --skill firecrawl-developer-index-leonardoacosta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developer questions are best answered from primary sources, but finding the exact issue, merged pull request, or documentation passage that defines a behavior is slow with general web search. This Skill queries the Firecrawl developer index to return matched passages from issues, PRs, READMEs, and docs so answers cite the authoritative source. ## Core Features & Use Cases - Passage-level search: Query the developer index over HTTP, MCP, or CLI and receive ranked results with matched markdown passages, preserving tables and code blocks. - Targeted filtering: Narrow results by artifact type (doc, issue, pull_request, readme), repository, documentation source, and repository metadata such as language, topic, and stars. - Question-type strategies: Match the search approach to the question, from literal error strings and known bugs to API contracts and version-specific behavior. - Use Case: When a library throws an unfamiliar error, search the error string scoped to issues and pull requests, then read the merged PR passages to learn exactly what changed and how to fix it. ## Quick Start Ask the agent to search the Firecrawl developer index for how a specific library handles a given error or API behavior and cite the source passage.

Frequently Asked Questions about firecrawl-developer-index

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I search GitHub issues and pull requests for an error message?

Search the literal error string plus the library name with types set to issue and pull_request using the Firecrawl developer search endpoint or CLI. If nothing matches, strip volatile parts like paths, line numbers, and ids, then retry with the invariant middle of the message.

What is the Firecrawl developer index used for?

The developer index is a searchable collection of documentation, GitHub issues, pull requests, and READMEs that returns matched markdown passages. It answers developer questions from primary sources rather than general web pages or blog posts.

Does Firecrawl developer search require an API key?

The developer search endpoint works keyless, but sending an Authorization header with a Firecrawl API key grants higher rate limits. The same applies across the HTTP, MCP, and CLI surfaces.

Why does filtering by language or stars remove documentation results?

Repository metadata filters like language, topic, and min_stars only apply to repository-backed artifacts, so documentation pages without a repository are excluded by design. To keep docs, drop the repository filters or scope the documentation half with the sources parameter.

When should I use general web search instead of the developer index?

Use general web search for comparisons, opinions, news, outages, or projects with no indexed repository or documentation. The index is for primary-source answers; ecosystem trade-offs and unindexed projects are web questions.