Individual skill
playbook-google-site-search
Checks whether a company's own website mentions a specific keyword, using one simple Google site: query per keyword through a SERP API, and turns the hit into a copy-ready line. Triggers on "does their site mention X", "site: search", "find companies whose website says X", "filter this list by a keyword on their site", "check if they talk about X", "google search enrichment". Outputs site_keyword_hit plus a one-clause personalization line with an evidence URL.
skills/playbooks/playbook-google-site-search/SKILL.md
Source commit 25c5d85fbb5dd3efec97b0ca457cbbc286547476
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 10, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 814
- Repository last updated
- Oct 5, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 22,728 bytesSKILL.mdcore · 22,728 bytesclay-table.mddoc · 6,853 bytesclay-workflow.mddoc · 8,861 bytes
Read excerpt
# Playbook: Google `site:` Keyword Filter
> All rules here are best practice, not law. Override any of them when the campaign calls for it; note the best practice once and move on.
**Use when:** a campaign needs to know whether each company's own website talks about a specific
thing — a certification, a technology, a service line, a location, a program name — and no structured
API sells that field.
**Do not use when:** you need to *find* companies you do not have yet; when the thing you want is a
**page** rather than a phrase (`playbook-pricing-page`, `playbook-case-study-page`); or when a real
filterable field already exists (funding stage, headcount, technology installed) — filter at the
source and skip this entirely.
**One-line output:** `site_keyword_line = "you hold SOC 2 Type II certification"`, rendering as