CtrlK
BlogDocsLog inGet started
Tessl Logo

ebay-search

Search eBay listings - find items, auctions, deals, and compare prices

58

Quality

73%

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/ebay-search/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

A well-structured, executable reference for a single-purpose search skill: complete credential setup, working commands, response schema, and error handling. Its weaknesses are minor — duplicated example commands, an inconsistent alternate-endpoint snippet, and a fully inline response reference.

Suggestions

Collapse the three near-identical example curl blocks into one example plus a short list of query variations to save tokens.

Remove or correct the inconsistent <details> curl block (different endpoint, missing auth header) and the "-q" flags tip, which does not match the JSON POST format shown.

Move the full organic_results field-by-field reference into a references/ file (e.g. references/response-fields.md) and keep only the key fields inline.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence: it never explains what eBay is or how curl works, and the setup, parameters, and response sections are tight. The one trimmable redundancy is the three near-identical example curl blocks that differ only in the query string, which keeps it below anchor 5 but above anchor 3's 'unnecessary explanation'.

4 / 5

Actionability

Setup and search commands are concrete and copy-paste ready, with documented parameters, response fields, and error codes. Minor gaps: the <details> block shows an inconsistent alternate endpoint ("https://api.orth.sh/v1/run") with no auth header, and the "-q" flags tip describes a GET-style invocation never shown in the doc.

4 / 5

Workflow Clarity

The sections form a coherent implicit sequence (credentials setup, run search, parse response, paginate, handle errors) with recovery guidance for 429 rate limits and empty results. It falls short of anchor 5 because there is no explicit ordered workflow and the doc exceeds the under-50-lines simple-skill exception; no destructive or batch operations require validation caps.

4 / 5

Progressive Disclosure

With no bundle files, all content is inline but well organized under clear headers (Setup, When to Use, Usage, Parameters, Response, Examples, Error Handling). The ~30-line response-field reference could arguably live in a separate reference file, which is the minor gap that keeps it at anchor 4 rather than 5.

4 / 5

Total

16

/

20

Passed

Description

61%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.

A concise, concrete description that clearly identifies its eBay-search niche with natural trigger terms. Its main weakness is the complete absence of a "Use when..." trigger clause, which caps completeness and limits trigger coverage.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to search eBay, find auctions or deals, or compare prices on eBay listings."

Include natural synonym terms users say, such as "used", "vintage", "second-hand", or "resale", to broaden trigger coverage.

Distinguish the listed capabilities (e.g. mention filtering by condition or paginating results) instead of restating "find items, auctions, deals" as separate actions.

DimensionReasoningScore

Specificity

The description names the domain and a couple of concrete actions ("Search eBay listings", "compare prices"), but "find items, auctions, deals" restates the same search action rather than adding distinct capabilities. It sits between anchor 3 and 4: more concrete than generic domain-naming, but not comprehensive coverage.

3 / 5

Completeness

The "what" is clear (search eBay listings, find auctions/deals, compare prices), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is above anchor 2 because the "what" is concrete, not vague.

3 / 5

Trigger Term Quality

Natural keywords like "eBay listings", "auctions", "deals", and "compare prices" match what users would actually say. A few common variations ("used", "vintage", "second-hand", "best price") are missing, keeping it below anchor 5.

4 / 5

Distinctiveness Conflict Risk

Explicitly naming "eBay" gives it a clear niche with minimal conflict risk against unrelated skills. Minor overlap remains with other marketplace/shopping search skills, so it does not fully reach anchor 5.

4 / 5

Total

14

/

20

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.

Validation — 15 / 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.