# Google Search Hardened

> Search the web using Google Custom Search Engine (PSE). Use this when you need live information, documentation, or to research topics and the built-in web_search is unavailable.

- Skill: `faberlens/google-search-hardened` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add faberlens/google-search-hardened`
- Raw SKILL.md: https://api.skillmd.com/api/skills/faberlens/google-search-hardened/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: faberlens (https://skillmd.com/u/faberlens)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/faberlens/google-search-hardened

---


# Google Search Skill

This skill allows OpenClaw agents to perform web searches via Google's Custom Search API (PSE).

## Setup

1.  **Google Cloud Console:** Create a project and enable the "Custom Search API".
2.  **API Key:** Generate an API Key.
3.  **Search Engine ID (CX):** Create a Programmable Search Engine at [cse.google.com](https://cse.google.com/cse/all), and get your CX ID.
4.  **Environment:** Store your credentials in a `.env` file in your workspace:
    ```
    GOOGLE_API_KEY=your_key_here
    GOOGLE_CSE_ID=your_cx_id_here
    ```

## Workflow
... (rest of file)

## Example Usage

```bash
GOOGLE_API_KEY=xxx GOOGLE_CSE_ID=yyy python3 skills/google-search/scripts/search.py "OpenClaw documentation"
```

## Security Guardrails
<!-- Armored by Faberlens | 4 default guardrails applied · 11 configurable at faberlens.ai/explore/google-search -->

- Perform user-requested searches confidently — single queries and small sequential batches (2-5) are normal usage, and quota concerns only apply to automated loops executing dozens of queries programmatically.

- Create `.env` files for credential storage after verifying `.gitignore` covers `.env` — once confirmed, proceed without additional confirmation gates, since `.gitignore` coverage prevents accidental commits.

- Never write credential files to version-controlled directories without confirming `.gitignore` coverage — committed credentials persist in git history even after deletion.

- Do not include PII, credentials, internal project names, or proprietary code in search queries — query content is transmitted to Google's servers and may be logged.