Spellcheck
- 627 installs
- 164 repo stars
- Updated August 3, 2026
- brave/brave-search-skills
spellcheck is a Brave Search API integration skill that normalizes misspelled query strings for developers who need reliable agent research, retrieval, and citation results.
About
spellcheck is an agent skill for the Brave Search Spellcheck API that corrects misspelled queries before search, retrieval, or "Did you mean?" UI steps run. Developers call `https://api.search.brave.com/res/v1/spellcheck/search` with an `X-Subscription-Token` header, passing `q` and optional `lang` parameters via cURL or equivalent HTTP clients. The skill is scoped for pre-search query cleanup when built-in endpoint spellcheck is unavailable or when agents need explicit correction logic. Most Brave Search endpoints already include spellcheck, so reach for this skill only when you want deterministic query normalization in custom agent pipelines. Requires a Brave Search API key on the Spellcheck subscription plan from the Brave Search API dashboard.
- Pre-search query correction
- Cuts zero-result Brave lookups
- Pairs with brave-search-skills
- Lightweight research utility
- Improves agent recall
Spellcheck by the numbers
- 627 all-time installs (skills.sh)
- Ranked #1,548 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/brave/brave-search-skills --skill spellcheckAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 627 |
|---|---|
| repo stars | ★ 164 |
| Last updated | August 3, 2026 |
| Repository | brave/brave-search-skills ↗ |
How do you fix misspelled Brave Search queries in agents?
Normalize misspelled Brave Search queries inside agent workflows so research, retrieval, and citation steps return relevant pages instead of empty or off-topic results.
Who is it for?
Developers building agent workflows that call Brave Search and need explicit pre-search typo correction before research or citation steps.
Skip if: Developers whose Brave Search endpoints already return built-in spellcheck suggestions and who do not need a separate pre-search cleanup step.
When should I use this skill?
User query text looks misspelled and the next step is a Brave Search API call or "Did you mean?" suggestion UI.
What you get
Corrected search query string and JSON spellcheck API response
- Corrected query string
- Spellcheck API JSON response
By the numbers
- Exposes the Brave Search `/res/v1/spellcheck/search` REST endpoint
Files
Spellcheck
Requires API Key: Get one at https://api.search.brave.com
>
Plan: Included in the Spellcheck plan. See https://api-dashboard.search.brave.com/app/subscriptions/subscribe
Quick Start (cURL)
curl -s "https://api.search.brave.com/res/v1/spellcheck/search" \
-H "Accept: application/json" \
-H "X-Subscription-Token: ${BRAVE_SEARCH_API_KEY}" \
-G \
--data-urlencode "q=artifical inteligence" \
--data-urlencode "lang=en" \
--data-urlencode "country=US"Endpoint
GET https://api.search.brave.com/res/v1/spellcheck/searchAuthentication: X-Subscription-Token: <API_KEY> header
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
q | string | Yes | — | Query to spell check (1-400 chars, max 50 words) |
lang | string | No | en | Language preference (2+ char language code, e.g. en, fr, de, pt-br, zh-hans). 51 codes supported |
country | string | No | US | Search country (2-letter country code or ALL) |
Response Fields
| Field | Type | Description |
|---|---|---|
type | string | Always "spellcheck" |
query.original | string | The input query as submitted |
results | array | Spell-corrected suggestions. May be empty when no correction is found |
results[].query | string | A corrected version of the query |
Example Response
{
"type": "spellcheck",
"query": {
"original": "artifical inteligence"
},
"results": [
{
"query": "artificial intelligence"
}
]
}Use Cases
- Pre-search query cleanup: Check spelling before deciding which search endpoint to call
- "Did you mean?" UI: Show users a corrected suggestion before running the search
- Batch query normalization: Clean up user inputs in bulk
Notes
- Built-in alternative: Web Search and LLM Context have
spellcheck=trueby default — use this standalone endpoint only when you need the correction before searching - Context-aware: Corrections consider the full query context, not just individual words
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10How it compares
Pick spellcheck when agents need explicit upstream query correction; rely on default Brave Search endpoint spellcheck when post-query suggestions are enough.
FAQ
Does spellcheck require a Brave Search API key?
spellcheck requires a Brave Search API key passed as `X-Subscription-Token`. Keys come from the Brave Search API dashboard and must be on the Spellcheck subscription plan.
When should agents use spellcheck instead of built-in spellcheck?
spellcheck is for pre-search query cleanup or custom "Did you mean?" UI. Most Brave Search endpoints already spellcheck results, so use spellcheck only when explicit correction is needed upstream.