Search the web using Tavily's LLM-optimized search API. Returns relevant results with content snippets, scores, and metadata. Use when you need to find web content on any topic without writing code.
81
76%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/tavily/search/SKILL.mdQuality
Discovery
75%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 solid description that clearly communicates both purpose and usage context. Its main strengths are the explicit 'Use when...' clause and clear differentiation through the Tavily API mention. However, it could benefit from more specific action verbs and broader trigger term coverage to help users discover it with varied natural language.
Suggestions
Add more natural trigger terms users might say, such as 'look up', 'research online', 'google', or 'find information on the internet'
List more specific capabilities beyond generic 'search', such as 'retrieve current information', 'find recent news', or 'discover sources on topics'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (web search via Tavily API) and describes what it returns (results with content snippets, scores, metadata), but doesn't list multiple concrete actions beyond 'search' - lacks specifics like filtering, advanced queries, or different search modes. | 2 / 3 |
Completeness | Clearly answers both what ('Search the web using Tavily's LLM-optimized search API. Returns relevant results with content snippets, scores, and metadata') and when ('Use when you need to find web content on any topic without writing code') with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes 'search the web', 'web content', and 'find' which are natural terms, but misses common variations like 'look up', 'google', 'research', 'online information', or 'internet search' that users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly distinguishes itself as a web search tool using Tavily specifically, with the 'without writing code' qualifier helping differentiate from code-based web scraping skills. The Tavily mention creates a distinct niche. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, highly actionable skill with excellent executable examples and clear authentication guidance. The main weakness is verbosity - the comprehensive API reference and multiple similar curl examples could be condensed or moved to separate files. The content successfully teaches how to use Tavily search without explaining concepts Claude already knows.
Suggestions
Move the detailed API Reference table and curl examples to a separate REFERENCE.md file, keeping only the script usage and one basic example in the main skill
Consolidate the 'Basic Search' and 'Advanced Search' curl examples into a single example with comments showing optional parameters
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundancy - showing both script usage AND curl examples for similar operations, and the API reference table is comprehensive but could be trimmed. The authentication section is appropriately concise. | 2 / 3 |
Actionability | Excellent actionability with fully executable bash commands, complete curl examples with all required headers, and copy-paste ready JSON payloads. Every example is concrete and immediately usable. | 3 / 3 |
Workflow Clarity | For a single-task skill (web search), the workflow is unambiguous. Authentication flow is clearly sequenced (check tokens → OAuth if needed), and the search depth table provides clear decision guidance for choosing options. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the API reference and multiple example variations could be split into a separate REFERENCE.md file. The skill is somewhat long for what could be a more concise overview with links to detailed docs. | 2 / 3 |
Total | 10 / 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.
1e2a6a0
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.