X Search 1.0.0

Search X (Twitter) posts using the xAI API. Use when the user wants to find tweets, search X/Twitter, look up what people are saying on X, or find social med...

Security Scan

The skill is largely coherent for searching X via the xAI Responses API and only requires the expected XAI_API_KEY and python3, but there are small inconsistencies in metadata/instructions that you should verify before installing.

Purpose & Capability

Name/description, required binary (python3), and required env var (XAI_API_KEY) align with contacting the x.ai Responses (Grok) API to perform searches. The API endpoint (https://api.x.ai/v1/responses) and model usage in code match the stated purpose.

Instruction Scope

SKILL.md instructs only to set XAI_API_KEY and run the included script, which is what the code does. Minor inconsistency: SKILL.md suggests you can set skills."x-search".apiKey or skills."x-search".env.XAI_API_KEY in ~/.openclaw/openclaw.json, but the provided search.py reads only the XAI_API_KEY environment variable and does not read that config file. Also the _meta.json ownerId differs from the registry ownerId in the supplied metadata (two different owner IDs), which is a metadata mismatch worth checking with the publisher.

Install Mechanism

Install spec is a single Homebrew formula for python (standard). No downloads from unknown hosts and no archive extraction; code files are included in the skill package.

Credentials

The skill requests one credential (XAI_API_KEY) which is the expected credential for the xAI API. No other secrets or unrelated environment variables are required.

Persistence & Privilege

The skill does not request always:true and is user-invocable; it does not modify other skills or system configs. It runs on demand and only needs the environment variable to operate.

What to consider before installing

This skill appears to do what it says (search X via xAI/Grok) and only needs your XAI_API_KEY and python3. Before installing: 1) Confirm you trust the skill publisher — the package metadata includes two different ownerId values (registry vs _meta.json) which you may want to verify. 2) Note SKILL.md mentions storing the key in ~/.openclaw/openclaw.json, but the script only reads XAI_API_KEY from the environment — if you set the key only in the JSON config it may not be picked up. 3) Limit the API key's permissions if possible and check your x.ai console for usage after first runs. 4) You can review and run the included tests (scripts/test_search.py) locally to confirm behavior before giving the key to this environment. 5) If you need higher assurance, ask the publisher to reconcile the ownerId mismatch and confirm whether the skill intends to read ~/.openclaw/openclaw.json.

X Search

Search X (Twitter) posts using the xAI Grok API with real-time access to X content.

Setup

1. Get your API key: https://console.x.ai
2. Set environment variable:

   export XAI_API_KEY="xai-your-key-here"
   

3. Or set skills."x-search".apiKey / skills."x-search".env.XAI_API_KEY in ~/.openclaw/openclaw.json

Usage

python3 {baseDir}/scripts/search.py "what is trending in AI right now"

Useful flags:

# Filter by handles (max 10)
python3 {baseDir}/scripts/search.py --handles jaaneek,OpenClaw "latest posts"

# Exclude handles (max 10)
python3 {baseDir}/scripts/search.py --exclude spambot,crypto_shill "trending AI"

# Date range (YYYY-MM-DD)
python3 {baseDir}/scripts/search.py --from 2026-03-01 --to 2026-03-20 "xAI grok updates"

# Enable image/video understanding in posts
python3 {baseDir}/scripts/search.py --images --video "product demos"

Notes

• Uses the xAI Responses API with x_search tool (Grok performs the search and summarizes results)
• Cannot use --handles and --exclude at the same time
• Results include citations with links to original X posts
• Present results in a readable format with post content, authors, and citations