mcpField
O
openclaw-grok-search

openclaw-grok-search

github.com/stemmakerProductivity5135 installsUpdated 36w ago
Repository

About openclaw-grok-search

A project-local skill for running Grok-backed web research and returning structured JSON with content and sources. It is intended for agents that need current information, documentation links, or evidence for troubleshooting.

Key features

  1. 01Cross-platform web research
  2. 02Structured JSON output
  3. 03Configurable CLI and environment settings
  4. 04Retry after a failed search

Use cases

  1. 01Checking recent releases or compatibility
  2. 02Finding official documentation and source URLs
  3. 03Researching evidence for error analysis

MCP support

The skill directs agents to use GrokSearch tools or CLI rather than built-in WebSearch or WebFetch.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/stemmaker/openclaw-grok-search --skill openclaw-grok-search

After installing, type/openclaw-grok-searchin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

README.md
config.example.json
scripts/
grok_search.py
configure.py

Details

From the project README

Openclaw Grok Search

Run cross-platform web research and return structured JSON output with content and sources. This skill is project-local and should run directly from the downloaded project directory.

When to Use

Use this skill before answering when any of these apply:

  1. The user asks for latest/current/today/recent information.
  2. The answer depends on versions, releases, changelogs, or compatibility.
  3. The task needs official docs, API references, or source URLs.
  4. The user reports an error and root-cause analysis needs web evidence.
  5. You are uncertain and need external confirmation before final output.

Quick Start

  1. Write config interactively (first run only).
python scripts/configure.py
  1. Run a query.
python scripts/grok_search.py --query "What changed in Python recently?"

Config Priority

  1. CLI args such as --base-url and --api-key
  2. Environment vars GROK_*
  3. Config files

Default config lookup order:

  1. config.json
  2. config.local.json

Cross-Platform Rules

  1. Prefer python ... commands, do not require PowerShell-only syntax.
  2. Keep config in the project folder, do not install or copy into ~/.codex.
  3. Support GROK_CONFIG_PATH only when you explicitly want a custom path.

Output Shape

Always print JSON with:

  1. ok
  2. content
  3. sources
  4. raw

Anti-Patterns

ProhibitedCorrect
No source citationInclude Source [<sup>1</sup>](URL)
Give up after one failureRetry at least once
Use built-in WebSearch/WebFetchUse GrokSearch tools/CLI

Comments

Markdown supported