brave-search
Web search and content extraction via Brave Search API. Use for searching documentation, facts, or any web content. Lightweight, no browser required.
Install with Tessl CLI
npx tessl i github:Dicklesworthstone/pi_agent_rust --skill brave-search86
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 description is functional with a clear 'Use for...' clause that addresses when to apply the skill. However, it could be more specific about concrete capabilities and include more natural trigger terms users would actually say. The mention of 'Lightweight, no browser required' is a nice differentiator but the core actions remain somewhat vague.
Suggestions
Add more specific actions like 'retrieve search results', 'extract page summaries', 'find documentation pages', or 'look up current information'
Include additional natural trigger terms users might say: 'look up', 'find online', 'research', 'what is', 'search the web for'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (web search) and some actions (search, content extraction), but lacks comprehensive specific actions like 'retrieve search results', 'extract page text', or 'find documentation links'. | 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'), with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'search', 'documentation', 'facts', 'web content', but missing common variations users might say like 'look up', 'find online', 'google', 'research', or 'browse'. | 2 / 3 |
Distinctiveness Conflict Risk | Mentions Brave Search API specifically which helps distinguish it, but 'web content' and 'search' are fairly generic and could overlap with browser-based search skills or other web tools. | 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 a well-crafted skill that exemplifies good practices: concise, actionable commands with clear examples, appropriate scope boundaries (the critical special URL handling section), and logical organization. The skill efficiently communicates everything needed without over-explaining concepts Claude already understands.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only essential information. No unnecessary explanations of what Brave Search is or how APIs work—assumes Claude's competence throughout. | 3 / 3 |
Actionability | Provides fully executable bash commands with clear flag combinations. The examples are copy-paste ready with concrete syntax patterns for different use cases. | 3 / 3 |
Workflow Clarity | For this simple, single-purpose skill, the workflow is unambiguous: search or extract content. The critical special URL handling section provides clear decision points for when NOT to use the tool. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is well-organized with clear sections (Requirements, Search, Extract, Output Format, Special Handling, When to Use). | 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.
- Reviewed
Table of Contents
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.