Enhanced web and package repository search using local SearXNG instance
65
48%
Does it follow best practices?
Impact
95%
3.80xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./searxng-search/SKILL.mdQuality
Discovery
32%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 identifies the tool (SearXNG) and general domain (web and package repository search) but is too terse. It lacks specific actions, a 'Use when...' clause, and natural trigger terms that users would employ when needing this skill.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to search the web, look up packages, find library documentation, or query online resources.'
List concrete actions the skill performs, such as 'searches the web, queries package registries (npm, PyPI, crates.io), retrieves documentation links, and aggregates results from multiple sources.'
Include natural trigger terms users might say, like 'search online', 'find a package', 'look up', 'google', 'npm search', 'pip search'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (web and package repository search) and the tool (SearXNG), but does not list specific concrete actions like 'query packages', 'filter results', or 'compare versions'. | 2 / 3 |
Completeness | Provides a partial 'what' (enhanced search using SearXNG) but completely lacks a 'when' clause or any explicit trigger guidance, which per the rubric caps this at 2 and the weakness of the 'what' brings it to 1. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'web', 'search', 'package repository', and 'SearXNG', but misses common user-facing variations such as 'look up', 'find packages', 'npm', 'pip', 'search the web', or 'google'. | 2 / 3 |
Distinctiveness Conflict Risk | Mentioning 'SearXNG' and 'package repository' adds some distinctiveness, but 'web search' is very broad and could overlap with any general search or browsing skill. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable skill with excellent concrete examples and a useful quick reference table. Its main weaknesses are length and organization — significant content (manual container setup, Nushell integration, advanced config) could be moved to reference files to keep the main skill lean. Adding a verification step after starting SearXNG would improve workflow clarity.
Suggestions
Move the 'Manual Container Start', 'Advanced Config', and 'Integration with Nushell' sections to separate reference files, keeping only brief pointers in the main SKILL.md
Add an explicit verification step after `start-searxng --detach`, e.g., `curl -s http://localhost:8888/config | jq '.instance_name'` to confirm it's running
Consider condensing the PyPI workaround into a brief note with a reference to the existing `references/pypi-direct-search.md` rather than duplicating content inline
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some unnecessary verbosity — the manual container start section largely duplicates what the helper script does, the PyPI workaround section is lengthy, and the Nushell integration section may not be essential. Some sections could be moved to reference files. | 2 / 3 |
Actionability | Excellent actionability throughout — every section provides concrete, copy-paste-ready curl commands, bash scripts, and code examples. The quick reference table, JSON response structure, and usage patterns are all immediately executable. | 3 / 3 |
Workflow Clarity | The start/stop workflow is clear, and debugging steps are provided. However, there are no explicit validation checkpoints — for example, after starting SearXNG there's no 'verify it's running' step, and the debugging section is separate from the workflow rather than integrated as checkpoints. | 2 / 3 |
Progressive Disclosure | References to `references/package-engine-status.md` and `references/pypi-direct-search.md` show some progressive disclosure, but the main file is quite long (~200 lines) with configuration details, manual container setup, and Nushell integration that could be split into reference files. The inline content is heavy for an overview. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
84b1da5
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.