CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

anysearch

Real-time search engine supporting web search, vertical domain search, parallel batch search, and URL content extraction.

Quality

71%

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

Quality

Content

67%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 a strong, command-first operational guide: exact invocations for every subcommand, explicit decision rules for vertical vs. general search, ordered platform detection, and genuine error-recovery loops. Its main weaknesses are localized redundancy (duplicated runtime tables and key-persistence steps) and two references to files (SHA256SUMS.txt, requirements.txt) that are absent from the bundle.

Suggestions

Collapse the duplicate runtime tables into a single CLI invocation table (the doc command row can say 'same invocation with the doc subcommand') and merge the 'Persisting Keys' section into the Scenarios table row to remove the repeated four-step procedure.

Either add SHA256SUMS.txt and requirements.txt to the bundle or delete the instructions referencing them, so every written step is executable.

Add brief guidance for handling per-item failures in batch_search responses (detect, retry individually, or fall back to sequential search) to complete the batch-operation feedback loop.

DimensionReasoningScore

Conciseness

The body is dense and operational (cheat sheet, rules, tables) with no educational padding, but contains clear duplication: the runtime invocation table appears twice with near-identical rows (doc table and CLI Invocation table), and the key-persistence procedure is stated twice (Scenarios table row and the 'Persisting Keys' section repeat the same four steps). Fits 'mostly efficient but could be tightened'; not 2 because there is no explanation of concepts Claude already knows and the padding is localized redundancy rather than pervasive verbosity.

3 / 5

Actionability

The Command Cheat Sheet gives exact, copy-paste-ready command shapes for search, batch_search, extract, and get_sub_domains, including both --sdp formats and explicit invalid examples, which approaches fully executable. However, two written instructions cannot be executed against the actual bundle: 'verify the bundled CLI scripts locally against SHA256SUMS.txt' and 'pip install -r requirements.txt' reference files that do not exist in the bundle — minor gaps that fit the 4 anchor rather than 5.

4 / 5

Workflow Clarity

Sequences are explicit and well-ordered: runtime.conf fast path, a numbered platform-detection procedure with first-success logic, a MUST rule to call get_sub_domains before vertical search, and error-recovery feedback loops (runtime fallthrough, retry after key save, --help on argument errors). Not 5 because batch_search results have no per-query failure validation guidance (e.g., how to detect and retry a failed item in a batch response); not 3 because validation and feedback loops for CLI/key failures are explicitly present.

4 / 5

Progressive Disclosure

Scored against the actual bundle: the full interface reference is correctly kept out of SKILL.md behind the offline doc command, which genuinely reads scripts/shared/doc_spec.md (verified in anysearch_cli.py), and referenced CLI script paths all exist — a good one-level-deep structure. Not 5 because navigation relies on the indirect doc command rather than clearly signaled reference files, and SHA256SUMS.txt/requirements.txt are mentioned but missing from the bundle.

4 / 5

Total

15

/

20

Passed

Description

62%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 delivers a clear, concrete inventory of the skill's four capabilities with good natural-language keywords, but it is purely a 'what' statement. It entirely lacks 'when to use' trigger guidance and its generic web-search/URL-extraction framing creates overlap risk with built-in search tools.

Suggestions

Append an explicit trigger clause, e.g. "Use when looking up current facts, news, or documentation; fact-checking claims; extracting full page content from a URL; or running several independent searches in parallel."

Add user-natural synonyms such as "look up", "browse", "fact-check", and "read this page/URL" to broaden trigger-term coverage.

Emphasize the distinctive vertical-domain capability (Stock:/CVE:/DOI:/patent-style identifier searches) to differentiate the skill from generic web-search tools.

DimensionReasoningScore

Specificity

"Real-time search engine supporting web search, vertical domain search, parallel batch search, and URL content extraction" names four concrete capabilities, matching the 'lists several specific actions; minor gaps' anchor. Not 5 because capabilities documented in the body (sub-domain discovery via get_sub_domains, anonymous access) are omitted; not 3 because it goes well beyond naming the domain with 1-2 actions.

4 / 5

Completeness

The 'what' is clear and concrete (the four supported capabilities), but there is no 'Use when...' clause or equivalent trigger guidance anywhere in the description, capping completeness at 3 per the judging guidelines. Not 4 because the 'when' is entirely absent rather than merely implicit or imprecise.

3 / 5

Trigger Term Quality

"web search", "search engine", "batch search", and "URL content extraction" are natural phrases users would say, giving good keyword coverage. Not 5 because common variations like "look up", "browse", "fetch/read a page", "fact-check", or "news" are missing; not 3 because coverage is clearly better than 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

"vertical domain search" and "parallel batch search" give it a partial niche, but "web search" and "URL content extraction" overlap heavily with built-in WebSearch/WebFetch and any other search skill. Fits 'somewhat specific but could still overlap with similar skills'; not 4 because the generic search terms create real conflict risk with common search tooling.

3 / 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

anysearch-ai/anysearch-skill

Path

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.