agentleFS
JinchengGao-InftyJinchengGao-Infty/agent-loadout/skills/grok-search/SKILL.md

grok-search

Skill3 starsChanged 8 months agoMITView on GitHub

Search the web for real-time information using dual engines: Grok AI (deep analysis + live web) and Tavily (structured results + web scraping). Use when needing current news, prices, latest releases, or any info beyond training data cutoff. Chinese triggers: 搜索, 搜一下, 查一下, 查查, 看看有没有, 最新, 新闻, grok搜索, 网上搜, 帮我查, 了解一下, 什么价格, 上线了吗, 发布了吗.

  • Reads credentials

10 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run both in parallel for important queries, then compare results.

    line 98
  2. Distinctive:

    If relying on a single source, explicitly state this limitation

    line 105
  3. Distinctive:

    When sources conflict: present both sides, assess credibility and recency

    line 107

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Prerequisites

Set these environment variables before use:

  • GROK_API_BASE — Your Grok-compatible API endpoint (e.g., http://localhost:8100/v1)
  • GROK_API_KEY — Your API key for the Grok endpoint
  • TAVILY_API_KEY — Your Tavily API key (get one free at tavily.com)

Instructions

Search for: $ARGUMENTS


Step 1: Do I Need to Search?

Yes — search when:

  • User explicitly asks for external info
  • Real-time data needed (latest versions, recent events, current prices)
  • Need to verify knowledge accuracy
  • Specific URLs, projects, or products' current status

No — skip when:

  • Pure code writing/debugging with sufficient context
  • User explicitly says not to search

Step 2: Choose Engine

ScenarioEngineWhy
Simple fact lookupTavilyFast, structured, scored results
Complex / controversial topicDual (both)Cross-verify, reduce hallucination
Need AI deep analysisGrokBuilt-in web search + reasoning
Latest newsTavily (topic=news)News mode optimized
Scrape specific URLTavily ExtractFull page content as Markdown
High-stakes decisionDual (both)≥2 sources required

Step 3: Execute

Grok Search (AI-driven, deep analysis)

curl -s ${GROK_API_BASE}/chat/completions \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer ${GROK_API_KEY}" \
  -d '{
    "model": "grok-3",
    "messages": [
      {"role": "system", "content": "You are a search assistant. Search the web and provide accurate, well-sourced answers."},
      {"role": "user", "content": "SEARCH_QUERY"}
    ],
    "stream": false
  }' | jq -r '.choices[0].message.content'

Tavily Search (structured results)

curl -s "https://api.tavily.com/search" \
  -H "Content-Type: application/json" \
  -d '{
    "api_key": "'${TAVILY_API_KEY}'",
    "query": "SEARCH_QUERY",
    "search_depth": "basic",
    "max_results": 5,
    "include_answer": true
  }' | jq '{answer: .answer, results: [.results[] | {title, url, content, score}]}'

Options:

  • search_depth: basic (fast) or advanced (thorough)
  • topic: general (default), news, finance
  • max_results: 1-20
  • time_range: day, week, month, year

Tavily Extract (scrape a URL)

curl -s "https://api.tavily.com/extract" \
  -H "Content-Type: application/json" \
  -d '{
    "api_key": "'${TAVILY_API_KEY}'",
    "urls": ["https://example.com/page"],
    "extract_depth": "basic"
  }' | jq '.results[] | {url, raw_content}'

Dual Search (cross-verify)

Run both in parallel for important queries, then compare results.


Evidence Standards

  • All factual conclusions need ≥2 independent sources for cross-verification
  • If relying on a single source, explicitly state this limitation
  • Prefer: official docs, Wikipedia, academic databases, authoritative media
  • When sources conflict: present both sides, assess credibility and recency
  • Confidence levels: High (multiple sources agree) · Medium (few sources) · Low (single source)

Search Complexity

LevelDescriptionStrategy
L1 - SimpleSingle fact, one querySingle engine, direct answer
L2 - MediumMultiple aspectsPrimary engine + follow-up
L3 - ComplexMulti-facetedDual search + structured planning

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.