serper-search
Skill1 starsChanged 9 months agoMITView on GitHub
Google search via Serper API. Fallback for when Brave Search misses niche technical docs, error messages, or obscure library documentation. Uses Google's index — the most comprehensive for technical queries.
- Reads credentials
- Installs packages
1 other project uses a version of this.
Adopted by
Most recently taken up by
- agentscope-ai/ReMetheir own version, first seen Aug 20, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- agentscope-ai/ReMe★ 3.8ksame name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- brave-searchSkill
- hn-distillSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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
- Distinctive: line 8
When to use instead of brave-search: When Brave returns poor/no results for niche technical queries — obscure library docs, specific error …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Serper Search (Google Fallback)
When to use instead of brave-search: When Brave returns poor/no results for niche technical queries — obscure library docs, specific error messages, framework-specific APIs. Google's index is larger and has better coverage of Stack Overflow, GitHub issues, and documentation sites.
When to use brave-search instead: For general research, LLM-optimized content (llm-context.js), SEO filtering (Goggles), and most searches. Brave is faster (669ms vs ~2.9s) and returns pre-extracted content.
Search
{baseDir}/search.js "query" # 5 results
{baseDir}/search.js "query" -n 10 # More results
{baseDir}/search.js "query" --content # Include page content as markdown
{baseDir}/search.js "query" --site docs.python.org # Restrict to domain
{baseDir}/search.js "query" --period w # Last week only
{baseDir}/search.js "query" --site stackoverflow.com --content # SO answers with contentOptions
-n <num>— Number of results (default: 5, max: 100)--content— Fetch and extract full page content as markdown (uses Readability)--period <time>— Time filter:d(day),w(week),m(month),y(year)--site <domain>— Restrict results to a specific domain--gl <country>— Country code (default: us)--hl <lang>— Language code (default: en)
Typical Fallback Patterns
# Brave missed it — try Google's index
{baseDir}/search.js "go-quartz library cron scheduling example" --content
# Error message lookup (Google excels at these)
{baseDir}/search.js "error: cannot find module '@prisma/client' after upgrade" -n 3 --content
# Specific library docs
{baseDir}/search.js "pgvector cosine similarity operator <=>" --site stackoverflow.com --content
# Recent content
{baseDir}/search.js "React 19 useOptimistic hook" --period m --contentSetup
Requires SERPER_API_KEY env var. Get one at https://serper.dev — free 2,500 queries, no credit card needed.
export SERPER_API_KEY="your-key" # Add to ~/.zprofile
cd {baseDir} && npm install # Run onceCost
- $1/1K queries (entry tier, $50 for 50K credits)
- $0.30/1K at 500K+ volume
- Free tier: 2,500 queries (one-time, no CC)
- 5× cheaper than Brave ($5/1K)
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
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.

