agentsclimarketplace

Searxng search

Skill FactrueSolin/searxng-skills/skills/searxng-search

A portable Agent Skill for searching the web through a user-configured SearXNG instance, with source-aware research workflows and a companion Python CLI.

Install
npx -y skills add FactrueSolin/searxng-skills --skill searxng-search

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 17 days oldThe repository was created 17 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use the local sxc CLI to search a configured SearXNG instance, inspect instance configuration, and answer research questions with verifiable source URLs. Use when the user asks for web search, current information, source gathering, or SearXNG instance details.

SKILL.md

3.6 KB, as published. Nobody here has run it

SearXNG Search

Use the locally installed sxc command to search the web through the user's SearXNG instance.

Preconditions

  1. Check whether sxc is available by running sxc --help.

  2. If it is unavailable, stop and tell the user that sxc must be installed. Do not install it or run an installer without explicit user action. You may show this installation command:

    uv tool install git+https://github.com/FactrueSolin/searxng-skills.git
    
  3. Check the configured instance with sxc config get-url before the first search unless the user supplied --url or SEARXNG_URL is known to be set.

  4. If no instance URL is configured, do not invent or select one. Ask the user to configure it and show:

    sxc config set-url https://example.org
    sxc config test
    
  5. Treat configured headers as secrets. They are stored as plaintext; never print, quote, or expose their values unless the user explicitly asks.

Commands

Use sxc search QUERY for searches. Available filters are:

  • --categories
  • --engines
  • --language
  • --page
  • --time-range
  • --safe-search
  • --enable-plugins
  • --disable-plugins
  • --limit

Output modes:

  • Default output is human-readable text.
  • Use --json when structured, normalized results make analysis or citation extraction safer.
  • Use --raw only when the original successful SearXNG response is required.

Use sxc instance info to retrieve the instance's /config response unchanged.

Global per-command overrides:

  • Instance URL: --url URL or SEARXNG_URL
  • Timeout: --timeout SECONDS or SEARXNG_TIMEOUT

Configuration commands:

sxc config set-url URL
sxc config get-url
sxc config path
sxc config test
sxc config set-header NAME VALUE
sxc config unset-header NAME
sxc config list-headers

Search workflow

  1. Turn the user's request into a short, focused query. Do not paste a long prompt into the search engine.
  2. Prefer primary sources: official documentation, standards, repositories, release notes, government publications, papers, and first-party announcements.
  3. For straightforward questions, use one search round when sufficient.
  4. For complex questions, use at most three search rounds. Refine each round based on gaps in the previous results rather than repeating the same query.
  5. Use result URLs actually returned by sxc. Open or inspect sources when the task requires claims beyond a search-result snippet.
  6. Clearly distinguish search-result snippets or summaries from statements verified in a source's body.
  7. Cite the actual source URL next to the supported claim. Never fabricate, reconstruct, or guess a URL.
  8. If search fails, results are insufficient, or a source cannot be inspected, say so plainly. Never claim that a search or verification occurred when it did not.

Answering

Keep the answer proportional to the question. Summarize findings, identify material uncertainty or disagreement, and include only URLs that were genuinely retrieved. Do not present snippets as full-source evidence.

<rule> 1. 直接调用sxc工具搜索。调用前不确认sxc工具是否存在。 2. 如果sxc工具不存在,提示用户使用 uv tool install git+https://github.com/FactrueSolin/searxng-skills.git 进行安装,并且教会他如何设置配置文件。 </rule>

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.