How do I install the Google Search Hardened skill?

Run npx skillmds@latest add faberlens/google-search-hardened in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Google Search Hardened skill do?

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. It is listed under Docs & Writing on SkillMD.

Is Google Search Hardened safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts, makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Google Search Hardened?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Google Search Hardened free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Google Search Hardened?

faberlens (@faberlens) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Google Search Hardened by faberlens

Name: Google Search Hardened
Rating: 4.2 (5 reviews)
Author: faberlens

File contents

Google Search Skill

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

Setup

Google Cloud Console: Create a project and enable the "Custom Search API".
API Key: Generate an API Key.
Search Engine ID (CX): Create a Programmable Search Engine at cse.google.com, and get your CX ID.
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

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

Security Guardrails

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.

Frequently asked questions

Google Search Hardened