search1api
AdvisoryAudited by Static analysis on Apr 30, 2026.
Overview
No suspicious patterns detected.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Installing the CLI adds an external executable that will handle the skill's searches, crawls, and API calls.
The skill depends on an external globally installed npm CLI that is not included in the reviewed artifacts; this is a normal setup pattern for a CLI integration, but users must trust the package source.
If not, guide the user to install it: npm install -g search1api-cli
Install the CLI only from a trusted npm source, verify the package and publisher, and avoid installing or running it with unnecessary privileges.
Using the skill may consume API credits or expose the key if it is mishandled outside this skill.
The skill requires a Search1API credential, which is expected for the service but gives the CLI access to the user's Search1API account and credits.
An API key is also required... s1 config set-key <your-api-key> ... Or set the environment variable SEARCH1API_KEY.
Use a dedicated API key if possible, keep it secret, monitor usage, and rotate it if it may have been shared.
Sensitive prompts, private text, or confidential URLs included in these commands may be processed by external services.
The reasoning command can send user-provided content through the CLI to an external reasoning provider, so data boundaries depend on Search1API/DeepSeek handling.
s1 reasoning "<content>" Deep thinking powered by DeepSeek R1. Use for complex analytical questions.
Avoid sending secrets or private data through search, crawl, or reasoning commands unless you are comfortable with the provider's privacy and retention practices.