ork-assess
Assess a code change, design, architecture, workflow, or competing options against explicit criteria and evidence. Use when a…
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
Claude Code
$ npx -y skills add yonatangross/orchestkit --skill web-research-workflow --agent claude-code
Codex
$ npx skills add yonatangross/orchestkit --skill web-research-workflow -a codex -y
Cursor
$ npx skills add yonatangross/orchestkit --skill web-research-workflow -a cursor -y
Gemini CLI
$ npx skills add yonatangross/orchestkit --skill web-research-workflow -a gemini-cli -y
GitHub Copilot
$ npx skills add yonatangross/orchestkit --skill web-research-workflow -a github-copilot -y
OpenCode
$ npx skills add yonatangross/orchestkit --skill web-research-workflow -a opencode -y
Windsurf
$ npx skills add yonatangross/orchestkit --skill web-research-workflow -a windsurf -y
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"
Unified approach for web content research that automatically selects the right tool for each situation.
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 patternWhen `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.
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.
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.
| 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 |
This skill is used by:
---
**Version:** 1.3.0 (March 2026)
The Complete AI Development Toolkit for Claude Code. 115 skills, 36 agents, 163 hooks. Install `ork` for stable (v10.x).
Assess a code change, design, architecture, workflow, or competing options against explicit criteria and evidence. Use when a…
Compare plausible implementation, architecture, product, or operational approaches before committing to one. Use when a request…
Map an unfamiliar codebase, feature, architecture, data flow, or operational path with file-backed evidence. Use when a request…
Render an answer inline as compact ASCII or box-drawing art with semantic status icons. Use for status, inventories, budgets,…
Make an approved, scoped change and prove the affected behavior. Use when a request asks to implement, build, add, or land a…
Review a pull request or branch for correctness, regressions, security, operational risk, and missing evidence. Use when a…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.