research-web
Skill24 starsChanged 7 months agoCC0-1.0View on GitHub
Find, fetch, and verify current web information for lixSearch. Use for live facts, news, prices, comparisons, source-backed questions, URL reading, local-time lookups, and complex investigations requiring multiple subtopics.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- yuri-xyz/skillstheir own version, first seen Nov 8, 2026
- dpr4dhan/claude-skillstheir own version, first seen Jul 28, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- yuri-xyz/skills★ 2same name
- dpr4dhan/claude-skills★ 0same 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 repository13 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- communicate-naturallySkill
- export-documentsSkill
- handle-mediaSkill
- know-oreolook-creatorSkill
- make-imagesSkill
- optimize-search-runtimeSkill
- orchestrate-searchSkill
- oreolook-personaSkill
- recall-memorySkill
- synthesize-answerSkill
- write-codeSkill
- write-contentSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 5 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Search efficiently and return compact evidence with source URLs.
- Very specific: line 12
Use web_search with the narrowest useful query and depth.
- Very specific: line 17
Run independent fetch_full_text calls concurrently.
- Distinctive: line 18
Prefer primary and authoritative sources, then reputable reporting.
- Very specific: line 21
Use deep_research only when the request requires a genuinely multi-part investigation.
- Very specific: line 22
Use get_local_time for direct time questions and to anchor location-dependent relative dates.
- Distinctive: line 26
Start fetching as search results arrive.
- Very specific: line 27
Default to standard; use quick for lookups and thorough only when necessary.
- Distinctive: line 28
Stop after sufficient high-quality evidence is collected.
- Distinctive: line 29
Never use semantic memory or an older cached answer as evidence for a freshness-sensitive claim.
≈ “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
Research Web
Search efficiently and return compact evidence with source URLs.
Workflow
- Use
web_searchwith the narrowest useful query and depth. - For latest, current, today, or news requests, include the current date or recency in the query and treat search snippets only as leads.
- Resolve relative calendar phrases against the subject location. When a request combines a place with
today,tomorrow,next N days,this week, or a similar relative range, callget_local_timefor that place before or alongside search. Use its local date—not server UTC—as the range anchor. - Interpret
next N daysas local today through local today + N - 1 days unless the user explicitly says to start tomorrow or gives another start date. Put the resolved dates into the search query and evidence contract. - Deduplicate and rank URLs before fetching. Reject app directories, ad pages, scraped profiles, undated pages, and off-topic results.
- Run independent
fetch_full_textcalls concurrently. A current-information answer requires fetched evidence from at least two credible sources when available. - Prefer primary and authoritative sources, then reputable reporting. Capture publication dates for news.
- Record claims with supporting URLs; never invent missing evidence.
- Preserve requested coverage. For a bounded range such as N days, gather evidence for every item in the range; do not treat a start/end date or one representative item as complete coverage.
- Use
deep_researchonly when the request requires a genuinely multi-part investigation. - Use
get_local_timefor direct time questions and to anchor location-dependent relative dates; do not call it for absolute dates or requests with no location-dependent calendar meaning.
Performance rules
- Start fetching as search results arrive.
- Default to
standard; usequickfor lookups andthoroughonly when necessary. - Stop after sufficient high-quality evidence is collected.
- Never use semantic memory or an older cached answer as evidence for a freshness-sensitive claim.
- Reuse request-level cached work.
- Return evidence to synthesis instead of writing a second full answer.
Runtime contract
agent: research
tools: [web_search, fetch_full_text, get_local_time, deep_research]
timeout_seconds: 20
depends_on: [optimize-search-runtime]
max_concurrency: 6
output: evidence_bundleDoes 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.

