agentleFS
pollinationspollinations/search.elixpo/skills/research-web/SKILL.md

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

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
  1. Distinctive:

    Search efficiently and return compact evidence with source URLs.

    line 8
  2. Very specific:

    Use web_search with the narrowest useful query and depth.

    line 12
  3. Very specific:

    Run independent fetch_full_text calls concurrently.

    line 17
  4. Distinctive:

    Prefer primary and authoritative sources, then reputable reporting.

    line 18
  5. Very specific:

    Use deep_research only when the request requires a genuinely multi-part investigation.

    line 21
  6. Very specific:

    Use get_local_time for direct time questions and to anchor location-dependent relative dates.

    line 22
  7. Distinctive:

    Start fetching as search results arrive.

    line 26
  8. Very specific:

    Default to standard; use quick for lookups and thorough only when necessary.

    line 27
  9. Distinctive:

    Stop after sufficient high-quality evidence is collected.

    line 28
  10. Distinctive:

    Never use semantic memory or an older cached answer as evidence for a freshness-sensitive claim.

    line 29

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Research Web

Search efficiently and return compact evidence with source URLs.

Workflow

  1. Use web_search with the narrowest useful query and depth.
  2. For latest, current, today, or news requests, include the current date or recency in the query and treat search snippets only as leads.
  3. 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, call get_local_time for that place before or alongside search. Use its local date—not server UTC—as the range anchor.
  4. Interpret next N days as 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.
  5. Deduplicate and rank URLs before fetching. Reject app directories, ad pages, scraped profiles, undated pages, and off-topic results.
  6. Run independent fetch_full_text calls concurrently. A current-information answer requires fetched evidence from at least two credible sources when available.
  7. Prefer primary and authoritative sources, then reputable reporting. Capture publication dates for news.
  8. Record claims with supporting URLs; never invent missing evidence.
  9. 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.
  10. Use deep_research only when the request requires a genuinely multi-part investigation.
  11. Use get_local_time for 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; use quick for lookups and thorough only 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_bundle

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.