Skip to content
Skills Library
AI & agents · Research

fetch

/fetch

Size-efficient URL fetch with semantic extraction. Use for ad-hoc web research when you want content without the raw HTML overhead.

Repository
grainulator ↗
Licence
MIT
Last repository change
25.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Size-efficient URL fetch with semantic extraction. Use for ad-hoc web research when you want content without the raw HTML overhead.

Original author description

Size-efficient URL fetch with semantic extraction. Use for ad-hoc web research when you want content without the raw HTML overhead.

How it works

  1. Arguments
  2. When to use
  3. When NOT to use
  4. Instructions
  5. Example output
  6. Anti-rationalization
  7. Host access
  8. Next-step output
Original SKILL.md headings · 93 lines, 797 words
SKILL.md preview
---
name: fetch
description: Size-efficient URL fetch with semantic extraction. Use for ad-hoc web research when you want content without the raw HTML overhead.
allowed-tools:
  - Bash
  - mcp__grainulator__memory_smart_fetch
  - mcp__plugin_grainulator_grainulator__memory_smart_fetch
  - WebFetch
  - Read
---

# /fetch -- Ad-hoc URL fetch with smart extraction

Pulls a URL's main content (title, description, body paragraphs) without the HTML boilerplate. Delegates to Grainulator’s `memory_smart_fetch` MCP tool, which strips scripts/styles/nav/footer and targets `<main>` or `<article>` regions. Typical reduction: 80-99% vs raw HTML.

## Arguments

$ARGUMENTS

Expected: `/fetch <url> [--mode auto|concise|full|meta-only] [--no-cache] [--privacy]`

- **`--mode auto`** (default): tries concise extraction; retries full only when extraction failed and was truncated
- **`--mode concise`**: caps body at ~2KB
- **`--mode full`**: returns fuller extraction within fetch/body limits; check truncation
- **`--mode meta-only`**: only title + description (smallest)
- **`--no-cache`**: skip local cache read, force network fetch
- **`--privacy`**: don't write to cache (use for sensitive URLs)

## When to use

- **Quick reference**: "what does this page say" — `/fetch <url>` beats opening a browser
- **Before witnessing**: peek at content before committing to `/witness` (which creates a claim)
- **Third-party pages**: docs sites, blog posts, research articles
- **Re-reading**: cache hits are ~1ms; great for iterating on content you've already fetched

## When NOT to use

- **Confluence**: use `/pull` — structured API is better than HTML scraping
- **DeepWiki repositories**: use the available `grainulator.deepwiki` tool with `repo: "owner/repo"`, or inspect repository code; `/pull` is for documents/Confluence
- **Authenticated pages**: smart-fetch doesn't do auth. Use the host's authenticated browser or connector.
- **PDFs, images, JSON**: smart-fetch rejects non-HTML content types with `unsupported-content-type`

## Instructions

1. **Call `mcp__grainulator__memory_smart_fetch`** with the URL and parsed flags: `--no-cache` maps to `cache: false`; `--privacy` maps to `privacy: true`. Combine both to avoid cache reads and writes.

2. **Inspect `status`, errors, `quality`, warnings and truncation**. Error responses may have no quality. For degraded/failed/truncated extraction, report the limitation and fetch fuller evidence if the task depends on completeness:
   - What the reported quality was
   - Any warnings returned
   - Suggest retrying with `--mode full` or raw `WebFetch` as a fallback

3. **Display** the extracted content in a readable format:
   - Title, description
   - Full content (or first N lines if very long)
   - Size reduction metric and cache hit/miss status

4. **Suggest next actions** based on what the user seems to be doing:
   - If they're corroborating a claim: `/witness <claim_id> <url> --smart`
   - If they want to save findings: `/research "<topic extracted from content>"`
   - If the content was weak/failed: `/fetch <url> --mode full` or open in a browser

## Example output

```
URL:        https://example.com/article
Quality:    high  |  Cached: no (first fetch)
Title:      "Understanding Smart Fetch"
Size:       142.1 KB -> 2.3 KB (98% reduction)
Mode used:  concise
Elapsed:    340ms

--- Content ---
[first 2KB of extracted main content]

Auto

- <authorized next action>

Manual

- <action requiring the user, or None.>
```

