web-research
Skill2 starsChanged 4 months agoMITView on GitHub
Orchestrate web search and web extraction to produce evidence-based conclusions or reports with traceable source URLs. Use for web research, market or competitor scans, current-fact verification, technical investigation, policy research, multi-source comparison, dynamic-page research, table-backed analysis, or any answer that must cite web sources.
45 other projects use a version of this.
Adopted by
Most recently taken up by
- juninmd/skillstheir own version, first seen Nov 8, 2026
- thensls/nsls-builder-toolkittheir own version, first seen Nov 8, 2026
- memi-design/design-skillstheir own version, first seen Nov 8, 2026
- ai-assist-org/ai-assisttheir own version, first seen Nov 8, 2026
- WingedGuardian/GENesis-AGItheir own version, first seen Nov 8, 2026
- Bobagi/claude-skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use data-analysis, meeting-notes and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
shanggqmSkilldata-analysis
数据分析技能,提供结构化的数据查询、统计分析和报告生成工作流。当用户需要查询数据库、进行数据统计分析、生成分析报告时使用。按规范输出原始数据、计算结果、Markdown报告和HTML可视化报告。
Also in 5 projects that use this
claude-office-skillsSkillmeeting-notes
>
Also in 4 projects that use this
kongyo2Skillprompt-engineering
Comprehensive prompt engineering framework for designing, optimizing, and iterating LLM prompts. This skill should be used when users request prompt creation, optimization, or improvement for any LLM task, or when users need help translating vague requirements into effective prompts through collaborative dialogue and iterative refinement.
Also in 4 projects that use this
rogue-dev-studioSkillbrowser-automation
Canonical browser automation and web UI verification: Playwright, agent browser CLIs, and CDP-based tooling in one playbook.
Also in 3 projects that use this
JetBrainsSkillbrand-guidelines
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Also in 4 projects that use this
AnthropicSkillpdf
Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.
Also in 6 projects that use this
Other versions45 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 45
- langchain-ai/deepagents★ 31ksame name
- pollinations/pollinations★ 5.3ksame name
- langchain-ai/deepagentsjs★ 1.6ksame name
- alfredxw/denova★ 990same name
- icey1287/SuperMew★ 884same name
- cohen-liel/hivemind★ 108same name
- grandamenium/cortextos★ 106same name
- WingedGuardian/GENesis-AGI★ 100same name
- jezweb/vite-flare-starter★ 49same name
- dewil/ai-toolkit★ 9same name
35 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 repository42 other files it gives its agents.
- architect-boundary-reviewSkill
- architect-decision-recordSkill
- architect-system-designSkill
- browser-playwright-checkSkill
- browser-useSkill
- code-search-navigationSkill
- controlled-emergence-observerSkill
- dev-code-locationSkill
- dev-small-scope-patchSkill
- dev-test-and-explainSkill
- eval-observation-writingSkill
- eval-promotion-adviceSkill
- eval-risk-gap-analysisSkill
- ops-log-diagnosisSkill
- ops-runtime-healthSkill
- ops-stuck-workflowSkill
- pm-acceptance-criteriaSkill
- pm-architecture-reviewSkill
- pm-delivery-planSkill
- pm-evolve-skillsSkill
- pm-long-horizon-planningSkill
- pm-priority-triageSkill
- pm-product-design-briefSkill
- pm-product-requirementsSkill
- pm-scope-controlSkill
- pm-solve-problemsSkill
- pm-tech-scopeSkill
- qa-regression-checkSkill
- qa-reproduce-issueSkill
- qa-verify-fixSkill
- run-local-command-checkSkill
- test-selectionSkill
- tm-delivery-governanceSkill
- tm-review-routingSkill
- tm-risk-dependencySkill
- ui-information-architectureSkill
- ui-requirementsSkill
- ui-usability-acceptanceSkill
- ui-visual-consistencySkill
- web-extractSkill
- web-searchSkill
- windows-useSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 9 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 38 edited versions we read keep these.
9
Distinctive
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
- Very specific: line 8
Run an end-to-end research workflow by combining web-search and web-extract.
- Very specific: line 13
Use the web-search procedure to construct queries and select authoritative, diverse sources.
- Very specific: line 14
Use the web-extract procedure on the selected URLs:
- Distinctive: line 16
Use Playwright only for dynamic content when needed.
- Distinctive: line 24
Write the requested answer or report with findings, evidence, limitations, and source list.
- Distinctive: line 25
When operating inside an agent task, use the available report tool and include source URLs in the report body or structured evidence.
- Very specific: line 26
Do not generate a site-specific .mjs probe for normal work.
- Distinctive: line 27
When the research hierarchy is known, execute it in dependency order.
- Distinctive: line 57
Every material factual claim must be supported by an extracted source.
- Distinctive: line 58
Use exact dates when freshness affects the conclusion.
- Distinctive: line 59
Prefer primary and official sources.
- Distinctive: line 61
Do not cite a search result that was never opened and checked.
- Distinctive: line 62
Do not cite a URL that does not support the associated claim.
- Very specific: line 70
Every evidence item retained source_url.
“Common” is measured: kept by at least 6 in 10 of the 38 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
Web Research
Run an end-to-end research workflow by combining web-search and web-extract. Produce conclusions that remain traceable to the underlying webpages.
Workflow
- Define the research question, decision to support, scope, freshness requirement, and expected report shape.
- Use the
web-searchprocedure to construct queries and select authoritative, diverse sources. - Use the
web-extractprocedure on the selected URLs:- Open webpages.
- Use Playwright only for dynamic content when needed.
- Extract relevant正文.
- Extract relevant tables with headers and units.
- Preserve
source_urlon every evidence item. - Set explicit extraction quality gates; reject weak pages instead of treating navigation text as evidence.
- Compare sources. Resolve differences using source authority, dates, definitions, methods, and directness of evidence.
- Separate verified facts, reasonable inferences, conflicting evidence, and unknowns.
- Form conclusions only from extracted evidence. Attach one or more source URLs to each material claim.
- Write the requested answer or report with findings, evidence, limitations, and source list.
- When operating inside an agent task, use the available report tool and include source URLs in the report body or structured evidence.
- Do not generate a site-specific
.mjsprobe for normal work; configure the shared web tools instead. - When the research hierarchy is known, execute it in dependency order. Complete the inventory layer before sampling descendants, and continue automatically while each next step is read-only and in scope.
Research Report Contract
## Research Question
<question and scope>
## Method
<queries, source-selection rule, retrieval date, dynamic-page use>
## Findings
1. <finding> [source](source_url)
2. <finding> [source](source_url)
## Table Evidence
<normalized table or comparison, with source_url for each source/table>
## Conclusion
<answer, recommendation, or decision support>
## Uncertainty And Conflicts
<unknowns, stale data, conflicting definitions, inaccessible sources>
## Sources
- <title> - <source_url>Source Discipline
- Every material factual claim must be supported by an extracted source.
- Use exact dates when freshness affects the conclusion.
- Prefer primary and official sources; use secondary sources for context or comparison.
- Clearly label inference rather than presenting it as a sourced fact.
- Do not cite a search result that was never opened and checked.
- Do not cite a URL that does not support the associated claim.
Completion Criteria
- Searches were purposeful and recorded.
- Selected pages were opened and inspected.
- Dynamic content used Playwright only where necessary.
- Relevant正文 and tables were extracted.
- Every evidence item retained
source_url. - Conclusions distinguish fact, inference, conflict, and uncertainty.
- The final answer or report includes usable source links.
- The workflow did not stop at a proposed method when the next research action was already authorized and executable.
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
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.

