Agent skill

Google Search

by team-attention in team-attention/hoyeon

Google search via real Chrome browser (chromux). An agent skill from team-attention/hoyeon.

MITAuto-check passedProductivity & Automation

Install Google Search

skills CLI

$ npx skills add team-attention/hoyeon --skill google-search -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install team-attention/hoyeon google-search --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/google-search .claude/skills/google-search && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "google-search" agent skill from https://github.com/team-attention/hoyeon/tree/main/skills/google-search into .claude/skills/google-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-search", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/team-attention/hoyeon/tree/main/skills/google-search

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add team-attention/hoyeon --skill google-search -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install team-attention/hoyeon google-search --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/google-search .agents/skills/google-search && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "google-search" agent skill from https://github.com/team-attention/hoyeon/tree/main/skills/google-search into .agents/skills/google-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-search", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add team-attention/hoyeon --skill google-search -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install team-attention/hoyeon google-search --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/google-search .cursor/skills/google-search && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "google-search" agent skill from https://github.com/team-attention/hoyeon/tree/main/skills/google-search into .cursor/skills/google-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-search", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/team-attention/hoyeon.git --path skills/google-search

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add team-attention/hoyeon --skill google-search -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install team-attention/hoyeon google-search --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/google-search .gemini/skills/google-search && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "google-search" agent skill from https://github.com/team-attention/hoyeon/tree/main/skills/google-search into .gemini/skills/google-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-search", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install team-attention/hoyeon google-search

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add team-attention/hoyeon --skill google-search -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/google-search .github/skills/google-search && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "google-search" agent skill from https://github.com/team-attention/hoyeon/tree/main/skills/google-search into .github/skills/google-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-search", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add team-attention/hoyeon --skill google-search -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install team-attention/hoyeon google-search --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/google-search .opencode/skills/google-search && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "google-search" agent skill from https://github.com/team-attention/hoyeon/tree/main/skills/google-search into .opencode/skills/google-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-search", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: google-search
GitHub stars: 173
Token cost: ~1.3k tokens
SKILL.md length: 397 words
Files: 2
Skills in repo: 36
Repo updated: May 21, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Google search via real Chrome browser (chromux). An agent skill from team-attention/hoyeon.

The user asks to search Google
SKILL.md covers Runtime Surface, When to Use, Prerequisites and Usage, plus 4 more sections
Runs JavaScript scripts from its folder; calls node
Find articles about

What it does

Google Search is an agent skill from team-attention/hoyeon. Google search via real Chrome browser (chromux). Use when the user asks to "search Google", "구글 검색", "구글에서 찾아줘", "find articles about", "search the web for", or needs web search results with full page content. Also trigger when: searching a specific site ("search dev.to for..."), finding recent articles/posts about a topic, extracting content from search results, or when WebSearch results are insufficient and real browser rendering is needed. Prefer this over WebSearch when the user wants site-specific search…

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files.

It sits in Productivity & Automation, covering Web search. The repository describes itself as: Requirements-first Harness — derive, verify, execute. The licence is MIT.

When your agent uses it

The user asks to search Google
Find articles about
Search the web for
Needs web search results with full page content

Example prompts

“search Google”
“find articles about”
“search the web for”
“/google-search”

Requirements

Node.js

What it can do on your machine

Read from SKILL.md and the folder at commit 7cff032. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships script files (JavaScript), which the agent can run.
Shell commands in SKILL.md call:
- node
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Google Search loads about 1.3k tokens when it runs. Until then it costs about 149 tokens; SKILL.md has 397 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~149
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from team-attention/hoyeon at commit 7cff032, republished under its MIT licence (© team-attention). 397 words, ~1,252 tokens.

Download SKILL.mdSave it as .claude/skills/google-search/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: google-search
description: Google search via real Chrome browser (chromux). Use when the user asks to "search Google", "구글 검색", "구글에서 찾아줘", "find articles about", "search the web for", or needs web search results with full page content. Also trigger when: searching a specific site ("search dev.to for..."), finding recent articles/posts about a topic, extracting content from search results, or when WebSearch results are insufficient and real browser rendering is needed. Prefer this over WebSearch when the user wants site-specific search, time-filtered results, or full article body/comments extraction.

Google Search (chromux)

Search Google and optionally extract full page content using a real Chrome browser via chromux. Unlike WebSearch, this uses an actual Chrome instance — same results a human would see, with JavaScript-rendered content and no bot detection.

Runtime Surface

Claude Code

Use the bundled chromux search script and fall back to WebSearch when chromux is unavailable.

Codex

Use Bash-first chromux operations. Do not add Hoyeon MCP for v1.
Resolve the script relative to the Hoyeon plugin root: skills/google-search/vendor/web-search.mjs.
If chromux is unavailable, use the current Codex web search surface when available and state that enrichment/body/comment extraction is degraded.

When to Use

