agentleFS
claude-worldclaude-world/claude-agent/.claude/skills/deep-read/SKILL.md

deep-read

Skill5 starsChanged 8 months agoMITView on GitHub

Read and extract content from JS-rendered web pages using headless Chrome (Cloudflare Browser Rendering). Unlike /summarize, handles SPAs, paywalled previews, and complex sites. Use when a URL fails with regular fetch, or when user says "read this page", "what does this page say", "get the content from this URL".

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 4 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If cf-browser MCP is unavailable, fall back to WebFetch with a note: "Using basic fetch — for JS-heavy pages, set up cf-browser (see …

    line 35
  2. Very specific:

    Call browser_markdown(url=<URL>) — returns clean markdown of the rendered page

    line 43
  3. Very specific:

    Call browser_json(url=<URL>, prompt="Extract the main structured data") — returns JSON

    line 47
  4. Very specific:

    Call browser_links(url=<URL>) — returns all hyperlinks on the page

    line 51
  5. Very specific:

    Call browser_screenshot(url=<URL>) — returns PNG screenshot

    line 55
  6. Very specific:

    Always try browser_markdown first — it's the cleanest output

    line 69
  7. Distinctive:

    If the page requires login, note this and suggest the user provide cookies

    line 70
  8. Distinctive:

    Keep summaries under 200 words

    line 71
  9. Distinctive:

    Use the user's language for the summary

    line 72

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Deep Read

You are the deep page reading skill for Claude-Agent. Extract content from web pages that regular fetching can't handle.

Input

$ARGUMENTS — a URL and optional extraction mode (default: summary).

Steps

1. Check Availability

If cf-browser MCP is unavailable, fall back to WebFetch with a note: "Using basic fetch — for JS-heavy pages, set up cf-browser (see README)."

2. Extract Content

Based on extraction mode:

summary (default):

  • Call browser_markdown(url=<URL>) — returns clean markdown of the rendered page
  • Summarize: TL;DR (1-2 sentences) + Key Points (3-5 bullets)

data:

  • Call browser_json(url=<URL>, prompt="Extract the main structured data") — returns JSON
  • Present as a formatted table or structured output

links:

  • Call browser_links(url=<URL>) — returns all hyperlinks on the page
  • Group by type: navigation, content, external

screenshot:

  • Call browser_screenshot(url=<URL>) — returns PNG screenshot
  • Save to workspace/screenshot-[domain].png

3. Save if Valuable

Save extracted content to workspace/deepread-[domain-slug].md.

4. Present

Format the output concisely:

  • For summaries: TL;DR + Key Points (under 200 words)
  • For data: formatted table
  • For links: grouped list
  • For screenshots: file path

Rules

  • Always try browser_markdown first — it's the cleanest output
  • If the page requires login, note this and suggest the user provide cookies
  • Keep summaries under 200 words
  • Use the user's language for the summary

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.