web-fetch

Name: web-fetch
Availability: InStock
Author: Corca

Route and classify public-web fetches through an internal seam.

9|3|Updated Apr 9, 2026

Search Tags:#routing #provenance #classification #fallback #web-fetch #public-web

Ready to run

npx skills add https://github.com/corca-ai/charness --skill web-fetch-corca-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: web-fetch
Source: https://github.com/corca-ai/charness/tree/main/plugins/charness/support/web-fetch
Command: npx skills add https://github.com/corca-ai/charness --skill web-fetch-corca-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Public-web fetches often require domain-aware routing and response classification to avoid leaking site-specific tactics into public workflows. This internal seam centralizes retrieval decisions and keeps public skills clean.

Core Features & Use Cases

Internal routing and classification for public-web fetches.
Supports escalation to domain-specific APIs or transforms when direct fetch is weak or blocked.
Provides provenance-friendly artifacts for retriever pipelines and audits.

Quick Start

Ask the agent to route a URL via the web-fetch seam and classify the response.

Frequently Asked Questions about web-fetch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I route public-web fetches without leaking site-specific tactics into public workflows?▼

Route public-web fetches through a dedicated internal seam to centralize retrieval decisions. This classifies responses and applies domain-specific APIs or URL transforms when direct fetches are weak or blocked, keeping public skills clean.

What is provenance in web scraping and how do I preserve fetch routing history?▼

Provenance in web scraping tracks the origin and retrieval method of fetched data. Enforce durable artifacts like source URL, route, retrieval method, and classification to preserve provenance and freshness for retriever pipelines and audits.

How do I handle blocked or weak direct fetches for specific domains?▼

Handle blocked or weak direct fetches by escalating to domain-specific APIs or URL transforms. The routing layer automatically detects retrieval failures and applies the necessary domain-aware fallbacks to ensure successful data retrieval.

Does this web-fetch routing approach support response classification for retriever pipelines?▼

Yes, the web-fetch routing approach supports response classification for retriever pipelines. It routes and classifies public-web fetches, enforcing durable artifacts that preserve source URL, route, and retrieval method for downstream processing.

When should I use an internal routing seam for web fetching instead of direct requests?▼

Use an internal routing seam for web fetching when public skills require domain-aware routing and response classification. It prevents leaking site-specific tactics into public workflows and manages escalation to domain-specific APIs when direct fetches fail.

Why do my public skills keep breaking when target websites change their structure?▼

Public skills break when site-specific tactics are embedded directly in workflows. An internal routing seam centralizes retrieval decisions and domain-specific API escalations, isolating structural changes from public skill logic to maintain stability.