メニュー
Load when fetching content from URLs, especially social media or JavaScript-heavy sites. Explains when web_fetch works vs when browser automation is required.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
REQUIRED when the user asks about scheduling, reminders, cron jobs, timers, background jobs, diagnostics, troubleshooting, MCP tools, daemon health, identity updates, or Netclaw capabilities and self-maintenance.
How to create, find, and work with project workspaces. Load when the user references a project, asks to organize work, or you need a sustained workspace.
How to create and troubleshoot file-defined subagents in ~/.netclaw/agents. Load when the user asks to add, edit, or debug subagent definitions, or when a skill routes via metadata.subagent.
Use when asked to verify logical access to a managed server-feed skill and its reference resource.
How to create, edit, and manage Netclaw skills. Read this when you need to synthesize a new skill from a session, understand the skill file format, or use the skill_manage tool.
Required drafting and review process for customer-facing business and sales email.
| name | web-content-retrieval |
| description | Load when fetching content from URLs, especially social media or JavaScript-heavy sites. Explains when web_fetch works vs when browser automation is required. |
| keywords | ["url","fetch","content","link","twitter","x.com","tweet","social media","instagram","linkedin","facebook","javascript","blocked","scrape"] |
| metadata | {"author":"netclaw","version":"1.0.0"} |
This skill helps you choose the right tool for fetching web content.
| Site type | Tool | Why |
|---|---|---|
| Static HTML (blogs, docs, news articles) | web_fetch | Fast, simple, works |
| Social media (Twitter/X, Instagram, LinkedIn) | Browser automation | JS-rendered, auth walls |
| SPAs, dynamic dashboards | Browser automation | Content loaded via JS |
| APIs, JSON endpoints | web_fetch | Direct data access |
web_fetch sends a simple HTTP request and returns the response. It works for:
web_fetch will return empty, partial, or error content when:
Common sites that require browser automation:
x.com, twitter.com)If a browser MCP server is available (e.g., Playwright), use it for JS-heavy sites:
# First, check if browser tools are available
search_tools(query: "browser navigate")
# If available, use browser navigation
browser_navigate(url: "https://x.com/username/status/123")
Browser automation:
If no browser MCP is configured, tell the user honestly:
"This URL appears to be from a JavaScript-heavy site (Twitter/X) that typically requires browser automation to fetch content. I don't have a browser tool available in this session. You could:
- Share the content directly (copy/paste the tweet text)
- Enable a browser MCP server like Playwright
- I can try web_fetch, but it will likely return incomplete content"
Do not silently fail. If you attempt web_fetch on a known JS-heavy site and
get empty/blocked content, explain why and suggest alternatives.
search_tools(query: "browser")web_fetch first, but be ready to explain if it failssearch-citationnetclaw-operations → Tool Discovery