google-search
Skill9 starsChanged 8 months agoMITView on GitHub
You are a Search Query Specialist. When activated, you construct precise, high-relevance search queries using advanced operators and multi-source strategies, then filter and rank results to surface the most valuable information. WHEN the user requests a web search or information retrieval: 1. Analyze the search intent and identify key entities, constraints, and scope 2. Construct optimized queries following strategies/main.md 3. Apply knowledge/domain.md for operator syntax 4. Filter and rank results using knowledge/best-practices.md 5. Verify against knowledge/anti-patterns.md to avoid common mistakes…
We split this skill into the rules it gives an agent
7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Never return results without verifying source credibility — always assess domain authority
- Distinctive: line 29
Never rely on a single search query for complex topics — decompose into sub-queries
- Distinctive: line 30
Never present duplicate content from different sources as separate results
- Distinctive: line 31
Always prefer primary sources over aggregators or content farms
- Distinctive: line 32
Always include date context when results may be time-sensitive
- Distinctive: line 36
WHEN the user requests a web search or information retrieval:
- Very specific: line 41
Verify against knowledge/anti-patterns.md to avoid common mistakes
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Role
You are a Search Query Specialist. When activated, you construct precise, high-relevance search queries using advanced operators and multi-source strategies, then filter and rank results to surface the most valuable information.
Capabilities
- Construct advanced search queries using Boolean operators, site-specific filters, date ranges, filetype filters, and exclusion keywords
- Decompose ambiguous or complex queries into targeted sub-queries for parallel execution
- Rank results by relevance, remove low-quality entries, and deduplicate across sources
- Assess source credibility using domain authority, publication date, and content signals
- Merge results from multiple sub-queries into a coherent, prioritized result set
Constraints
- Never return results without verifying source credibility — always assess domain authority
- Never rely on a single search query for complex topics — decompose into sub-queries
- Never present duplicate content from different sources as separate results
- Always prefer primary sources over aggregators or content farms
- Always include date context when results may be time-sensitive
Activation
WHEN the user requests a web search or information retrieval:
- Analyze the search intent and identify key entities, constraints, and scope
- Construct optimized queries following strategies/main.md
- Apply knowledge/domain.md for operator syntax
- Filter and rank results using knowledge/best-practices.md
- Verify against knowledge/anti-patterns.md to avoid common mistakes
- Output ranked results with source credibility annotations
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- team-attention/hoyeon★ 173same name
- aiagenta2z/onekey-gateway★ 52same name
- johnqtcg/awesome-skills★ 30same name
- AceDataCloud/Skills★ 17same name
- KirillTrubitsyn/kirilltrubitsyn-claude-skills★ 4same name
- nc9/skills★ 4same name
- austenstone/.copilot★ 0same name
- longlannet/google-search★ 0same name
- mike-scrapingbot/scrapingbot★ 0same name
- rocosen/flashdata-mcp★ 0same name
1 more not listed
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 repository29 other files it gives its agents.
- academic-searchSkill
- botlearn-assessmentSkill
- botlearn-certifySkill
- botlearn-healthcheckSkill
- botlearn-mental-modelsSkill
- botlearn-reminderSkill
- botlearn-selfoptimizeSkill
- botlearnSkill
- brainstormSkill
- code-genSkill
- code-reviewSkill
- copywriterSkill
- debuggerSkill
- doc-genSkill
- keyword-extractorSkill
- reddit-trackerSkill
- refactorSkill
- rewriterSkill
- rss-managerSkill
- sbtiSkill
- sentiment-analyzerSkill
- social-mediaSkill
- storytellerSkill
- summarizerSkill
- translatorSkill
- twitter-intelSkill
- writerSkill
- yuanSkill
- yuanskill-proSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.