web-research-workflow — Claude Code skill: research, install
The web-research-workflow skill picks a web access method, extracts page content, and tracks competitor changes. Use it for research, documentation capture, and site monitoring.
MIT 228 installs ★ 305 updated 2026-10-24
npx skills add yonatangross/orchestkit --skill web-research-workflow -a claude-codeWhat web-research-workflow does
web-research-workflow starts with WebFetch and moves to Tavily when the result is empty or partial, provided TAVILY_API_KEY is available. Pages that need JavaScript, authentication, or multi-page navigation fall back to agent-browser. The workflow can return raw Markdown and capture documentation content.
Its supporting rules cover tool selection, browser flows, competitor snapshots, diff detection, and change severity. Price or major feature changes can trigger immediate alerts, while copy edits and minor styling changes receive lighter treatment. Claude Code requires version 2.1.277 or later, along with network access.
What it helps with
- research a page with the right access method
- extract raw Markdown from a website
- capture documentation across several pages
- track competitor pricing and feature changes
- classify changes found in page snapshots
Example prompts for the agent
- Research this product page and return the content as Markdown.
- Compare the competitor’s current pages with saved snapshots and list the changes.
- Collect the documentation from these pages, using a browser when the first fetch fails.
How to install web-research-workflow
1Skills CLI (Vercel)
npx skills add yonatangross/orchestkit --skill web-research-workflow -a claude-code2Manually: put the files in place
~/.claude/skills/web-research-workflow/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/web-research-workflow/
1Skills CLI (Vercel)
npx skills add yonatangross/orchestkit --skill web-research-workflow -a codex2Manually: put the files in place
.agents/skills/web-research-workflow/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add yonatangross/orchestkit --skill web-research-workflow -a cursor2Manually: put the files in place
.cursor/skills/web-research-workflow/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install yonatangross/orchestkit src/skills/web-research-workflow2Manually: put the files in place
.github/skills/web-research-workflow/SKILL.md1Skills CLI (Vercel)
npx skills add yonatangross/orchestkit --skill web-research-workflow -a gemini-cli2Platform CLI
gemini skills install https://github.com/yonatangross/orchestkit --path src/skills/web-research-workflowManually: put the files in place
.devin/skills/web-research-workflow/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add yonatangross/orchestkit --skill web-research-workflow -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about web-research-workflow
How do I install web-research-workflow in Claude Code?
Run npx skills add yonatangross/orchestkit --skill web-research-workflow -a claude-code, then check ~/.claude/skills/web-research-workflow/SKILL.md.
What does web-research-workflow do?
The skill chooses between WebFetch, Tavily, and agent-browser for web research. It can also capture site snapshots, compare revisions, and classify changes for monitoring.
Do I need TAVILY_API_KEY to use it?
No. Without TAVILY_API_KEY, the workflow uses WebFetch and then agent-browser; with the key, Tavily adds search, extraction, crawling, and research steps.
Source text
SKILL.md · MIT
---
name: web-research-workflow
license: MIT
compatibility: "Claude Code 2.1.277+. Requires network access."
description: Unified decision tree for web research and competitive monitoring. Auto-selects WebFetch, Tavily, or agent-browser based on target site characteristics and available API keys. Includes competitor page tracking, snapshot diffing, and change alerting. Use when researching web content, scraping, extracting raw markdown, capturing documentation, or monitoring competitor changes.
context: inherit
user-invocable: false
disable-model-invocation: true
allowed-tools: "Bash Read Write WebFetch"
effort: low
model: haiku
metadata:
category: mcp-enhancement
version: "1.3.0"
author: "OrchestKit"
complexity: "low"
tags: "research, browser, webfetch, tavily, automation, scraping, content-extraction, competitive-intelligence, monitoring"
---
# Web Research Workflow
Unified approach for web content research that automatically selects the right tool for each situation.
## Quick Decision Tree
```
URL to research
│
▼
┌─────────────────┐
│ 1. Try WebFetch │ ← Fast, free, no overhead
│ (always try) │
└─────────────────┘
│
Content OK? ──Yes──► Parse and return
│
No (empty/partial/<500 chars)
│
▼
┌───────────────────────┐
│ 2. TAVILY_API_KEY set?│
└───────────────────────┘
│ │
Yes No ──► Skip to step 3
│
▼
┌───────────────────────────┐
│ Tavily search/extract/ │ ← Raw markdown, batch URLs
│ crawl/research │
└───────────────────────────┘
│
Content OK? ──Yes──► Parse and return
│
No (JS-rendered/auth-required)
│
▼
┌─────────────────────┐
│ 3. Use agent-browser │ ← Full browser, last resort
└─────────────────────┘
│
├─ SPA (react/vue/angular) ──► wait --load networkidle
├─ Login required ──► auth flow + state save
├─ Dynamic content ──► wait --text "Expected"
└─ Multi-page ──► crawl pattern
```
## Tavily Enhanced Research
When `TAVILY_API_KEY` is set, Tavily provides a powerful middle tier between WebFetch and agent-browser. It returns raw markdown content, supports batch URL extraction, and offers semantic search with relevance scoring. If `TAVILY_API_KEY` is not set, the 3-tier tree collapses to 2-tier (WebFetch → agent-browser) automatically.
Load details: `Read("rules/tool-selection.md")` for when-to-use-what tables, escalation heuristics, SPA detection patterns, and cost awareness.
Load details: `Read("references/tavily-api.md")` for Search, Extract, Map, Crawl, and Research endpoint examples and options.
## Browser Patterns
For content requiring JavaScript rendering, authentication, or multi-page crawling, fall back to agent-browser.
Load details: `Read("rules/browser-patterns.md")` for auto-fallback, authentication flow, multi-page research patterns, best practices, and troubleshooting.
## Competitive Monitoring
Track competitor websites for changes in pricing, features, positioning, and content.
Load details: `Read("rules/monitoring-competitor.md")` for snapshot capture, structured data extraction, and change classification.
Load details: `Read("rules/monitoring-change-detection.md")` for diff detection, structured comparison, Tavily site discovery, and CI automation.
### Change Classification
| Severity | Examples | Action |
|----------|----------|--------|
| Critical | Price increase/decrease, major feature change | Immediate alert |
| High | New feature added, feature removed | Review required |
| Medium | Copy changes, positioning shift | Note for analysis |
| Low | Typos, minor styling | Log only |
## Integration with Agents
This skill is used by:
- `web-research-analyst` - Primary user
- `market-intelligence` - Competitor research
- `product-strategist` - Deep competitive analysis
## Related Skills
- `browser-content-capture` - Detailed browser patterns
- `agent-browser` - CLI reference
---
**Version:** 1.3.0 (March 2026)
© OrchestKit · MIT · yonatangross/orchestkit