CtrlK
BlogDocsLog inGet started
Tessl Logo

searxng-search

Free meta-search via SearXNG — aggregates results from 70+ search engines. Self-hosted or use a public instance. No API key needed. Falls back automatically when the web search toolset is unavailable.

56

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/research/searxng-search/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

A highly actionable skill with executable examples throughout, weakened by redundancy across setup sections, absent validation checkpoints in the workflow, and an unreferenced bundle script.

Suggestions

Reference the bundled script (e.g. "For a ready-made CLI wrapper, run scripts/searxng.sh \"query\"") so the existing bundle is discoverable and the body can shed the inline curl examples.

Add an explicit validation step to the search-then-extract workflow: check that results are non-empty before extracting, and retry on a different instance if empty.

Consolidate the repeated SEARXNG_URL setup guidance (Configuration, Detection Flow, Instance Discovery) into one section to reduce redundancy.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete code, but the Configuration, Detection Flow, and Instance Discovery sections re-explain the same SEARXNG_URL setup, adding tokens that could be tightened.

2 / 3

Actionability

Provides fully executable curl, Python, and Docker commands plus a flag table and parsing snippet — copy-paste ready with specific examples.

3 / 3

Workflow Clarity

A decision tree and a search-then-extract workflow are present, but there is no explicit validation checkpoint (e.g. confirm non-empty results before extracting) or fix-retry feedback loop.

2 / 3

Progressive Disclosure

Content is organized into sections, but it is a single monolithic ~213-line body and the bundled scripts/searxng.sh is never referenced or linked, so navigation to existing detail is missing.

2 / 3

Total

9

/

12

Passed

Description

67%

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 specific, distinctive description that clearly conveys capability but omits an explicit usage-trigger clause, capping completeness. Trigger term coverage is good but not comprehensive.

Suggestions

Add an explicit trigger clause, e.g. "Use when web search is unavailable, you need a free/API-key-less search, or the user asks for SearXNG/meta-search."

Broaden trigger terms with natural user phrasings like "search the web", "free search", and "Google alternative".

Keep the third-person voice but lead with the action verb (already mostly done) to maximize specificity.

DimensionReasoningScore

Specificity

Lists several concrete actions — "aggregates results from 70+ search engines", "Self-hosted or use a public instance", "Falls back automatically" — rather than vague language.

3 / 3

Completeness

Clearly states what the skill does, but lacks an explicit "Use when…" trigger clause, so the "when" side is only implied.

2 / 3

Trigger Term Quality

Includes relevant terms (SearXNG, meta-search, search engines, web search) but misses common user phrasings like "search the web" or "free search", so coverage is incomplete.

2 / 3

Distinctiveness Conflict Risk

The SearXNG-specific framing and fallback-when-web-search-unavailable positioning carve a clear niche unlikely to trigger the wrong skill.

3 / 3

Total

10

/

12

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository
NousResearch/hermes-agent
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.