User asks to search Google or the web for something
Need site: operator to search within a specific domain
Need time-filtered results (past day/week/month/year)
Need full article body and comments, not just snippets
WebSearch gives poor results and real browser search would help

Prerequisites

Requires chromux CLI installed. Launch headless Chrome before use:

bash

chromux launch default --headless 2>/dev/null || true

This starts Chrome without a visible window. Skips if already running.

Usage

bash

node ${baseDir}/vendor/web-search.mjs "<query>" [options]

Options

Flag	Description	Default
`--site <domain>`	Add `site:` filter (e.g. `dev.to`, `stackoverflow.com`)	none
`--time <d\|w\|m\|y>`	Time filter: day, week, month, year	none (all time)
`--count <N>`	Max results	`10`
`--no-enrich`	Skip page visits, return Google snippets only (faster)	enrichment on
`--comments <N>`	Max comments to extract per page	`5`
`--body <N>`	Max body chars to extract per page	`500`
`--json`	Output raw JSON instead of text	text
`--check`	Verify chromux is available	-

Show full SKILL.md (157 more words)Show less

Examples

Basic search:

bash

node ${baseDir}/vendor/web-search.mjs "react server components best practices" --count 5

Site-specific search:

bash

node ${baseDir}/vendor/web-search.mjs "authentication patterns" --site stackoverflow.com --count 10

Quick search (snippets only, no page visits):

bash

node ${baseDir}/vendor/web-search.mjs "bun vs deno 2024" --no-enrich --count 10

Time-filtered search:

bash

node ${baseDir}/vendor/web-search.mjs "openai o3 release" --time w --count 5

Full content extraction with JSON output:

bash

node ${baseDir}/vendor/web-search.mjs "claude code tips" --site dev.to --comments 5 --body 1000 --json

Output Format

Text mode (default)

[1] Article Title Here
    URL: https://example.com/article
    Author: John Doe
    Tags: javascript, react
    Body: First 500 chars of article body...
    Comments (3):
      1. commenter1: Comment text here...
      2. commenter2: Another comment...

[2] Another Article
    URL: https://example.com/other
    ...

JSON mode (`--json`)

Returns an array of objects:

json

[
  {
    "title": "Article Title",
    "url": "https://example.com/article",
    "snippet": "Google search snippet",
    "author": "John Doe",
    "tags": ["javascript", "react"],
    "body": "Full article body text...",
    "comments": [
      {"author": "commenter1", "text": "Comment text..."}
    ]
  }
]

Fields like author, tags, body, comments are only present when enrichment is enabled. The enrichment extracts content using site-specific JS extractors for Dev.to and Lobsters, with a generic fallback for other sites.

Performance Notes

No enrichment (--no-enrich): ~3-5 seconds (Google search only)
With enrichment: ~2-3 seconds per result page (sequential visits)
For 10 results with enrichment: ~25-35 seconds total
Use --no-enrich when you only need URLs and snippets
Use --count to limit results when enrichment is on

Error Handling

Situation	Behavior
chromux not installed	`--check` returns `available: false`
Google CAPTCHA	Returns 0 results, retry later
Page load timeout during enrichment	Skips that URL, continues with others
No results found	Returns empty array/output

Fallback

If chromux is unavailable, fall back to the built-in WebSearch tool.

Files

SKILL.md and 1 other file in skills/google-search of team-attention/hoyeon.

SKILL.md
vendor/web-search.mjs

Open the folder on GitHubat commit 7cff032

Compare with similar skills

Google Search next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Google Search compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Google Search this skillteam-attention/hoyeon	173	—	~1.3k	Automated safety check: Pass	MIT	4 mo ago
Brave Searchbadlogic/pi-skills	2.6k	5 repos	~592	Automated safety check: Pass	MIT	4 mo ago
Enterprise AI Scenario MapMetaInFLow/Enterprise-ai-scenario-map-skill	632	—	~1.8k	Automated safety check: Pass	MIT	6 mo ago
Web Searchjjyaoao/HelloAgents	3.2k	1 repos	~5.6k	Automated safety check: Pass	MIT	4 days ago
Ddg SearchTheSyart/claude-agent-examples	407	1 repos	~493	Automated safety check: Pass	None	2 mo ago
Local Web SearchuluckyXH/OpenMOSS	1.3k	—	~392	Automated safety check: Notes	MIT	3 mo ago

Similar skills

