Web research
Skill Razaib-khan/ForgeWeave/src/forgeweave/templates/gemini/.gemini/skills/web-research
Behavioral execution framework for AI agents — define deterministic, portable skills & agents across OpenCode, Claude Code, Gemini CLI, and Qwen Code.
npx -y skills add Razaib-khan/ForgeWeave --skill web-researchAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Browser-driven or scraping-based skill for real-time internet extraction using Playwright and HTTP-based fetching
SKILL.md
2.6 KB, as published. Nobody here has run it
Web Research
Purpose
Fetch and extract content from live web pages using HTTP-based fetching (httpx + trafilatura) for standard pages and Playwright headless browser for JavaScript-rendered pages. Is the raw data acquisition layer for all research skills.
When to Use
- You need to fetch content from a specific URL
- A page requires JavaScript rendering to display its content
- You need to extract structured data from multiple pages
- Real-time information needs to be retrieved from the web
When Not to Use
- The user wants a summary of a topic they haven't specified URLs for
- The task is analyzing the local codebase
Inputs
| Input | Type | Required | Description |
|---|---|---|---|
url or urls | string/array | Yes | URL(s) to fetch |
mode | enum | No (default: auto) | auto, text, html, screenshot |
js_render | boolean | No (default: false) | Whether to use Playwright |
Expected Outputs
| Output | Description |
|---|---|
| Clean text content | Extracted main content from the page |
| Code examples | Extracted code blocks if mode=auto |
| Screenshot | Full-page screenshot if mode=screenshot |
Exact Workflow Steps
- Try HTTP fetch first using
webfetch - If response is incomplete (<2000 chars) or empty, fall back to Playwright MCP tools:
browser_navigate— navigate to the URLbrowser_snapshot— get structured accessibility tree with element refsbrowser_console_messages— check for JS errors that may indicate rendering issues
- Extract clean text content and code blocks
- If requested, take a screenshot via
browser_take_screenshot(Playwright MCP)
Required Checks
- Content was successfully extracted
- Fallback to Playwright was attempted if HTTP fetch failed
- Rate limiting was respected (1s between requests to same domain)
Failure Modes
| Failure Condition | Response |
|---|---|
| HTTP 404 | Try with Playwright (some SPAs return 404 for JS-rendered content) |
| All methods fail | Report URL as unreachable |
| Content too large | Truncate and report |
References
| Reference | Path |
|---|---|
| Web Scraper skill | ../web-scraper/SKILL.md |
| Async Crawler skill | ../async-crawler/SKILL.md |
| Playwright Architect skill | ../playwright-architect/SKILL.md |