Overview

Provides real-time X/Twitter search within OpenClaw by calling xAI’s Grok x_search tool, returning actual tweets (with URLs and metadata) filtered by time, handles, and output format.

Key Advantages

1.Real-time access to live X/Twitter discussions instead of static web results.

2.Direct integration with xAI’s /v1/responses API using grok-4-1-fast, optimized for agentic search workflows.

3.Flexible filtering by time window (days) and by specific handles or excluded handles.

4.Multiple output formats (full JSON, compact tweet view, links-only) for different downstream use cases.

5.Simple configuration via XAI_API_KEY and optional environment variables for model and default time window.

Use Cases

Monitoring what people are currently saying about a product, company, or technology on X/Twitter.
Pulling recent tweets from specific accounts (e.g., founders, projects, news outlets) for research or dashboards.
Tracking short-term trends around a topic (e.g., “AI trending today” with a 1-day window).
Gathering example tweets and links for content curation, newsletters, or reports.
Augmenting an agent’s reasoning with fresh, citation-backed social media signals in workflows that need real-time context.

Evaluation History (1)

7.6/103/19/2026linux-arm64

▼

OS: linux-arm64LLM: z-ai/glm-4.5-air

**Quick judgement** A focused and practical skill for real-time X/Twitter search via xAI’s Grok models. It’s well-suited for agents or workflows that need fresh social media context with clear citations, given an appropriate xAI API key. **Key strengths** - Returns real tweets with URLs, usernames, timestamps, and citations. - Good control over recency (`--days`) and account-based filters (`--handles`, `--exclude`). - Output modes (`--json`, `--compact`, `--links-only`) make it convenient for both human review and downstream automation. **Risks / limitations** - Depends entirely on xAI’s API availability, rate limits, and search quality; outages or policy changes will break or degrade the skill. - No built-in moderation or content filtering is described; results may include toxic, NSFW, or misleading content from X/Twitter. - Requires proper handling of the secret `XAI_API_KEY`; misconfiguration or leakage could incur unwanted usage or costs. **Recommended scenarios** - Agents that need up-to-the-minute social sentiment or discussions to complement web search or static knowledge. - Developer or research workflows where cited, verifiable X/Twitter content is important (e.g., checking claims, gathering examples). - Monitoring or exploration tasks (trends, announcements, niche community chatter) where some content risk is acceptable and can be handled at the application layer.

Search X

Overview

Key Advantages

Use Cases

Evaluation Scores

Download Trend

Evaluation History (1)

Comments (0)

Post a Comment