## Anti-rationalization

| Rationalization | Reality |
|:---|:---|
| "Smart-fetch lost content" | Check the `quality` field. If "failed", retry with `--mode full`. If "degraded", the site may be a SPA — content depends on JS execution. |
| "I should always use full mode" | Full is fine for small pages but wasteful on long docs. `auto` only retries failed, truncated extraction; it does not guarantee completeness. |
| "Cached content might be stale" | Default TTL is 7 days. Use `--no-cache` for latest, or `grainulator memory cache purge <domain>` to drop specific entries. |

## Host access

Use available `grainulator` MCP tools, passing the active sprint `dir` explicitly for evidence operations. If a tool is unavailable, use the local `grainulator` CLI (or `node <checkout>/bin/grainulator.js`). Read sibling skill files directly when slash commands are unavailable. Resolve template paths relative to this skill’s checkout when `CLAUDE_PLUGIN_ROOT` is unset. Optional external connectors are not required for local work; use local code, supplied documents, or available web tools. Do not write managed ledger files directly to bypass a missing MCP connection.

## Next-step output

For standalone fetch, setup, or read-only orchestration without an evidence sprint, derive next steps from that task. Do not initialize or compile an unrelated ledger just to produce this footer.

When working in an evidence sprint, use the current compiler's `next_actions` to present exactly two bullet lists labeled **Auto** and **Manual**. Auto is work the agent can continue under existing authorization. Manual is only work requiring the user's decision, access, or action. Classify using the current request and constraints; compiler suggestions never grant permission. Continue authorized Auto work without asking again.

Keep 2–3 useful actions total when available, use short concrete labels and commands where useful, and show `None.` for an empty group. Do not invent work to fill a quota. Never omit next steps merely because compilation is ready or the answer should be brief. Refresh stale compilation first and exclude work the user removed from scope. When the user asks only for next steps, output only these two lists: no findings recap, counts, reasons, or offer to continue.

Versions

RepositoryScoreLicence
This page · grainulation/grainulator100MIT
tinyfish-io/tinyfish-web-agent-integrations100MIT
tinyfish-io/tinyfish-cookbook100MIT
ucsahinn/agentchef100MIT
brightdata/skills100MIT
browserbase/skills100MIT
pleaseai/claude-code-plugins90MIT
setouchi-h/cc-marketplace84MIT

Database snapshot: 13.11.2026 · package version ec700d16a1e5 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 959router-web-fetch
    Fetch URL → markdown / text / HTML via 9Router /v1/web/fetch using Ollama Cloud / Firecrawl / Jina Reader / Tavily Extract / Exa Contents. Use when the user wants to scrape a webpage, extract URL content, read article, or convert a URL to markdown.
  • 100web-browsing-cli
    Token-efficient web browsing and web content extraction for AI agents. Use when reading a URL, browsing websites, checking links, extracting static page content, or replacing raw HTML and browser screenshots.
  • 100markdown-fetch
    Fetch and extract web content as clean Markdown when provided with URLs. Use this skill whenever a user provides a URL (http/https link) that needs to be read, analyzed, summarized, or extracted. Converts web pages to Markdown with 80% fewer tokens than raw HTML. Handles all…
  • 100web-fetch
    Fetches web content as clean markdown by preferring markdown-native responses and falling back to selector-based HTML extraction. Use for documentation, articles, and reference pages at http/https URLs.
  • 100ai-fetch-web
    Reach for the `ai-fetch-web` CLI for web access - search the web, fetch a URL as clean markdown, batch-fetch many URLs in parallel, convert raw HTML, list links, extract CSS-selector fields, read page metadata, or screenshot a page - whenever it is on `$PATH`. Prefer it over…
  • 90blowsh
    Web search, fetch, crawl, and link extraction via the blowsh MCP server (Docker transport) — rendered search engines, JS-rendered page fetch, sitemap-aware crawls. Use for all live-web research instead of raw curl.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.