websearch-research

Runs two-pass web research with URL and retrieval date cited on every claim.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/JYeswak/grok_bot_playground --skill websearch-research-jyeswak
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: websearch-research
Source: https://github.com/JYeswak/grok_bot_playground/tree/main/plugin/skills/websearch-research
Command: npx skills add https://github.com/JYeswak/grok_bot_playground --skill websearch-research-jyeswak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Uncited research answers cannot be verified: a claim without a URL and a date cannot be re-checked, and undated links go stale silently. This Skill enforces a research discipline where every factual statement traces to a named source read on a named date. ## Core Features & Use Cases - Two-pass verification: Runs two independent research passes with different queries, then cross-checks claims — confirmed items become findings, single-pass items are labeled single-sourced, and contradictions are surfaced rather than averaged away. - Mandatory citation discipline: Every claim carries a source URL and retrieval date; anything unsourced is labeled unsourced opinion, never blended into findings. - Provenance honesty: Community posts are labeled community-claim and treated as leads, never as primary-source evidence; paywalled or credential-gated sources are recorded as unreachable. - Use Case: A teammate asks you to verify a vendor's changelog claim. You run two passes, confirm it against the vendor's own page with today's date, flag a contradicting community post, and deliver a dated markdown brief ending with the decision the finding supports. ## Quick Start Research whether the vendor's API supports batch endpoints and give me a cited brief with a URL and retrieval date on every claim.

Frequently Asked Questions about websearch-research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a claim against primary sources?▼

State the claim narrowly, then run two research passes with different queries that read the vendor's own pages or official documentation. Confirm the claim only when both passes agree, and attach the source URL and retrieval date to it.

How to do web research with citations for every claim?▼

Record queries and sources per pass, and attach a URL plus retrieval date to each factual statement. Claims that cannot be sourced are labeled unsourced opinion rather than presented as findings.

Can community posts be used as evidence in research?▼

Community posts are treated as leads, never as evidence. Anything actionable from a forum or social post must be verified against the vendor's own page before it counts as a finding, and it stays labeled community-claim until then.

What happens when sources contradict each other?▼

Contradictions between passes are reported explicitly as contradictions, never averaged away or resolved by picking the convenient source. The brief notes what evidence would settle the disagreement.

What are the limitations of read-only web research?▼

Paywalled or credential-gated sources are recorded as unreachable rather than bypassed, and no access is improvised. Research is read-only over public pages or sources the operator explicitly provides.