Octoparse universal scraper

Data extraction through ~670 preset Octoparse templates, run as cloud tasks via the Octoparse MCP server.

Division of responsibility — read this before anything else:

• This skill routes. Which template fits, which is the default, which pairs are real chains, what to avoid.
• The MCP service executes and holds truth about schemas. Input/output fields, sourceTree, and current availability come from search_templates at run time, never from memory.
• data/catalog.json is a routing projection only (id, name, category, language, run_on, price). It is regenerated from upstream and carries no schemas.

Never assemble parameters from this skill's prose or from a remembered field name. Always read the live inputSchema first.

Prerequisites

Octoparse MCP server connected and authorized. If search_templates fails with an auth error, use the octoparse-mcp-setup skill.

Workflow

Step 1 — Pick the capability