CtrlK
BlogDocsLog inGet started
Tessl Logo

web-search-linkup

Web search and content fetching - search the web or extract content from URLs

49

Quality

53%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/research-tools/capabilities/web-search-linkup/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-structured and self-contained with good progressive disclosure, but it loses points on a broken primary code example, duplicated endpoint descriptions, and the absence of any response validation or error-handling guidance. Fixing the malformed Search curl example would be the highest-impact improvement.

Suggestions

Fix the Search curl example so the body is a single valid JSON string inside `-d`, matching the structure of the Fetch example (e.g. wrap q/depth/outputType under a `body` key).

Remove the duplicated endpoint one-liners ("The /search/… endpoint allows you to…") that repeat the Capabilities section verbatim under Usage.

Add brief error/validation guidance, such as checking the response status and what to do when credentials are missing or the API returns an error.

DimensionReasoningScore

Conciseness

The body is mostly lean parameter lists and curl examples, but endpoint descriptions are duplicated ("The /search endpoint allows you to retrieve web content" appears in both Capabilities and Usage) and the Use Cases section restates the obvious, so it could be tightened.

2 / 3

Actionability

Concrete curl examples are provided, but the primary Search example is malformed — the request body JSON appears as stray lines outside the `-d` string — so the most important example is not copy-paste executable, matching the 'incomplete guidance' anchor.

2 / 3

Workflow Clarity

The skill is organized as API reference rather than a sequenced workflow, and there are no validation or error-handling checkpoints for API responses (e.g. what to do on auth failure or empty results), leaving the sequence present but checkpoints implicit.

2 / 3

Progressive Disclosure

It is a single self-contained file with no bundle references, organized into clear sections (Setup, Capabilities, Usage, Use Cases, Discover More) and no nested/deep references, which is appropriate navigation for a skill of this size.

3 / 3

Total

9

/

12

Passed

Description

50%

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 and states concrete actions, but it omits any explicit "when to use" trigger guidance and relies on a thin set of keywords, leaving it competent but undifferentiated. It scores uniformly at the midpoint across all dimensions.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to search the web, look something up online, or fetch/extract content from a URL."

Broaden trigger terms to include natural user phrasings such as "look up", "research", "fetch a webpage", and "read a page".

Differentiate from built-in web tools by naming the Linkup/Gooseworks provider and its depth or sourcing capabilities in the description.

DimensionReasoningScore

Specificity

The description names the web domain and a couple of concrete actions ("search the web or extract content from URLs") but is not comprehensive, matching the 'names domain and some actions' anchor rather than the multi-action level-3 example.

2 / 3

Completeness

It clearly answers "what" (web search and content fetching) but contains no "Use when…" clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Natural terms like "web search", "search the web", and "extract content" appear, but common variations a user might say ("look up", "research", "fetch a page", "browse") are missing, so coverage is partial.

2 / 3

Distinctiveness Conflict Risk

"Web search and content fetching" is somewhat specific but overlaps conceptually with built-in web search/fetch tools and other search skills, so it could still trigger for the wrong skill.

2 / 3

Total

8

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
gooseworks-ai/goose-skills
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.