brave-search

Web search and content extraction via Brave Search API. Use for searching documentation, facts, or any web content. Lightweight, no browser required.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

93%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a lean, action-dense reference: copy-paste CLI commands, a compact options table, a concrete output-format example, and a clear "When to Use" section, with no concept over-explanation. The only minor gap is the absence of an explicit post-setup validation checkpoint (e.g., confirming the API key works) and error-recovery guidance. No bundle files exist, so progressive disclosure is appropriately self-contained.

Suggestions

Add a one-line setup verification step, e.g. run a trivial search after exporting BRAVE_API_KEY to confirm the key works before relying on it.

Add brief error-recovery guidance for common failures (invalid/expired API key, rate limits, unreachable URL with content.js).

Clarify how --content behaves when a page is non-extractable (e.g., returns empty or an error marker) so output parsing is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean throughout: short setup steps, copy-paste commands, a compact options list, and a minimal output-format block, with no explanation of concepts Claude already knows; every section earns its place, matching the lean-and-efficient 5-anchor.	5 / 5
Actionability	Commands are fully executable and copy-paste ready ("{baseDir}/search.js \"query\" -n 10", "{baseDir}/content.js https://example.com/article") with concrete examples covering common cases and a documented options table, matching the fully-executable 5-anchor.	5 / 5
Workflow Clarity	Setup is a clearly sequenced 5-step list and the search/extract workflows are unambiguous single commands, but there are no explicit validation/checkpoint steps after setup (e.g., verifying the API key works) or error-recovery guidance, fitting the clear-sequence-with-minor-gaps 4-anchor.	4 / 5
Progressive Disclosure	This is a simple, single-purpose skill under 50 lines with no external references needed; content is well-organized into clear sections (Setup, Search, Options, Extract, Output Format, When to Use), satisfying the simple-skill exception for a 5.	5 / 5
	Total	19 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise, third-person, and explicitly pairs what the skill does with when to use it via a concrete "Use for" trigger clause. It carves a clear niche (API-based, no-browser search) with low conflict risk. Minor trigger-term synonym coverage and slight action-specifiity gaps prevent a perfect specificity/trigger score.

Dimension	Reasoning	Score
Specificity	"Web search and content extraction via Brave Search API" lists two concrete actions (search, content extraction) over a named API; minor coverage gaps (no mention of freshness/country filtering) keep it just below the comprehensive 5-anchor.	4 / 5
Completeness	It explicitly states what ("Web search and content extraction via Brave Search API") and when ("Use for searching documentation, facts, or any web content") with concrete trigger phrases, matching the anchor that answers both what and when explicitly.	5 / 5
Trigger Term Quality	"searching documentation, facts, or any web content" gives natural trigger terms users would say, but lacks common synonyms/extensions like "look up" or domain-specific terms; a few natural terms missing relative to the 5-anchor.	4 / 5
Distinctiveness Conflict Risk	The Brave Search API niche with "no browser required" framing carves a distinct trigger space (API-based web search vs interactive browsing skills) with minimal conflict risk, matching the clear-niche 5-anchor.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: hefgi/dotfiles
Path: .agents/skills/brave-search/SKILL.md
Commit: e6f304f

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.