CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tavily-sdk

Build production-ready Tavily integrations with best practices baked in. Reference documentation for developers using coding assistants to implement web search, content extraction, crawling, and research in agentic workflows, RAG systems, or autonomous agents.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is tavily-best-practices in andrewyng/context-hub

SKILL.md
Quality
Evals
Security

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 an exemplary overview: lean, executable code for every method, a clear method-selection decision table, and well-signaled one-level-deep references that all resolve to real bundle files. The only minor gap is the absence of error-recovery guidance for the research() polling workflow's "failed" state.

DimensionReasoningScore

Conciseness

The body is dense and reference-like: install commands, init snippet, need→method decision tables, one compact code sample plus a "Key parameters" line per method, then pointers to references. The single contextual line ("Tavily is a search API designed for LLMs...") is product-specific rather than a concept Claude already knows, and nothing else is padding — anchor 5's "every token earns its place".

5 / 5

Actionability

Every method has copy-paste-ready executable code, including env-var-based client init, and the research() example is a complete polling workflow (`while response["status"] not in ["completed", "failed"]`). "Key parameters" lists after each example cover the common cases, matching anchor 5's fully executable, common-case coverage.

5 / 5

Workflow Clarity

The "Choosing the Right Method" tables give an unambiguous need→method decision sequence, and the research example includes a status-check loop. However, no guidance is given for what to do when status becomes "failed" — a minor checkpoint/validation gap — so it fits anchor 4 ('clear sequence with most checkpoints present') rather than 5's explicit error-recovery feedback loops.

4 / 5

Progressive Disclosure

All six referenced files (sdk.md, search.md, extract.md, crawl.md, research.md, integrations.md) exist in the bundle, are exactly one level deep, and contain no nested internal references. The "Detailed Guides" section clearly signals what each file contains, and the SKILL.md itself is a genuine overview with quick examples — anchor 5's well-signaled one-level-deep structure.

5 / 5

Total

19

/

20

Passed

Description

66%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 names concrete capabilities (web search, extraction, crawling, research) and anchors them to a specific product (Tavily) and audience, making it reasonably specific and distinct. Its main weakness is the absence of any explicit 'Use when...' trigger guidance, which caps completeness and leaves 'when to use this skill' only weakly implied.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions Tavily, needs web search or content extraction in an LLM/agent application, or asks to add search to a RAG pipeline."

Include natural synonyms users actually say: "Tavily API", "web scraping", "search API", "extract content from URLs".

Trim the buzzword lead-in "production-ready... with best practices baked in" and instead enumerate the full capability set (search, extract, crawl, map, research).

DimensionReasoningScore

Specificity

"implement web search, content extraction, crawling, and research" lists four concrete actions in a named domain (Tavily integrations), matching anchor 4's 'several specific actions; minor gaps'. Not 5 because URL discovery/map() is absent and the lead-in "production-ready Tavily integrations with best practices baked in" is mild buzzword; not 3 because it clearly goes beyond 1-2 actions.

4 / 5

Completeness

The 'what' is clear ("Build production-ready Tavily integrations... implement web search, content extraction, crawling, and research") but there is no "Use when..." clause or equivalent explicit trigger guidance; 'when' is only weakly implied by "in agentic workflows, RAG systems, or autonomous agents", which describes contexts rather than telling Claude when to reach for the skill. Per the judging guideline, a missing 'Use when...' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms users would say are present: "web search", "content extraction", "crawling", "research", "agentic workflows", "RAG systems". Good coverage but a few common variations are missing — notably "scraping" (a frequent synonym for extraction), "search API", and "Tavily API" — so it fits anchor 4 rather than 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"Tavily" is named prominently, giving a clear niche with distinct triggers. However, broad phrases like "web search... in agentic workflows, RAG systems, or autonomous agents" overlap with generic web-search/scraping/research skills, creating minor conflict risk with closely related skills — anchor 4, not 5's minimal conflict risk.

4 / 5

Total

15

/

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

boranfurkan/discordlancer

Path

.claude/skills/tavily-sdk/SKILL.md

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.