xAI Search

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.

What this means

A single query may result in multiple external search operations through Grok.

Why it was flagged

The skill enables provider-side search tools and discloses that one request may trigger multiple search calls. This is central to the search purpose and not evidence of hidden or unsafe tool use.

Skill content
This leverages Grok's `web_search` and `x_search` tools. ... The model will make multiple search calls if needed (agentic)
Recommendation

Use the skill for intended searches and provide clear query scope or filters when needed.

What this means

Using the skill consumes authority associated with the xAI API key you provide.

Why it was flagged

The helper script reads an xAI API key from the environment to authenticate to the provider. This is expected for the integration, but it is sensitive account access and the registry metadata lists no primary credential.

Skill content
api_key = os.environ.get("XAI_API_KEY") ... client = Client(api_key=api_key)
Recommendation

Set XAI_API_KEY deliberately, use a restricted or rotatable key if available, and remove or revoke it when no longer needed.

What this means

The installed SDK version may vary depending on what pip resolves at install time.

Why it was flagged

The setup uses an unpinned pip dependency. This is a normal, user-directed install for the stated purpose, but package version and provenance are not locked by the artifact.

Skill content
Python 3 + xai-sdk: `pip install xai-sdk`
Recommendation

Install from a trusted package source, consider using a virtual environment, and pin or review the xai-sdk version if reproducibility matters.

What this means

Search terms and any information typed into the query leave the local environment and are processed by xAI/Grok.

Why it was flagged

The documented workflow sends the user's query content to xAI's external API. This is disclosed and purpose-aligned, but users should treat submitted queries as provider-shared data.

Skill content
curl -s https://api.x.ai/v1/chat/completions ... "messages": [{"role": "user", "content": "YOUR QUERY HERE"}]
Recommendation

Avoid putting secrets or unnecessary private information into searches, and review xAI's data handling terms if that matters for your use case.