AnySearch provides a bridge to current information through general web search and vertical domain queries. It enables the retrieval of facts, news, and documentation while supporting full-page content extraction to move beyond search snippets.
The tool is designed for tasks requiring rigorous fact-checking and multi-intent queries, allowing for parallel batch searches across specific identifiers like patents, CVEs, or DOIs.
Follow the documented setup, then try a first task.
Installs: Complete AnySearch skill repository, installed as "anysearch" in Claude Code's user skill directory. · Claude Code
In a terminal, download the pinned v3.1.1 release. To use another release, replace v3.1.1 in the command with the latest tag from the repository's releases page.
curl -L -o anysearch-skill.zip https://github.com/anysearch-ai/anysearch-skill/archive/refs/tags/v3.1.1.zip
In the same terminal directory, extract the downloaded archive.
unzip anysearch-skill.zip
Using your file manager or terminal, move the extracted v3.1.1 directory into Claude Code's skill directory and rename it to anysearch. If another release was downloaded, replace anysearch-skill-3.1.1 with its extracted directory name.
In the terminal, begin post-install verification by checking Python first.
python --version # Need >= 3.6, requires `requests` library
Next, check Python 3; on many macOS systems this is the available Python executable.
python3 --version # Need >= 3.6, requires `requests` library
Next, check the alternative Node.js runtime. The first successful runtime check determines the preferred active CLI.
node --version # Need >= 12, no external dependencies
If Python and Node.js are unavailable, check the Shell fallback: PowerShell 5.1+ on Windows, or bash 3.2+ on Linux/macOS with jq and curl.
For each available Python runtime, run its corresponding terminal entry test. Replace <skill_dir> with ~/.claude/skills/anysearch.
python <skill_dir>/scripts/anysearch_cli.py doc
If python3 is available, run its terminal entry test too. Replace <skill_dir> with ~/.claude/skills/anysearch.
python3 <skill_dir>/scripts/anysearch_cli.py doc
If Node.js is available, run its terminal entry test too. Replace <skill_dir> with ~/.claude/skills/anysearch.
node <skill_dir>/scripts/anysearch_cli.js doc
If PowerShell on Windows is available, run its entry test. Replace <skill_dir> with ~/.claude/skills/anysearch, substituting your actual project or agent path where applicable.
powershell -ExecutionPolicy Bypass -File <skill_dir>/scripts/anysearch_cli.ps1 doc
If Bash on Linux/macOS is available, run its entry test. Replace <skill_dir> with ~/.claude/skills/anysearch, substituting your actual project or agent path where applicable.
bash <skill_dir>/scripts/anysearch_cli.sh doc
Record success and any errors or warnings for each available runtime. Select the runtime that succeeds with the cleanest output.
Write the selected runtime to runtime.conf. Replace <skill_dir> with ~/.claude/skills/anysearch; replace <RUNTIME> with Python, Node.js, PowerShell or Bash and <COMMAND> with the corresponding tested CLI command without the doc argument. Use the working python or python3 executable for Python.
echo "Runtime: <RUNTIME>" > <skill_dir>/runtime.conf echo "Command: <COMMAND>" >> <skill_dir>/runtime.conf
Installs: Complete AnySearch skill repository, installed as "anysearch" in OpenCode's user skill directory. · OpenCode
In a terminal, download the pinned v3.1.1 release. To use another release, replace v3.1.1 in the command with the latest tag from the repository's releases page.
curl -L -o anysearch-skill.zip https://github.com/anysearch-ai/anysearch-skill/archive/refs/tags/v3.1.1.zip
In the same terminal directory, extract the downloaded archive.
unzip anysearch-skill.zip
Using your file manager or terminal, move the extracted v3.1.1 directory into OpenCode's skill directory and rename it to anysearch. If another release was downloaded, replace anysearch-skill-3.1.1 with its extracted directory name.
In the terminal, begin post-install verification by checking Python first.
python --version # Need >= 3.6, requires `requests` library
Next, check Python 3; on many macOS systems this is the available Python executable.
python3 --version # Need >= 3.6, requires `requests` library
Next, check the alternative Node.js runtime. The first successful runtime check determines the preferred active CLI.
node --version # Need >= 12, no external dependencies
If Python and Node.js are unavailable, check the Shell fallback: PowerShell 5.1+ on Windows, or bash 3.2+ on Linux/macOS with jq and curl.
For each available Python runtime, run its corresponding terminal entry test. Replace <skill_dir> with ~/.config/opencode/skills/anysearch.
python <skill_dir>/scripts/anysearch_cli.py doc
If python3 is available, run its terminal entry test too. Replace <skill_dir> with ~/.config/opencode/skills/anysearch.
python3 <skill_dir>/scripts/anysearch_cli.py doc
If Node.js is available, run its terminal entry test too. Replace <skill_dir> with ~/.config/opencode/skills/anysearch.
node <skill_dir>/scripts/anysearch_cli.js doc
If PowerShell on Windows is available, run its entry test. Replace <skill_dir> with ~/.config/opencode/skills/anysearch, substituting your actual project or agent path where applicable.
powershell -ExecutionPolicy Bypass -File <skill_dir>/scripts/anysearch_cli.ps1 doc
If Bash on Linux/macOS is available, run its entry test. Replace <skill_dir> with ~/.config/opencode/skills/anysearch, substituting your actual project or agent path where applicable.
bash <skill_dir>/scripts/anysearch_cli.sh doc
Record success and any errors or warnings for each available runtime. Select the runtime that succeeds with the cleanest output.
Write the selected runtime to runtime.conf. Replace <skill_dir> with ~/.config/opencode/skills/anysearch; replace <RUNTIME> with Python, Node.js, PowerShell or Bash and <COMMAND> with the corresponding tested CLI command without the doc argument. Use the working python or python3 executable for Python.
echo "Runtime: <RUNTIME>" > <skill_dir>/runtime.conf echo "Command: <COMMAND>" >> <skill_dir>/runtime.conf
Installs: Complete AnySearch skill repository, installed as "anysearch" in one project's .skills directory. · Cursor, Windsurf
In a terminal, download the pinned v3.1.1 release. To use another release, replace v3.1.1 in the command with the latest tag from the repository's releases page.
curl -L -o anysearch-skill.zip https://github.com/anysearch-ai/anysearch-skill/archive/refs/tags/v3.1.1.zip
In the same terminal directory, extract the downloaded archive.
unzip anysearch-skill.zip
Using your file manager or terminal, replace <project> with the target project's path, then move the extracted directory into that project's .skills directory. If another release was downloaded, also replace anysearch-skill-3.1.1 with its extracted directory name.
In the terminal, begin post-install verification by checking Python first.
python --version # Need >= 3.6, requires `requests` library
Next, check Python 3; on many macOS systems this is the available Python executable.
python3 --version # Need >= 3.6, requires `requests` library
Next, check the alternative Node.js runtime. The first successful runtime check determines the preferred active CLI.
node --version # Need >= 12, no external dependencies
If Python and Node.js are unavailable, check the Shell fallback: PowerShell 5.1+ on Windows, or bash 3.2+ on Linux/macOS with jq and curl.
For each available Python runtime, run its corresponding terminal entry test. Replace <skill_dir> with the installed <project>/.skills/anysearch path, substituting the actual project path for <project>.
python <skill_dir>/scripts/anysearch_cli.py doc
If python3 is available, run its terminal entry test too. Replace <skill_dir> with the installed <project>/.skills/anysearch path, substituting the actual project path for <project>.
python3 <skill_dir>/scripts/anysearch_cli.py doc
If Node.js is available, run its terminal entry test too. Replace <skill_dir> with the installed <project>/.skills/anysearch path, substituting the actual project path for <project>.
node <skill_dir>/scripts/anysearch_cli.js doc
If PowerShell on Windows is available, run its entry test. Replace <skill_dir> with <project>/.skills/anysearch, substituting your actual project or agent path where applicable.
powershell -ExecutionPolicy Bypass -File <skill_dir>/scripts/anysearch_cli.ps1 doc
If Bash on Linux/macOS is available, run its entry test. Replace <skill_dir> with <project>/.skills/anysearch, substituting your actual project or agent path where applicable.
bash <skill_dir>/scripts/anysearch_cli.sh doc
Record success and any errors or warnings for each available runtime. Select the runtime that succeeds with the cleanest output.
Write the selected runtime to runtime.conf. Replace <skill_dir> with <project>/.skills/anysearch; replace <RUNTIME> with Python, Node.js, PowerShell or Bash and <COMMAND> with the corresponding tested CLI command without the doc argument. Use the working python or python3 executable for Python.
echo "Runtime: <RUNTIME>" > <skill_dir>/runtime.conf echo "Command: <COMMAND>" >> <skill_dir>/runtime.conf
Installs: Complete AnySearch skill repository, installed as "anysearch" in a user-selected agent skill directory. · Generic
In a terminal, download the pinned v3.1.1 release. To use another release, replace v3.1.1 in the command with the latest tag from the repository's releases page.
curl -L -o anysearch-skill.zip https://github.com/anysearch-ai/anysearch-skill/archive/refs/tags/v3.1.1.zip
In the same terminal directory, extract the downloaded archive.
unzip anysearch-skill.zip
Using your file manager or terminal, replace <your_agent_skill_dir> with the target agent's skill directory, then move and rename the extracted directory. If another release was downloaded, also replace anysearch-skill-3.1.1 with its extracted directory name.
In the terminal, begin post-install verification by checking Python first.
python --version # Need >= 3.6, requires `requests` library
Next, check Python 3; on many macOS systems this is the available Python executable.
python3 --version # Need >= 3.6, requires `requests` library
Next, check the alternative Node.js runtime. The first successful runtime check determines the preferred active CLI.
node --version # Need >= 12, no external dependencies
If Python and Node.js are unavailable, check the Shell fallback: PowerShell 5.1+ on Windows, or bash 3.2+ on Linux/macOS with jq and curl.
For each available Python runtime, run its corresponding terminal entry test. Replace <skill_dir> with <your_agent_skill_dir>/anysearch after substituting the actual agent skill directory.
python <skill_dir>/scripts/anysearch_cli.py doc
If python3 is available, run its terminal entry test too. Replace <skill_dir> with <your_agent_skill_dir>/anysearch after substituting the actual agent skill directory.
python3 <skill_dir>/scripts/anysearch_cli.py doc
If Node.js is available, run its terminal entry test too. Replace <skill_dir> with <your_agent_skill_dir>/anysearch after substituting the actual agent skill directory.
node <skill_dir>/scripts/anysearch_cli.js doc
If PowerShell on Windows is available, run its entry test. Replace <skill_dir> with <your_agent_skill_dir>/anysearch, substituting your actual project or agent path where applicable.
powershell -ExecutionPolicy Bypass -File <skill_dir>/scripts/anysearch_cli.ps1 doc
If Bash on Linux/macOS is available, run its entry test. Replace <skill_dir> with <your_agent_skill_dir>/anysearch, substituting your actual project or agent path where applicable.
bash <skill_dir>/scripts/anysearch_cli.sh doc
Record success and any errors or warnings for each available runtime. Select the runtime that succeeds with the cleanest output.
Write the selected runtime to runtime.conf. Replace <skill_dir> with <your_agent_skill_dir>/anysearch; replace <RUNTIME> with Python, Node.js, PowerShell or Bash and <COMMAND> with the corresponding tested CLI command without the doc argument. Use the working python or python3 executable for Python.
echo "Runtime: <RUNTIME>" > <skill_dir>/runtime.conf echo "Command: <COMMAND>" >> <skill_dir>/runtime.conf
Installs: Complete AnySearch skill repository, installed once as "anysearch" in the shared personal-agent skill directory used by multiple AI tools. · Codex, Cursor, OpenClaw
In a terminal, download the pinned v3.1.1 release. To use another release, replace v3.1.1 in the command with the latest tag from the repository's releases page.
curl -L -o anysearch-skill.zip https://github.com/anysearch-ai/anysearch-skill/archive/refs/tags/v3.1.1.zip
In the same terminal directory, extract the downloaded archive.
unzip anysearch-skill.zip
Using your file manager or terminal, move the extracted v3.1.1 directory into the shared agent skill directory and rename it to anysearch. If another release was downloaded, replace anysearch-skill-3.1.1 with its extracted directory name.
In the terminal, begin post-install verification by checking Python first.
python --version # Need >= 3.6, requires `requests` library
Next, check Python 3; on many macOS systems this is the available Python executable.
python3 --version # Need >= 3.6, requires `requests` library
Next, check the alternative Node.js runtime. The first successful runtime check determines the preferred active CLI.
node --version # Need >= 12, no external dependencies
If Python and Node.js are unavailable, check the Shell fallback: PowerShell 5.1+ on Windows, or bash 3.2+ on Linux/macOS with jq and curl.
For each available Python runtime, run its corresponding terminal entry test. Replace <skill_dir> with ~/.agents/skills/anysearch.
python <skill_dir>/scripts/anysearch_cli.py doc
If python3 is available, run its terminal entry test too. Replace <skill_dir> with ~/.agents/skills/anysearch.
python3 <skill_dir>/scripts/anysearch_cli.py doc
If Node.js is available, run its terminal entry test too. Replace <skill_dir> with ~/.agents/skills/anysearch.
node <skill_dir>/scripts/anysearch_cli.js doc
If PowerShell on Windows is available, run its entry test. Replace <skill_dir> with ~/.agents/skills/anysearch, substituting your actual project or agent path where applicable.
powershell -ExecutionPolicy Bypass -File <skill_dir>/scripts/anysearch_cli.ps1 doc
If Bash on Linux/macOS is available, run its entry test. Replace <skill_dir> with ~/.agents/skills/anysearch, substituting your actual project or agent path where applicable.
bash <skill_dir>/scripts/anysearch_cli.sh doc
Record success and any errors or warnings for each available runtime. Select the runtime that succeeds with the cleanest output.
Write the selected runtime to runtime.conf. Replace <skill_dir> with ~/.agents/skills/anysearch; replace <RUNTIME> with Python, Node.js, PowerShell or Bash and <COMMAND> with the corresponding tested CLI command without the doc argument. Use the working python or python3 executable for Python.
echo "Runtime: <RUNTIME>" > <skill_dir>/runtime.conf echo "Command: <COMMAND>" >> <skill_dir>/runtime.conf
Uses anysearch
Use the anysearch skill to search for "<topic or question>" with at most 5 results. Give me a concise summary of what you find and cross-reference any factual claims that appear uncertain or disputed.
Claude
Codex
Cursor
OpenClaw
Windsurf
OpenCode