CtrlK
BlogDocsLog inGet started
Tessl Logo

brave-search

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

84

2.23x
Quality

77%

Does it follow best practices?

Impact

96%

2.23x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-mikeastock/skills/brave-search/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 content is an exemplary lean skill body: executable commands, documented flags, a concrete output format, and a prominently flagged exception list for special URLs. The only real improvement is removing the mild duplication between the intro/"When to Use" section and the frontmatter description.

DimensionReasoningScore

Conciseness

The body is lean and command-focused, but the opening line "Headless web search and content extraction using Brave Search API. No browser or setup required" and the "When to Use" section largely restate the frontmatter description — minor instances that could be trimmed, matching anchor 4.

4 / 5

Actionability

Fully executable, copy-paste-ready commands with flag variants ("search.py \"query\" -n 3 --content"), a concrete extraction command, and an explicit output-format example covering the common cases — anchor 5.

5 / 5

Workflow Clarity

This is a simple, single-purpose skill where each invocation is unambiguous: usage, flags, and expected output are all specified, and the critical URL-handling exceptions (GitHub → gh, .md → curl) are called out; no destructive or batch operations exist, so the validation cap does not apply.

5 / 5

Progressive Disclosure

A short, well-organized overview with clear section headers and clearly signaled one-level-deep script references ({baseDir}/search.py, {baseDir}/content.py); no nested references and nothing inlined that belongs in a separate file (no bundle files exist beyond the skill body, so structure is judged on the body itself).

5 / 5

Total

19

/

20

Passed

Description

62%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 clearly answers both what the skill does and when to use it. Its main weakness is trigger coverage: natural phrasings users would actually say (looking things up, fetching a URL) are absent, and "any web content" is overly broad. Adding a few concrete trigger phrases and excluding its known non-triggers (GitHub URLs, .md files) would raise both completeness and distinctiveness.

Suggestions

Add natural trigger phrases and synonyms users would say, e.g. "Use when asked to look up, search, or verify facts online, or fetch the content of a specific URL".

Replace the vague "any web content" with concrete cases (documentation, articles, web pages) to sharpen completeness and trigger quality.

State the exclusions in the description (e.g., "not for GitHub URLs or raw .md files — use gh/curl for those") to reduce overlap with other fetch/search tools.

DimensionReasoningScore

Specificity

Names the domain ("via Brave Search API") and two concrete actions ("Web search and content extraction"), matching the 1-2-concrete-actions anchor; it lacks the several-action comprehensive coverage of anchor 4.

3 / 5

Completeness

Explicit "what" ("Web search and content extraction via Brave Search API") plus an explicit "Use for..." trigger clause satisfies anchor 4; it falls short of anchor 5 because the when-clause relies on the broad phrase "any web content" rather than concrete trigger phrases.

4 / 5

Trigger Term Quality

"searching documentation, facts, or any web content" provides some natural keywords, but common user phrases like "look this up", "find information", or "fetch this URL" are missing and "any web content" is a generic catch-all, keeping it at the some-keywords anchor rather than good coverage.

3 / 5

Distinctiveness Conflict Risk

"Brave Search API" establishes a clear niche with distinct triggers, but the broad "web search" framing has minor overlap risk with built-in search/fetch tools, fitting the mostly-distinct anchor rather than minimal-conflict anchor 5.

4 / 5

Total

14

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Dicklesworthstone/pi_agent_rust
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.