/wigolo-extract
Local-first structured extraction from any webpage — tables, definition lists, key-value pairs, JSON-LD, microdata, chart hints (SVG titles / aria-labels / figcaptions), brand assets, and metadata. Use when the user wants structured data, pricing tables, feature comparisons, or
$ npx -y skills add KnockOutEZ/wigolo --skill wigolo-extract --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/wigolo-extract
Context preview
The summary Claude sees to decide when to auto-load this skill.
Local-first structured extraction from any webpage — tables, definition lists, key-value pairs, JSON-LD, microdata, chart hints (SVG titles / aria-labels / figcaptions), brand assets, and metadata. Use when the user wants structured data, pricing tables, feature comparisons, or
SKILL.md
wigolo-extract.SKILL.mdname: wigolo-extract
description: |
Local-first structured extraction from any webpage — tables, definition lists, key-value pairs, JSON-LD, microdata, chart hints (SVG titles / aria-labels / figcaptions), brand assets, and metadata. Use when the user wants structured data, pricing tables, feature comparisons, or says "extract the table", "get structured data", "pull the pricing", "extract as JSON". For autonomous navigation across many pages, use wigolo's `agent` tool instead.
license: AGPL-3.0-only
metadata:
author: KnockOutEZ
version: 0.1.43-beta.2
homepage: https://github.com/KnockOutEZ/wigolo
repository: https://github.com/KnockOutEZ/wigolo
wigolo extract
Structured data extraction beyond simple markdown.
Quick Reference
// Full structured extraction (ALWAYS prefer this)
{ "url": "https://bun.sh", "mode": "structured" }
// JSON Schema extraction — heuristic field matching
{ "url": "https://example.com/pricing", "mode": "schema", "schema": { "type": "object", "properties": { "name": { "type": "string" }, "price": { "type": "string" }, "sku": { "type": "string" } } } }
// CSS selector extraction
{ "url": "https://example.com", "mode": "selector", "css_selector": ".product-card", "multiple": true }
// Metadata only (matches fetch metadata shape)
{ "url": "https://example.com", "mode": "metadata" }
// From raw HTML
{ "html": "<table>...</table>", "mode": "tables" }Modes
| Mode | What it extracts | When to use | |------|-----------------|-------------| | `structured` | Tables + definition lists + JSON-LD + chart hints + key-value pairs | **Default choice — use this** | | `tables` | HTML tables only | When you specifically need only tables | | `schema` | Fields matching a JSON Schema (LLM-sourced fields verified against source; hallucinated values returned as null) | When you know the exact fields you want | | `brand` | Logo, favicon, colors, fonts, social_links (with provenance; favicons never promote to logo_url) | Brand kit / identity extraction | | `metadata` | OpenGraph, meta tags, JSON-LD, canonical_url, og_image | For page metadata only | | `selector` | CSS selector matches | When you know the exact CSS selector |
**Always use `mode: "structured"` instead of `mode: "tables"`.** Structured captures everything tables does, plus definitions, key-value pairs, JSON-LD, and chart descriptions.
Chart Hints
When a page has visual charts (SVG, Canvas), `chart_hints` contains text descriptions extracted from aria-labels, SVG `<title>`, and figcaptions. Use these to describe visual data even when the underlying data is JavaScript-rendered.
Schema Mode
`mode: "schema"` matches your JSON Schema field names against page content via CSS classes, ARIA labels, microdata, and JSON-LD. When a language model is available it sources fields and **verifies each value against the source — hallucinated values are returned as `null`** rather than guessed. Pass `{ properties: { field: { type: "string" } } }`.
Named Schemas
Instead of hand-writing a schema, pass `named_schema` for a strict, heuristic-only extraction (no LLM required) into a known shape:
{ "url": "https://blog.example.com/post", "named_schema": "Article" }Available: `Article`, `Recipe`, `Product`, `CodeSnippet`, `Paper`, `EventListing`. Mutually exclusive with `schema`.
Brand Mode
`mode: "brand"` pulls a page's identity assets — `logo`, `favicon`, `colors`, `fonts`, and `social_links` — each with provenance. Favicons never get promoted to `logo_url`.
Token Budget
`max_tokens_out` (cl100k-base) caps extracted output; trailing table rows or heavy keys are dropped first to fit.
Anti-Patterns
- DON'T use `mode: "tables"` — use `mode: "structured"` instead.
- DON'T pass a schema without `properties` key — handler rejects it.
- DON'T extract for a whole page when you need markdown — use `fetch` instead.
When NOT to use wigolo-extract
- **Multi-page autonomous structured extraction** — use wigolo's `agent` tool instead.
- **Page requires login / click / form-fill before the data appears** — handle authentication with `use_auth` or interact with the page before extracting.
See Also
- [wigolo-fetch](../wigolo-fetch/SKILL.md) — for markdown content
- [wigolo-agent](../wigolo-agent/SKILL.md) — for multi-page schema-driven gathering
Read more
name: wigolo-extract description: | Local-first structured extraction from any webpage — tables, definition lists, key-value pairs, JSON-LD, microdata, chart hints (SVG titles / aria-labels / figcaptions), brand assets, and metadata. Use when the user wants structured data, pricing tables, feature comparisons, or says "extract the table", "get structured data", "pull the pricing", "extract as JSON". For autonomous navigation across many pages, use wigolo's `agent` tool instead. license: AGPL-3.0-only metadata: author: KnockOutEZ version: 0.1.43-beta.2 homepage: https://github.com/KnockOutEZ/wigolo repository: https://github.com/KnockOutEZ/wigolo
wigolo extract
Structured data extraction beyond simple markdown.
Quick Reference
// Full structured extraction (ALWAYS prefer this)
{ "url": "https://bun.sh", "mode": "structured" }
// JSON Schema extraction — heuristic field matching
{ "url": "https://example.com/pricing", "mode": "schema", "schema": { "type": "object", "properties": { "name": { "type": "string" }, "price": { "type": "string" }, "sku": { "type": "string" } } } }
// CSS selector extraction
{ "url": "https://example.com", "mode": "selector", "css_selector": ".product-card", "multiple": true }
// Metadata only (matches fetch metadata shape)
{ "url": "https://example.com", "mode": "metadata" }
// From raw HTML
{ "html": "<table>...</table>", "mode": "tables" }Modes
| Mode | What it extracts | When to use | |------|-----------------|-------------| | `structured` | Tables + definition lists + JSON-LD + chart hints + key-value pairs | **Default choice — use this** | | `tables` | HTML tables only | When you specifically need only tables | | `schema` | Fields matching a JSON Schema (LLM-sourced fields verified against source; hallucinated values returned as null) | When you know the exact fields you want | | `brand` | Logo, favicon, colors, fonts, social_links (with provenance; favicons never promote to logo_url) | Brand kit / identity extraction | | `metadata` | OpenGraph, meta tags, JSON-LD, canonical_url, og_image | For page metadata only | | `selector` | CSS selector matches | When you know the exact CSS selector |
**Always use `mode: "structured"` instead of `mode: "tables"`.** Structured captures everything tables does, plus definitions, key-value pairs, JSON-LD, and chart descriptions.
Chart Hints
When a page has visual charts (SVG, Canvas), `chart_hints` contains text descriptions extracted from aria-labels, SVG `<title>`, and figcaptions. Use these to describe visual data even when the underlying data is JavaScript-rendered.
Schema Mode
`mode: "schema"` matches your JSON Schema field names against page content via CSS classes, ARIA labels, microdata, and JSON-LD. When a language model is available it sources fields and **verifies each value against the source — hallucinated values are returned as `null`** rather than guessed. Pass `{ properties: { field: { type: "string" } } }`.
Named Schemas
Instead of hand-writing a schema, pass `named_schema` for a strict, heuristic-only extraction (no LLM required) into a known shape:
{ "url": "https://blog.example.com/post", "named_schema": "Article" }Available: `Article`, `Recipe`, `Product`, `CodeSnippet`, `Paper`, `EventListing`. Mutually exclusive with `schema`.
Brand Mode
`mode: "brand"` pulls a page's identity assets — `logo`, `favicon`, `colors`, `fonts`, and `social_links` — each with provenance. Favicons never get promoted to `logo_url`.
Token Budget
`max_tokens_out` (cl100k-base) caps extracted output; trailing table rows or heavy keys are dropped first to fit.
Anti-Patterns
- DON'T use `mode: "tables"` — use `mode: "structured"` instead.
- DON'T pass a schema without `properties` key — handler rejects it.
- DON'T extract for a whole page when you need markdown — use `fetch` instead.
When NOT to use wigolo-extract
- **Multi-page autonomous structured extraction** — use wigolo's `agent` tool instead.
- **Page requires login / click / form-fill before the data appears** — handle authentication with `use_auth` or interact with the page before extracting.
See Also
- [wigolo-fetch](../wigolo-fetch/SKILL.md) — for markdown content
- [wigolo-agent](../wigolo-agent/SKILL.md) — for multi-page schema-driven gathering
The go-to web for your AI coding agent — local-first search, fetch, crawl & research over MCP. No API keys, no cloud, $0/query. Public beta.
Repo: KnockOutEZ/wigolo
Other skills on wigolo.
- /wigolo-agent
Autonomous data gathering across sources — plans search queries and URLs from a natural-language prompt, executes in parallel within a time budget, optionally extracts structured fields via JSON Schema, and synthesizes results with full step transparency. Use when the user needs
Open skill - /wigolo-cache
Local-first knowledge cache — full-text and hybrid semantic search over every page wigolo has already fetched, crawled, or searched. Use before any web request: cached hits return instantly and free. Triggers when the user says "check the cache", "have we seen this", "what's on
Open skill - /wigolo-crawl
Local-first multi-page crawl with sitemap, BFS, DFS, and URL-map strategies, anchor-fragment dedup, rate limiting, robots.txt respect, and automatic local cache population. Use when the user wants to index documentation, crawl a docs site, extract all pages under a path, or says
Open skill - /wigolo-diff
Compare two versions of a page and see exactly what changed — a live URL against its cached copy, two URLs, or two markdown blobs. Section-level hunks, word- or line-level granularity, or a summary of counts. Use when the user says "what changed", "diff these", "compare this
Open skill - /wigolo-fetch
Local-first URL fetch with clean markdown, structured metadata, JS-rendered SPA support, authenticated browser sessions, PDFs, and content change detection. Use when the user provides a URL, says "fetch", "get this page", "read this URL", or wants content from a specific
Open skill - /wigolo-find-similar
Hybrid semantic discovery — fuses embeddings + keyword search + live web search via 3-way Reciprocal Rank Fusion. Use when the user has a good source and wants more like it, says "find similar", "related pages", "more like this", or wants to discover content related to a known
Open skill

