agentleFS
glebisglebis/claude-skills/google-image-search/SKILL.md

google-image-search

Skill400 starsChanged 4 months agoMITView on GitHub

Search and download images via Google Custom Search API with LLM-powered selection. This skill should be used when finding images for articles, presentations, research documents, or enriching Obsidian notes with relevant visuals. Supports simple queries, batch processing from JSON config, automatic config generation from terms, and full note enrichment with automatic image insertion below headings.

  • Reads credentials

We split this skill into the rules it gives an agent

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

  • 5

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    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. Common:

    Search for images using Google Custom Search API with intelligent scoring and LLM-based selection.

    line 8
  2. Common:

    Search for a single term:

    line 49
  3. Common:

    Create JSON config from a list of terms using LLM:

    line 71
  4. Common:

    After scoring, LLM picks the best image from top candidates based on:

    line 147
  5. Common:

    When in an Obsidian vault:

    line 156

“Common” is measured: kept by at least 6 in 10 of the 3 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

Google Image Search Skill

Search for images using Google Custom Search API with intelligent scoring and LLM-based selection.

When to Use

  • Finding images to illustrate technical articles or research
  • Adding visuals to presentations
  • Enriching Obsidian notes with relevant images
  • Batch image search for multiple topics
  • Generating image search configs from plain text lists

Requirements

  • Google Custom Search API key and Search Engine ID
  • OpenRouter API key (for LLM selection)
  • llm CLI installed at /opt/homebrew/bin/llm

Store credentials in .env:

Google-Custom-Search-JSON-API-KEY=your_key
Google-Custom-Search-CX=your_cx
OPENROUTER-API-KEY=your_openrouter_key

(The OPENROUTER_API_KEY=... spelling works too — see the plugin note below.)

OpenRouter / llm-openrouter caveat

The llm-openrouter plugin only registers its models when it can read a key named OPENROUTER_KEY (env var or llm keys set openrouter). With only OPENROUTER_API_KEY set, llm models list shows zero OpenRouter models and every openrouter/... name fails with Unknown model — the script then silently falls back to keyword scoring. llm_select.py sets both names for the subprocess, so this is handled; if selection ever regresses, check OPENROUTER_KEY first:

llm models list | grep -c openrouter   # 458+ means the plugin registered its models

Modes of Operation

1. Simple Query

Search for a single term:

python3 ~/.claude/skills/google-image-search/scripts/google_image_search.py \
  --query "neural interface wearable device" \
  --output-dir ./images \
  --num-results 5

2. Batch Processing

Process multiple queries from JSON config:

python3 ~/.claude/skills/google-image-search/scripts/google_image_search.py \
  --config image_queries.json \
  --output-dir ./images \
  --llm-select

3. Generate Config from Terms

Create JSON config from a list of terms using LLM:

python3 ~/.claude/skills/google-image-search/scripts/google_image_search.py \
  --generate-config \
  --terms "AlterEgo wearable" "sEMG electrodes" "BCI headset" \
  --output my_queries.json

4. Enrich Obsidian Note

Extract visual terms from note, find images, and insert below headings:

python3 ~/.claude/skills/google-image-search/scripts/google_image_search.py \
  --enrich-note ~/Brains/brain/Research/neural-interfaces.md

This mode:

  1. Detects Obsidian vault and attachments folder
  2. Uses LLM to extract visual-worthy terms from note
  3. Searches for images for each term
  4. Downloads best images to attachments folder
  5. Inserts image embeds below relevant headings
  6. Creates backup before modifying note

Key Options

OptionDescription
--query TEXTSimple single query
--config FILEJSON config for batch
--generate-configGenerate config from --terms
--enrich-note FILEEnrich Obsidian note
--output-dir DIRWhere to save images
--urls-onlyReturn URLs only, no download
--llm-selectUse LLM to pick best image (default: on)
--no-llm-selectDisable LLM selection
--num-results NResults per query (default: 5)
--dry-runShow what would be done

JSON Config Format

Each entry supports:

{
  "id": "unique-id",
  "heading": "Display Heading",
  "description": "Context for what image to find",
  "query": "Google search query",
  "numResults": 5,
  "selectionCriteria": "What makes a good image",
  "requiredTerms": ["must", "have"],
  "optionalTerms": ["bonus", "terms"],
  "excludeTerms": ["stock", "clipart"],
  "preferredHosts": ["official-site.com"],
  "selectionCount": 2
}

See references/api_config_reference.md for full documentation.

Scoring System

Images are scored based on:

  • Required terms: -80 if missing, +30 if all present
  • Optional terms: +5 per match
  • Exclude terms: -50 per match
  • Preferred hosts: +25 if trusted, -5 if unknown
  • MIME type: +5 for PNG/JPEG, -10 for GIF
  • Resolution: +10 for high res, -10 for low res
  • File size: -5 if very small

LLM Selection

After scoring, LLM picks the best image from top candidates based on:

  • Title and URL metadata
  • Scoring reasons
  • Selection criteria

The LLM evaluates authenticity, clarity, and relevance for technical audiences.

Obsidian Integration

When in an Obsidian vault:

  • Auto-detects vault root via .obsidian folder
  • Uses configured attachments folder (default: Attachments)
  • Generates Obsidian-style embeds: ![[image.png|alt text]]
  • Creates backup before modifying notes

Script Files

FilePurpose
google_image_search.pyMain entry point
api.pyGoogle Custom Search API
config.pyCredentials and config handling
download.pyImage download with magic bytes
evaluate.pyKeyword-based scoring
llm_select.pyLLM selection and term extraction
obsidian.pyVault detection and enrichment
output.pyMarkdown output generation

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.