From ork
Automates web research and competitive monitoring via decision tree selecting WebFetch, Tavily, or agent-browser by site traits and API keys. Tracks pages, diffs snapshots, alerts changes for scraping, markdown extraction, docs capture.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ork:web-research-workflowhaikuThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Unified approach for web content research that automatically selects the right tool for each situation.
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 pattern
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("${CLAUDE_SKILL_DIR}/rules/tool-selection.md") for when-to-use-what tables, escalation heuristics, SPA detection patterns, and cost awareness.
Load details: Read("${CLAUDE_SKILL_DIR}/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("${CLAUDE_SKILL_DIR}/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("${CLAUDE_SKILL_DIR}/rules/monitoring-competitor.md") for snapshot capture, structured data extraction, and change classification.
Load details: Read("${CLAUDE_SKILL_DIR}/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:
web-research-analyst - Primary usermarket-intelligence - Competitor researchproduct-strategist - Deep competitive analysisbrowser-content-capture - Detailed browser patternsagent-browser - CLI referenceVersion: 1.3.0 (March 2026)
npx claudepluginhub yonatangross/orchestkit --plugin orkMonitors competitor pricing pages, feature tables, changelogs, and product changes using Firecrawl. Supports recurring competitive intelligence with pricing tier extraction and structured alerts.
Visits competitors' homepages, features, pricing, and blogs via Chrome MCP, generates structured Markdown competitive intelligence reports with summaries, snapshots, table, and actions, and saves to Google Drive for weekly pulses or deep dives.
Runs end-to-end competitor research by scraping public surfaces (site, blog, pricing, social, search rank, mentions, demand) via Firecrawl, HyperSEO, and Apify scrapers, diffs against prior runs, and synthesizes a brief. Use for battle cards, comparison pages, weekly digests, or answering 'what is [competitor] doing?'.