Web search and content extraction via Brave Search API. Use for searching documentation, facts, or any web content. Lightweight, no browser required.
88
83%
Does it follow best practices?
Impact
96%
2.23xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a decent description that covers the basics well—it identifies the tool, states what it does, and provides explicit 'Use for' guidance. However, it could be stronger with more specific concrete actions and richer trigger terms that match how users naturally phrase web search requests. The 'no browser required' differentiator is a nice touch but the overall scope is still somewhat broad.
Suggestions
Add more specific concrete actions, e.g., 'retrieve search results, extract page text, look up documentation, find facts online'.
Expand trigger terms with natural user phrases like 'look up', 'find online', 'search for', 'URL content', 'fetch webpage'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (web search, content extraction) and the tool (Brave Search API), but doesn't list multiple specific concrete actions beyond 'searching' and 'content extraction'. Missing specifics like 'retrieve search results, extract page content, summarize articles'. | 2 / 3 |
Completeness | Clearly answers both what ('Web search and content extraction via Brave Search API') and when ('Use for searching documentation, facts, or any web content'). The 'Use for...' clause serves as an explicit trigger guidance, and the 'Lightweight, no browser required' adds useful differentiation context. | 3 / 3 |
Trigger Term Quality | Includes some natural keywords like 'web search', 'documentation', 'facts', 'web content', but misses common variations users might say such as 'look up', 'find online', 'Google', 'search the web', 'URL', 'website'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of Brave Search API and 'no browser required' helps distinguish it from browser-based web skills, but 'web search' and 'web content' are broad enough to potentially overlap with browser automation or other web-fetching skills. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent, well-crafted skill that is concise, actionable, and well-structured. It provides executable commands, clear output format expectations, and critical edge-case handling for special URLs. The only minor note is the 'When to Use' section could arguably be trimmed, but it serves a useful purpose for tool selection decisions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and purposeful. No unnecessary explanations of what Brave Search is or how APIs work. The 'When to Use' section is borderline but serves as a useful decision guide. | 3 / 3 |
Actionability | Provides concrete, copy-paste-ready bash commands with clear flag combinations. The output format section shows exactly what to expect. Special URL handling gives specific alternative tools and commands. | 3 / 3 |
Workflow Clarity | This is a simple, single-purpose skill (search and extract). The two operations (search and content extraction) are clearly separated with unambiguous usage. The critical special URL handling section provides clear decision logic for edge cases. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is well-organized into logical sections (Requirements, Search, Extract, Output Format, Special Handling, When to Use) with clear headers and appropriate depth. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
47823e3
Table of Contents
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.