zytedata
- 37 skills
- 0 followers
- 33 repo stars
- last month last updated
- ▌ Scrape 4 · zytedata bundleBuild a full-site or multi-page Scrapy spider to get structured data from a website, in a new project or added to an existing one. Do not use for analyzing locally saved HTML, fixing or debugging an existing spider, schema-only or existing-spec work, Scrapy Cloud operations, or advisory questions.
- ▌ Scrape Plan 2 · zytedata bundlePlan a web scrape and author a validated extraction spec — explore a detail page, discover fields, confirm the schema, then validate it with more pages, HTML-variant comparison, extracted values, and an optional browser review, and present the plan for approval.
- ▌ Zyte · zytedata bundleZyte APIs and cloud services: credentials (set up, log in, get an API key, or a blocked site); Scrapy Cloud (deploy, schedule or run a spider, manage cron jobs, list/stop jobs, inspect items and logs); recorded API usage (spend, requests, response times, status codes) and pricing (plans, tiers, discounts, cost estimates); how-to and docs questions about any Zyte product or account/billing, from docs.zyte.com. NOT for writing/debugging spiders locally (scrapy-extra) or estimating spend from code instead of recorded stats.
- ▌ Scrape 3 · zytedata bundleBuild a full-site or multi-page Scrapy spider to get structured data from a website, in a new project or added to an existing one. Do not use for analyzing locally saved HTML, fixing or debugging an existing spider, schema-only or existing-spec work, Scrapy Cloud operations, or advisory questions.
- ▌ Scrape Plan · zytedata bundlePlan a web scrape and author a validated extraction spec — explore a detail page, discover fields, confirm the schema, then validate it with more pages, HTML-variant comparison, extracted values, and an optional browser review, and present the plan for approval.
- ▌ Scrapy Extra · zytedata bundleRead this BEFORE writing, modifying, debugging, or explaining any Scrapy or web-poet code — spiders, page objects, pipelines, settings, selectors — down to a one-line fix, or scaffolding/configuring a Scrapy project, scrapy-poet, scrapy-zyte-api, or browser rendering. These libraries moved on since your training cutoff; invoke this FIRST. NOT for building a scraper for a given site (scrape), a saved HTML file (scrape-analyze-page), or Scrapy Cloud deploy/jobs (zyte).
- ▌ Scrape Analyze Page 3 · zytedata bundleExtract structured data (all available fields with values) from a page saved locally as an HTML file, optionally following a schema. Do not invoke when the user provides a URL. When invoking, pass the user's full request verbatim as args — do not pre-parse file paths and don't rephrase it.
- ▌ Scrape 2 · zytedata bundleEnd-to-end web scraping workflow — from URL to working spider with web-poet page objects. Use this for full-site or multiple-page crawls that create a new scraping workflow. Do not use for fixing, debugging, or modifying an existing spider.
- ▌ Scrape Spec 2 · zytedataExpand a spec created by /scrape-define — download more pages, compare HTML variants, extract values, optional browser review
- ▌ Scrape Define 2 · zytedataCreate a new extraction spec from a URL — explore a detail page, discover fields, quick schema approval
- ▌
- ▌ Scrape Zyte Login 2 · zytedata bundleSet up the user's Zyte account and credentials. Use when the user asks to set up, log in, sign up, or get an API key for Zyte; when ZYTE_API_KEY is missing; when a site is blocked; or before Scrapy Cloud deployment.
- ▌ Scrape Analyze Page 2 · zytedata bundleExtract structured data (all available fields with values) from a page saved locally as an HTML file, optionally following a schema. Use this skill only to process already downloaded files. Do not invoke when the user provides a URL. When invoking, pass the user's full request verbatim as args — do not pre-parse file paths and don't rephrase it.
- ▌ Scrape Explore Site 2 · zytedata bundleExplore a website to find and save diverse pages (start, list, detail) with classified links
- ▌ Scrape Scrapy Cloud 2 · zytedata bundleGeneral-purpose Scrapy Cloud skill — deploy projects, schedule spiders, list/stop jobs, and view items or logs. Use when asked to deploy a project or spider to Scrapy Cloud / Zyte Cloud / Scrapinghub, schedule or run a spider remotely, manage jobs, or inspect scraped items and logs.
- ▌
- ▌ Scrape Review Schema 2 · zytedata bundleGenerate an HTML review page for schema and extracted data verification
- ▌ Scrape Ensure Project 2 · zytedata bundleEnsure a Scrapy project exists with scrapy-poet and Zyte API support
- ▌ Scrape Zyte API Stats 2 · zytedata bundleQuery usage stats for Zyte API requests that have already been sent, including cost, request volume, response times, status codes, filters, grouping, and pagination. Use this skill whenever answering the request requires looking up recorded Zyte API usage, spend, request counts, response times, grouped stats, or filtered stats — including projecting future spend or usage when the projection explicitly extrapolates from actual recorded usage (e.g. "based on this month's usage so far, project month-end spend"). Do not use it when the user asks what a spider, job, or workload might, would, or could generate — those are hypothetical estimates with no recorded data to query, even if a spider exists in the project. For a projection to qualify, the user must explicitly reference past or current recorded usage as the basis. Also do not use for dashboard setup, documentation, configuration, or account-help questions.
- ▌
- ▌ Scrape Codegen Analyze 2 · zytedataAnalyze an HTML page to produce field extraction instructions for code generation
- ▌ Scrape Codegen Generate 2 · zytedataGenerate web-poet page object code from per-page extraction analyses
- ▌ Scrape · zytedata bundleEnd-to-end web scraping workflow — from URL to working spider with web-poet page objects. Use this for full-site or multiple-page crawls that create a new scraping workflow. Do not use for fixing, debugging, or modifying an existing spider.
- ▌ Scrape Spec · zytedataExpand a spec created by /scrape-define — download more pages, compare HTML variants, extract values, optional browser review
- ▌ Scrape Define · zytedataCreate a new extraction spec from a URL — explore a detail page, discover fields, quick schema approval
- ▌
- ▌ Scrape Zyte Login · zytedata bundleSet up the user's Zyte account and credentials. Use when the user asks to set up, log in, sign up, or get an API key for Zyte; when ZYTE_API_KEY is missing; when a site is blocked; or before Scrapy Cloud deployment.
- ▌ Scrape Analyze Page · zytedata bundleExtract structured data (all available fields with values) from a page saved locally as an HTML file, optionally following a schema. Use this skill only to process already downloaded files. Do not invoke when the user provides a URL. When invoking, pass the user's full request verbatim as args — do not pre-parse file paths and don't rephrase it.
- ▌ Scrape Explore Site · zytedata bundleExplore a website to find and save diverse pages (start, list, detail) with classified links
- ▌ Scrape Scrapy Cloud · zytedata bundleGeneral-purpose Scrapy Cloud skill — deploy projects, schedule spiders, list/stop jobs, and view items or logs. Use when asked to deploy a project or spider to Scrapy Cloud / Zyte Cloud / Scrapinghub, schedule or run a spider remotely, manage jobs, or inspect scraped items and logs.
- ▌
- ▌ Scrape Review Schema · zytedata bundleGenerate an HTML review page for schema and extracted data verification
- ▌ Scrape Ensure Project · zytedata bundleEnsure a Scrapy project exists with scrapy-poet and Zyte API support
- ▌ Scrape Zyte API Stats · zytedata bundleQuery usage stats for Zyte API requests that have already been sent, including cost, request volume, response times, status codes, filters, grouping, and pagination. Use this skill whenever answering the request requires looking up recorded Zyte API usage, spend, request counts, response times, grouped stats, or filtered stats — including projecting future spend or usage when the projection explicitly extrapolates from actual recorded usage (e.g. "based on this month's usage so far, project month-end spend"). Do not use it when the user asks what a spider, job, or workload might, would, or could generate — those are hypothetical estimates with no recorded data to query, even if a spider exists in the project. For a projection to qualify, the user must explicitly reference past or current recorded usage as the basis. Also do not use for dashboard setup, documentation, configuration, or account-help questions.
- ▌
- ▌ Scrape Codegen Analyze · zytedataAnalyze an HTML page to produce field extraction instructions for code generation
- ▌ Scrape Codegen Generate · zytedataGenerate web-poet page object code from per-page extraction analyses