ExtractHub extractor builder (Agent Skill)

An Agent Skill that teaches an AI agent to build ExtractHub extractors: it inspects the page you name, picks the cheapest fetch mode that works (plain HTML, embedded JSON, JSON API, JavaScript rendering, XHR capture, browser actions), writes the extractor definition, validates it, uploads it as a private draft, tests it and releases it when you say so.

Ask your agent things like:

• "Create an ExtractHub extractor for this shop's search result pages: title, price, rating, link."
• "Scrape this job board with ExtractHub: https://... (title, company, location, salary)."
• "My ExtractHub extractor returns empty prices on this page, fix it."

For multi-step scrapes (a list page, then every detail page it links to) use it together with the extracthub-pipeline-builder skill, which chains released extractors into a pipeline.

What is inside

extracthub-extractor-builder/
├── SKILL.md                         workflow the agent follows
├── references/
│   ├── config-reference.md          field shapes, extract types, JSON paths, all transforms
│   ├── request-options.md           proxy, JS rendering, browser actions, XHR, POST, price tiers, Studio import
│   ├── selectors-and-pitfalls.md    supported selectors, stable selector strategy, engine pitfalls
│   ├── troubleshooting.md           empty fields, blocked pages, JS-only content, API errors
│   └── releasing-and-versions.md   draft, pins (@1, @1.2.3, @draft), semver, visibility
├── examples/                        6 complete definitions + notes
├── schema/extractor-definition.schema.json
├── scripts/check-config.mjs         zero-dependency structure checker (Node 18+)
├── scripts/validate.mjs             dry run on a saved sample file with the real engine (needs an API key)
└── LICENSE                          MIT

Install

Claude Code

Clone the repository into your personal skills directory (all projects) or a project's .claude/skills/:

git clone https://github.com/extracthub-io/extracthub-extractor-builder.git ~/.claude/skills/extracthub-extractor-builder

Claude Code picks it up automatically; ask for an ExtractHub extractor and it loads the skill. Update later with git -C ~/.claude/skills/extracthub-extractor-builder pull.

Claude Desktop and claude.ai

Download the repository as a ZIP (Code → Download ZIP) or zip a clone so that the zip contains one folder with SKILL.md inside:

git clone https://github.com/extracthub-io/extracthub-extractor-builder.git
zip -r extracthub-extractor-builder.zip extracthub-extractor-builder -x "*.git*"

Upload it under Settings → Capabilities → Skills (code execution must be enabled). The local checker needs Node.js; where Node is unavailable the agent validates with the MCP server or by reading the HTML.

Other agents

Agents that support the Agent Skills format load the folder from their skills directory. For any other agent, point it at SKILL.md as instructions and keep the folder next to it so it can open the references.

Connect the ExtractHub MCP server (recommended)

With the MCP server the agent can validate against the real engine, upload, test and release by itself. Without it, the agent gives you the definition and a Studio import file instead.

1. Create an API key in the ExtractHub dashboard (API keys page). The "Use with MCP" card shows ready-made snippets.
2. Add the server (Streamable HTTP, https://api.extracthub.io/mcp, key as a Bearer token):

Claude Code:

claude mcp add --transport http extracthub https://api.extracthub.io/mcp --header "Authorization: Bearer YOUR_EXTRACTHUB_API_KEY"

Claude Code, one key for both the MCP server and scripts/validate.mjs (recommended): put the key in .claude/settings.local.json (keep it out of git) and reference it from the project's .mcp.json:

// .claude/settings.local.json
{ "env": { "EXTRACTHUB_API_KEY": "YOUR_EXTRACTHUB_API_KEY" }, "enabledMcpjsonServers": ["extracthub"] }

// .mcp.json
{ "mcpServers": { "extracthub": { "type": "http", "url": "https://api.extracthub.io/mcp",
  "headers": { "Authorization": "Bearer ${EXTRACTHUB_API_KEY}" } } } }

Restart Claude Code; /mcp should list extracthub as connected.

Claude Desktop (claude_desktop_config.json, through the mcp-remote bridge):

{
  "mcpServers": {
    "extracthub": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.extracthub.io/mcp", "--header", "Authorization:${EXTRACTHUB_AUTH}"],
      "env": { "EXTRACTHUB_AUTH": "Bearer YOUR_EXTRACTHUB_API_KEY" }
    }
  }
}

Other clients: URL https://api.extracthub.io/mcp, transport Streamable HTTP, header Authorization: Bearer YOUR_EXTRACTHUB_API_KEY (or X-API-Key: YOUR_EXTRACTHUB_API_KEY). The server does not offer OAuth yet, so clients that only support OAuth connectors cannot connect; use the skill without MCP there.

More: https://extracthub.io/mcp

Test key vs live key

• Test keys (exth_test_...) are free and never fetch pages: extract calls return simulated results. Good for wiring up a pipeline; useless for checking whether selectors work.
• Live keys fetch the real page and are billed per URL (standard tier, or the JS tier when the extractor renders JavaScript, captures XHR or runs browser actions). A call that fails after the page was fetched (error or block page, extraction error, provider timeout) is still charged; failures before any fetch are free. The agent tells you before it runs a live test. Validation (dry runs on HTML the agent already fetched) costs nothing.
• Creating, updating and releasing extractors need a live key (no credit is used for these themselves); a test key can only validate.

以上为 README 的开头部分。其余内容请阅读原文。 查看完整 README ↗