Brave Search
badlogic/pi-skills
Web search and content extraction via Brave Search API. An agent skill from badlogic/pi-skills.
2.6k GitHub starsUsed in 5 repos~592 tokens
Productivity & AutomationAuto-check passed
Enterprise AI Scenario Map
MetaInFLow/Enterprise-ai-scenario-map-skill
企业AI场景地图生成报告工具。通过 web-search 深度调研企业信息，按照V2.1标准模板生成结构化AI应用场景地图报告，包含企业画像、业务诊断、行业实践、AI场景全量表、实施路径等完整内容。
632 GitHub stars~1.8k tokensUpdated 6 mo ago
Productivity & AutomationAuto-check passed
Web Search
jjyaoao/HelloAgents
Implement web search capabilities using the z-ai-web-dev-sdk.
3.2k GitHub starsUsed in 1 repo~5.6k tokens
Productivity & AutomationAuto-check passed
Ddg Search
TheSyart/claude-agent-examples
Web search without an API key using DuckDuckGo Lite via webfetch.
407 GitHub starsUsed in 1 repo~493 tokens
Productivity & AutomationAuto-check passed
Local Web Search
uluckyXH/OpenMOSS
A skill your agent uses when the user asks for web search that should run via the local-160 Responses API with websearch tool (base URL like https://proxy.example.com, model gpt-5.2-codex(xhigh)).
1.3k GitHub stars~392 tokensUpdated 3 mo ago
Productivity & AutomationAuto-check: notes
Ask Search
ythx-101/ask-search
Web search via self-hosted SearxNG. An agent skill from ythx-101/ask-search.
538 GitHub stars~332 tokensUpdated 6 mo ago
Productivity & AutomationAuto-check passed

More from team-attention/hoyeon

All 36 skills in this repo

Skill Session Analyzer
team-attention/hoyeon
This skill should be used when the user asks to "analyze session", "evaluate skill execution", "check session logs", provides a session ID with a skill path, or wants to verify that a skill executed…
173 GitHub stars~1.9k tokensUpdated 4 mo ago
Auto-check: notes
Browser Work
team-attention/hoyeon
Recon-first browser automation. An agent skill from team-attention/hoyeon.
173 GitHub stars~1.9k tokensUpdated 4 mo ago
Auto-check passed
Check
team-attention/hoyeon
This skill should be used when the user wants to verify their changes before pushing, or update the project's rule checklists.
173 GitHub stars~1.8k tokensUpdated 4 mo ago
Auto-check: notes
Compound
team-attention/hoyeon
This skill should be used when the user says "/compound", "compound this", "document learnings", "save what we learned", or after completing a PR.
173 GitHub stars~1.1k tokensUpdated 4 mo ago
Auto-check: notes
QA
team-attention/hoyeon
Systematically QA test any application — web apps, native macOS apps, Electron apps, CLI tools, interactive REPLs, or anything on screen.
173 GitHub stars~2.6k tokensUpdated 4 mo ago
Auto-check: notes
Tech Decision
team-attention/hoyeon
This skill should be used when the user asks about "technical decision", "what to use", "A vs B", "comparison analysis", "library selection", "architecture decision", "which one to use"…
173 GitHub stars~1.4k tokensUpdated 4 mo ago
Auto-check passed

Questions about Google Search

What does Google Search do?

Google search via real Chrome browser (chromux). An agent skill from team-attention/hoyeon. Google Search is an agent skill from team-attention/hoyeon. Google search via real Chrome browser (chromux).

When should I use Google Search?

Google Search fits situations like: the user asks to search Google; find articles about; search the web for; needs web search results with full page content.

How do I install Google Search in Claude Code?

Run `npx skills add team-attention/hoyeon --skill google-search -a claude-code`. Or copy the skill folder (skills/google-search in team-attention/hoyeon) into .claude/skills/google-search in your project. Claude Code loads it when a task matches its description.

How do I install Google Search in Codex?

Run `npx skills add team-attention/hoyeon --skill google-search -a codex`. Or copy the skill folder (skills/google-search in team-attention/hoyeon) into .agents/skills/google-search in your project. Codex loads it when a task matches its description.

Can I use Google Search in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add team-attention/hoyeon --skill google-search -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/google-search, .gemini/skills/google-search, .github/skills/google-search and .opencode/skills/google-search in your project.

What does Google Search need to run?

Going by SKILL.md and its folder, Google Search needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node). Our summary lists: Node.js.

Does Google Search access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Google Search safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Google Search use?

Google Search is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Google Search use?

About 1.3k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Google Search?

Skills that share tags, products or a category with Google Search: Brave Search (badlogic/pi-skills, 2.6k stars), Enterprise AI Scenario Map (MetaInFLow/Enterprise-ai-scenario-map-skill, 632 stars), Web Search (jjyaoao/HelloAgents, 3.2k stars) and Ddg Search (TheSyart/claude-agent-examples, 407 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Google Search?

team-attention (a GitHub organization) maintains it in team-attention/hoyeon, which has 173 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on May 21, 2026.

Source: team-attention/hoyeon on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Google Search

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Google Search (chromux)

Runtime Surface

Claude Code

Codex

When to Use

Prerequisites

Usage

Options

Examples

Output Format

Text mode (default)

JSON mode (--json)

Performance Notes

Error Handling

Fallback

Files

Compare with similar skills

Similar skills

More from team-attention/hoyeon

Related

Questions about Google Search

JSON mode (`--json`)