Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Research checklist and source-quality guidance for the archer e2e fixture.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-18 | ✗→✓ | ▲ Improved | -29% | 0% |
| case-05 | ✓→✗ | ▼ Worse | -38% | 0% |
| case-08 | ✓→✗ | ▼ Worse | -40% | 0% |
| case-10 | ✓→✗ | ▼ Worse | -61% | 0% |
| case-14 | ✓→✗ | ▼ Worse | 47% | 0% |
Use this for any question that needs current, verifiable information from the web. The deliverable is a synthesized answer where every load-bearing claim is backed by a source you actually read.
search_web_pages(query, [site], [published_after], [published_before], [mode])— discover candidate sources. Write the query as a natural-language description of the ideal page, not keywords. Use mode: pro (default).
fetch_page_content(url, [max_chars]) — read the full page (markdown). Asearch snippet is NEVER sufficient evidence — fetch before you cite.
cover it. For contested or high-stakes questions, plan at least two independent angles.
search_web_pages per sub-query. Prefer primary sources;use published_after for anything time-sensitive.
fetch_page_content on the 2-3 most promising results persub-query. Quote/cite only what you read, not what a snippet implied.
sources (independent = different owners, not mirrors of one another). When sources disagree, surface the disagreement rather than picking silently.
inline citation to the URL you fetched. Separate "well-supported" from "uncertain / single-source".
Sources list of the URLs you actually fetched.an honest "the evidence is mixed" beats false confidence.
Other measured skills in the registry, with their headline benchmark lift.