spellcheck — Claude Code skill: query correction and setup
Check a search query for spelling errors and get corrected suggestions. Use it to clean up input before a search or show a “Did you mean?” prompt.
npx skills add brave/brave-search-skills --skill spellcheck -a claude-codeWhat spellcheck does
The skill sends a query to the Brave Search Spellcheck API and returns the original text alongside correction suggestions. Suggestions use the context of the whole query, and the results can be empty. You can set a language and search country.
A Brave Search API key is required in the X-Subscription-Token header. Use this endpoint when you need a correction before searching; Web Search and LLM Context have spellcheck enabled by default. Without the key, the endpoint request will fail.
What it helps with
- correct misspelled queries before search
- offer a corrected query suggestion to users
- normalize user-entered search text
Example prompts for the agent
- Check the spelling of “artifical inteligence” before searching.
- Prepare a “Did you mean?” suggestion for this search query.
- Check this English query for country
US.
How to install spellcheck
1Skills CLI (Vercel)
npx skills add brave/brave-search-skills --skill spellcheck -a claude-code2Manually: put the files in place
~/.claude/skills/spellcheck/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/spellcheck/
1Skills CLI (Vercel)
npx skills add brave/brave-search-skills --skill spellcheck -a codex2Manually: put the files in place
.agents/skills/spellcheck/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add brave/brave-search-skills --skill spellcheck -a cursor2Manually: put the files in place
.cursor/skills/spellcheck/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install brave/brave-search-skills spellcheck2Manually: put the files in place
.github/skills/spellcheck/SKILL.md1Skills CLI (Vercel)
npx skills add brave/brave-search-skills --skill spellcheck -a gemini-cli2Platform CLI
gemini skills install https://github.com/brave/brave-search-skills --path skills/spellcheckManually: put the files in place
.devin/skills/spellcheck/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add brave/brave-search-skills --skill spellcheck -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about spellcheck
How do I install spellcheck in Claude Code?
Run npx skills add brave/brave-search-skills --skill spellcheck -a claude-code. The skill file is at ~/.claude/skills/spellcheck/SKILL.md.
What does spellcheck do?
It sends a query to the Brave Search Spellcheck API and returns suggested corrections. The suggestions take the full query into account.
What does spellcheck need to run?
It requires a Brave Search API key, sent in the X-Subscription-Token header. Web Search and LLM Context already enable spellcheck by default, so use the standalone endpoint when you need corrections before searching.
Source text
SKILL.md · MIT
---
name: spellcheck
description: USE FOR spell correction. Returns corrected query if misspelled. Most search endpoints have spellcheck built-in; use this only for pre-search query cleanup or "Did you mean?" UI.
---
# 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)
```bash
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
```http
GET https://api.search.brave.com/res/v1/spellcheck/search
```
**Authentication**: `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
```json
{
"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=true` by 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
© brave · MIT · brave/brave-search-skills