botlearn-google-search
v1.0.0Constructs and executes precise, multi-query Google searches using advanced operators to retrieve, filter, and rank credible, up-to-date sources.
⭐ 0· 308·1 current·1 all-time
by邢怀康@calvinxhk
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name, description, skill.md, strategies, and knowledge docs consistently describe constructing advanced Google queries, decomposing queries, deduplicating and ranking results. No unrelated binaries, credentials, or config paths are requested.
Instruction Scope
The SKILL.md and strategies describe constructing queries, executing them, collecting top results, and filtering/ranking, but they do not specify how to execute searches (no prescribed API, no target endpoints, no tool or rate-limit guidance, and no mention of respecting provider terms or privacy). This leaves broad discretion to the agent/runtime about which network tools or endpoints to use, which could lead to unexpected behavior if the agent has access to arbitrary web/network tools.
Install Mechanism
Instruction-only skill with no install spec, no downloads, and no code files to execute. This is the lowest-risk install surface.
Credentials
The package does not request environment variables, credentials, or config paths. There are no apparent requests for unrelated secrets or external service tokens that would be disproportionate to a search-query helper.
Persistence & Privilege
always is false and the skill is user-invocable; it can be invoked autonomously by the model (platform default) but it does not request persistent privileges, system modifications, or cross-skill configuration changes.
Assessment
This skill is internally consistent for constructing and ranking search queries, but it is implementation-agnostic about how searches are performed. Before installing: 1) Confirm which tool your agent will use to actually run queries (built-in browser, Google Custom Search API, SerpAPI, curl, etc.) and whether that tool requires separate credentials or has privacy/usage costs. 2) Ensure the agent/tool will not accidentally send sensitive or private data to public search engines — avoid sending PII, secrets, or confidential documents as raw search terms. 3) If you require compliance with Google terms or rate limits, prefer a well-defined provider (Google CSE or an audited SERP provider) and add explicit rate-limit and TOS-respect guidance. 4) Test the skill in a controlled environment (use the included smoke tasks) to verify where queries are executed and what network endpoints are contacted. If you need the skill to use only vetted endpoints, ask the maintainer to explicitly document the execution mechanism or to add an adapter that uses your approved search API.Like a lobster shell, security has layers — review code before you run it.
latestvk978z0eqnt20389zc2v09f7jfs8236cp
License
MIT-0
Free to use, modify, and redistribute. No attribution required.